Known Issues And Limitations

CUBA 7.0 does not support the desktop client. You should not migrate your project to this release if you depend on Desktop module.

Hot-deploy mechanism for UI screens is limited to changes in the existing screens only. If you create a new screen while your application is running this screen will not be hot-deployed. See GitHub issue for details.

Tree UI component has been reworked using TreeDataGrid. For now it does not have borders and padding and looks different than old Tree.

The framework does not use idea / eclipse Gradle plugins and you must import the project using the standard IDE mechanisms. In the simplest case you just open build.gradle file as a project. See Studio User Guide for detailed instructions.

CUBA and add-ons (BPM, Charts, FTS, Reports) configuration files have been moved from the classpath root to the root packages of the appropriate application components. For example, /cuba-persistence.xml became /com/haulmont/cuba/persistence.xml. These changes do not affect properly configured application projects, except in one case: in the test containers, there is a reference to the test-app.properties file which is now at com/haulmont/cuba/testsupport/test-app.properties. So if you are using middleware integration tests, edit your test container class and replace the reference:

Old commons-lang dependency has been removed, the platform depends on new commons-lang3 library. You can either migrate usages to commons-lang3 (simply change imports to use org.apache.commons.lang3 package) or add explicit dependency compile('commons-lang:commons-lang:2.6') to your global module in build.gradle.

Dependency on groovy-all package has been removed. Now the framework depends only on groovy, groovy-templates and groovy-sql modules. Add required Groovy modules to your project dependencies if needed.

Dependency on MyBatis and com.haulmont.cuba.core.sys.mybatis.UUIDTypeHandler class have been removed. If you need MyBatis in your project, see the Integration with MyBatis section for instructions.

Interfaces Component.Container, Component.HasValue, Component.HasFormatter and others have been extracted from Component and moved to com.haulmont.cuba.gui.components package. See GitHub issue for details. Imports of those interfaces must be changed, e.g. instead of com.haulmont.cuba.gui.components.Component.HasValue import com.haulmont.cuba.gui.components.HasValue directly.

Deprecated methods addListener and removeListener of Instance have been removed. Use addPropertyChangeListener and removePropertyChangeListener instead.

All addSomeListener and removeSomeListener methods in UI components now receive Consumer<E> where E is a type of event object. If you use those methods with a lambda parameter then your code will not require migration. If you implement one of the old listener interfaces (e.g. ValueChangeListener) with a standalone class you will need to implement Consumer<E> (e.g. ValueChangeEvent) instead. See GitHub issue for details.

Regular screens cannot be used in the frame element anymore. Previously, such usage generated a warning in the server log. Now only frames/fragments with controllers inherited from AbstractFrame or ScreenFragment can be used as frames inside another screens.

WebWindowManager class has been replaced with WebScreens. If you have extended WebWindowManager in your code you will need to migrate your improvements manually.

Behavior of Component methods isVisible and isEnabled has been changed. Now methods return only value of the component visibility / enabled without taking parent value into consideration. New isVisibleRecursive and isEnabledRecursive methods are introduced.

Interface HasValue now has type parameter V - type of the corresponding value of UI component. Old code that uses untyped UI components, for instance TextField or LookupField might be broken. You can find default type of the UI component in its interface in TYPE_DEFAULT constant. For example (here TextField has default type String):

JQuery is not loaded by default on first page rendering anymore. Add jquery.js to dependencies of your UI component class explicitly if it requires JQuery.

FreeMarker templates are not supported in caption and description attributes of a window. Now values loaded from XML are treated as simple String values. If you want to use templates in those attributes you can call com.haulmont.cuba.core.global.TemplateHelper methods manually from a screen controller.

Screens declared in screens.xml file with class attribute do not support Runnable interface anymore. You can register only UI controllers that extend Screen class. The old behaviour is considered dangerous because a caller that opens such a screen receives null from openWindow call. Those screens must be changed: you can convert them into Spring beans or if you need to call them only from the menu - use class attribute of a menu item.

Screen agent support has been removed without replacement. You can get DeviceInfo using the DeviceInfoProvider bean and either create different screens for each device type or open fragments in a screen.

Old Havana UI theme completely reimplemented on the basis of Halo theme. If you have extended Havana you will need to migrate your SCSS styles accordingly. See GitHub issue for details.

Property wordwrap of TextArea has been renamed to wordWrap. XML definitions still work, but wordwrap is removed from XSD and should not be used anymore.

ComponentPalette has been removed. Use the standard mechanism with cuba.web.componentsConfig application property if your application component provides UI components.

Deprecated ObjectsCache classes have been removed as a legacy and undocumented feature.

Charts UI palette - the ChartComponentPalette class have been removed. Use the standard application component mechanism or include charts-web-components.xml into cuba.web.componentsConfig application property explicitly. If you did not use ChartComponentPalette then migration actions are not required.

Class com.haulmont.cuba.core.app.DataServiceQueryBuilder has been renamed to RdbmsQueryBuilder.

com.haulmont.cuba.gui.components.RowsCount.BeforeRefreshEvent does not have reference to a datasource anymore.

Validators of UI components are triggered even if the value of UI component is empty.

If you have defined own password encryption module (not SHA1), set cuba.legacyPasswordEncryptionModule = <your encryption module> in the app.properties files for all modules. It is necessary to authenticate existing users having empty SEC_USER.PASSWORD_ENCRYPTION field in the database.

By default, the UI components description property isn’t processed as HTML markup. This can be changed by setting descriptionAsHtml=true.

BaseAction does not set caption implicitly (using id as message key) anymore. Now it must be set explicitly.

WidgetsTree UI component has been removed as legacy and undocumented feature.

Removed multiSelect attribute of the TwinColumn UI component.

TextArea and ResizableTextArea are now different UI components with own XML elements: <textArea> and <resizableTextArea>. The <textArea> element still has resizableDirection and resizable attributes for backward compatibility, but if you inject the component with resizable="true" in a controller, the type of the field must be ResizableTextArea, otherwise you will get ClassCastException.

A password storage format for the cuba.rest.client.secret application property has been changed. The password encoder should be defined and the default property value is now {noop}secret instead of secret. If you explicitly defined the cuba.rest.client.secret property value in your project you should change its value according to the new format (add {noop} before the value. See GitHub issue for details.

Since version 7.0.8 cookies which set programmatically with AppCookies are httpOnly by default. It potentially can break some client-side code accessing cookies.

Former Premium Add-ons

The former premium add-ons (BPM, Charts, Full-Text Search, Reports) - are free and open-source since version 7.0. The source code projects have been moved to GitHub:

LoginPasswordLoginProvider of the client blocks sends user’s password to the middleware as is (i.e. not hashed as in previous versions). See cuba.checkPasswordOnClient app property for recommendations.

Web client exception handlers have new base classes, see Client-Level Exception Handlers. The old classes have been deprecated and kept for backward compatibility.

Studio

All Studio functionality has been moved to the plugin for IntelliJ IDEA. It supports projects based on CUBA 6.10 and 7.0, so you can open an existing project in the new Studio and migrate it to the new framework version. See CUBA Studio User Guide for details.

If you need premium add-ons (Reports, BPM, etc.) for a project based on CUBA 6.10 and you have a subscription, you should set the premium repository access credentials in ~/.gradle/gradle.properties as described in the documentation. Studio does not pass the credentials to Gradle.