![]() Implemented scaffolding of configuration interfaces. In order to run it, select the Middleware node or one of the packages under the Beans node in the CUBA project tree and click the New > JMX Bean item of the context menu. Studio will create a Spring bean in the core module with two listener methods: one notified before and another after transaction commit. In order to run it, select an entity class, package, or the top-level Middleware node in the CUBA project tree and click the New > Entit圜hangedEvent Listener context menu item. Implemented scaffolding of Entit圜hangedEvent listeners. For example, by specifying command line arguments you can set non-default timezone: -Duser.timezone=Europe/London or increase memory settings: -Xmx1500m for the application server. These settings are applied to the tomcat process running the CUBA application in debug mode. Two additional settings were added to the CUBA Application run configuration: Command line arguments and Environment Variables. ![]() ![]() Fields were rearranged between steps and more fields were added to the wizard: Module Prefix, supported programming languages, Locales, Main Data Store properties. The CUBA project creation wizard has been extended. If you encounter any problems with Java / Groovy projects, you can switch back to the old mechanism by turning off the following setting: Main Menu → CUBA → Settings → Project Settings → Hot deploy compiled classes. The Hot Deploy mechanism for projects using platform 7.2.0 or later has been reworked (for all languages) in order to support Kotlin language. Studio visual designers, smart auto completions, inspections and hot deploy support Kotlin language as well. All elements of the CUBA project: entities, screens, services can be generated using Kotlin. You can select Kotlin as a project’s programming language in the project creation wizard, if selected platform version is 7.2.0 or later. Support for Kotlin as a programming language has been added. Adding data containers, tables and grids, table column, table action and form field components to the screen has become easier. By pressing it you can add one or more columns or actions to the table.Ĭomponent creation wizard dialogs have been added to the Screen Designer. When a table, one of table columns or actions is selected, the Component Inspector displays the + Add button. Adding a new table column or action also became easier. Now you can view and edit column and action properties and event handlers right in the Component Inspector panel. As a part of this change, several modal dialogs were removed that were used previously to edit columns and actions. Screen Designer now displays Table (and DataGrid) columns and actions in the Component Hierarchy tree. The source code immediately reflects all changes. You can drag new components from the Palette to the Hierarchy, reorder components and edit component properties in the Inspector panel when only source code is displayed in the editor. When the editor caret is moved from one XML tag to another, the corresponding component is selected in the Component Hierarchy and Component Inspector panels.Ĭlicking element in the Hierarchy panel moves the caret to the corresponding XML tag in the source code. The following infrastructure improvements have been implemented for developers located in China: Previously downloaded standalone Studio IDE will not be upgraded - you should download the new version from the CUBA Platform web site. Standalone IDE version of the Studio has been upgraded to the IntelliJ Community platform 2019.3. Now it is configured to use up to -Xmx1200m, up from previously used -Xmx768m value. In case if using MySQL driver is essential for some reason, it can be enabled by adding the disableMariaDbDriver parameter to the connection string.ĭefault memory settings for the standalone IDE version of the Studio have been increased. It is no longer required to download MySQL proprietary driver in order to use MySQL with the Studio. Studio now uses MariaDB connector when connecting to both MySQL and MariaDB databases. The same done to the database schema check happening before the CUBA Application run configuration is started. Processing time of the Generate Database Scripts operation has been significantly optimized (reduced). Integration with the IntelliJ IDEA Ultimate EditionĪfter logging in you will be able to download and install trial versions of the commercial add-ons in the Marketplace window. Environment variables as connection parameters
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |