Error in a view defined in a screen, please specify the screen

Support
#1

Hi

On server launch the following error message can be seen when a property does not exist in a view defined locally in a screen xml.

image
image740×101 10.7 KB

It seems that the platform checks all views including the ones in screens the first time a view is required.

8:35:31.520 INFO  com.haulmont.cuba.core.sys.AbstractViewRepository - Initializing views
18:35:31.572 ERROR com.haulmont.cuba.core.sys.ServiceInterceptor - Exception: 
com.haulmont.cuba.core.global.DevelopmentException: View ibusy2_SupplierOrderLine/ definition error: property agent doesn't exist
	at com.haulmont.cuba.core.sys.ViewLoader.loadViewProperties(ViewLoader.java:129)
	at com.haulmont.cuba.core.sys.ViewLoader.loadViewProperties(ViewLoader.java:169)
	at com.haulmont.cuba.core.sys.AbstractViewRepository.deployView(AbstractViewRepository.java:441)
	at com.haulmont.cuba.core.sys.AbstractViewRepository.init(AbstractViewRepository.java:110)
	at com.haulmont.cuba.core.sys.AbstractViewRepository.checkInitialized(AbstractViewRepository.java:82)
	at com.haulmont.cuba.core.sys.AbstractViewRepository.findView(AbstractViewRepository.java:209)
	at com.haulmont.cuba.core.sys.AbstractViewRepository.getView(AbstractViewRepository.java:181)
	at com.haulmont.cuba.core.global.LoadContext.setView(LoadContext.java:165)
	at com.haulmont.cuba.core.global.FluentLoader.initCommonLoadContextParameters(FluentLoader.java:70)
	at com.haulmont.cuba.core.global.FluentLoader.access$100(FluentLoader.java:29)
	at com.haulmont.cuba.core.global.FluentLoader$ById.createLoadContext(FluentLoader.java:241)
	at com.haulmont.cuba.core.global.FluentLoader$ById.optional(FluentLoader.java:250)
	at com.ibusy2.service.CompanyServiceBean.getCompanyOrNull(CompanyServiceBean.java:74)

As you can see the screen is not mentionned. And I have hundreds of screen and counting. It would be nice to mention it.

Especially when now the local views in screen are the ‘recommended’ way (yeepee hundreds and hundreds more views to maintain and unfetched errors that go with them, it’s christmas !)

Regards
Michael

#2

This particular exception is caused by loading an inline view defined in the shared views.xml file.

You can define only named views, then you will be able to spot errors quickly - you will see the name like ibusy2_SupplierOrderLine/my-view.

#3

Ok, it was not a view inlined in a screen, then, my bad.

Not sure if/when I will spend time renaming all internal views of my big views.xml file, but that’ts an option !

Thank you @krivopustov

Michaël