CUBA Studio Changelog

Version 1.2.0

• Common
  1. Platform 5.2 release support.
     Automatic migration of existing projects is provided, the following will be done by the migration procedure:
     • Update servlet API version in build.gradle
     • Update Spring XSD version in all spring.xml files
     • Add new context parameter to web module's web.xml if the web-toolkit module exists
     • Move views.xml from core module in global and update cuba.viewsConfig application property in web, desktop and portal modules
     • Replace cuba.connectionUrl with cuba.connectionUrlList in all application properties files
     • Optionally change the platform XSD version to 5.2 in all XML files.
  2. Gradle 1.12 is now recommended, and it will be automatically downloaded if nothing is specified in the Gradle home field of the server window.
  3. Double-click on the navigator tree opens the selected item for edit.
  4. Go to edit/browse screen commands are added to the entities tree, Go to entity command is added to the screens tree.
  5. Links in the Project properties section can be used to create optional modules (Desktop, Portal, Web-toolkit).
  6. Language field in the server window can be used to choose the Help panel language.
  7. New project dialog is completely reworked.
  8. New project template now contains .gitignore file with some default patterns.
  9. Plugins support. To create a plugin, click on the Generate Studio plugin project link in the Project properties section and follow the instructions in the Context help panel.
     The generated plugin allows to use the current project as base for other projects.
  10. User home directory can be defined in studio.user.home JVM property. Default value is specified in the Studio launch scripts located in bin directory. See DEFAULT_JVM_OPTS variable.
• Entity designer
  1. Full support of @MappedSuperclass entities.
  2. Non-persistent entities registered in metadata.xml are displayed in the navigator tree and can be used in datasources.
  3. @SystemLevel base entities are not displayed in various lists anymore.
  4. @Lob annotation is used to define an entity attribute of unlimited length.
  5. Order by field allows to specify ordering for an entity attribute of type List.
  6. Precision and scale of BigDecimal attributes are now stored in @Column annotation parameters, if they differ from 19,2.
  7. Mandatory Boolean attributes now have field initializers which set them to false.
  8. Any entity attribute can be marked as Unique. In this case an appropriate unique constraint will be generated in the database init/update scripts.
  9. Update script commands for HSQL, PostgreSQL and Microsoft SQL Server are separated by semicolons. This ensures the execution of the whole script in one transaction. If the update script fails, all its changes are reverted, which keeps database scheme in sync with the information about executed updates.
  10. Database can be created or updated right from the DB manager page and from the warning dialog that appears on application server start if the database scheme doesn't conform to the data model.
• Screen designer
  1. Autocompletion in the datasource query editor: pressing Ctrl+Enter shows either the list of entities or the list of entity attributes, depending on the cursor position.
     For example, if you type "select e from li" and press Ctrl+Enter, you will see the list of entities which names start from "li". If you type "select e from library$Author e where e." and press Ctrl+Enter, you will see the attributes of entity library$Author.
  2. When you link components to a datasource, the screen layout designer shows only properties contained in the view, specified for this datasource.
  3. If the FieldGroup fields have the same width, the layout designer combines them in a column and sets the width for the whole column.
  4. Layout tab is activated right after opening a screen for edit.
  5. Empty init() method is not created in new screen controllers anymore.
• Over 100 other bug fixes, enhancements and usability improvements.