- upgrade 2020.7.5
- see Upgrading the Prime Radiant for how to run the upgrade
- CLI upgrade
nsf update -v 2020.7.5
2020.7.1 patch fixes a few issues with the
The following issues have been fixed in web-styles version
<i/>tags were used for icons instead of
<span/>, which caused some strange issues with duplicated icons in the UI. These have been corrected to use
- Fixed some loading issues with the new jqPlot version. Graphs should now render correctly again.
createaccess right was wrongly mapped in
access-rights.js, which is now fixed
Fixed compatibility issues
The Prime Radiant had trouble with previous versions of the expanders because the latest web-styles and base-components were being used.
It will now correctly use older versions for expanders
When using newer expanders versions, the Prime Radiant will convert the expansionSettings to use the nsx-default-stack in combination with setting the applicationInstance to PROVIDED. (See release 2020.7.0 for an explanation on this setup.)
Full export more consistent with import
The export button on the application page will now export everything related to the source base of the application. This will make the import/export more consistent as developers will be able to synchronize the entire sourceBase from the application page.
This should also fix issues with components being exported to the sourceBase of the application even if they had a different sourceBase configured.
Nsx-prime has been modified to use a single classLoader for all expansion-resources. Before, it was possible for nsx-prime to use a chain of classLoaders. This, however, could have the effect of causing class conflicts in some specific setups.
2020.7.2 fixed the version of
base-creator-tasks in the upgrade zip.
2020.7.1 contained the wrong version, causing the
update source bases and
update deploy bases buttons to fail until the correct jar was fetched by another task.
2020.7.5 contains some more bugfixes.
2020.8.1, which groups changes to web-styles, base-components and the expanders.
There was an issue that caused the Prime Radiant to use the wrong expansionSettings.xml when expanding or harvesting, causing some strange issues because for example the expansion path was different than expected.
Also, synchronization of the expansionSettings with the configuration in the Prime Radiant has been improved. It will now be more stable and will show warnings if expanding when there are still issues in the model, such as missing model-repositories.
The base-components have been split up in
base-components-model, which only contains the model and harvest, and
base-components, which contains that and some additional expanders.
This change should not have any effect of the actual applications.
Furthermore, an issue has been fixed where an engine could get stuck if interrupted at the wrong time.
The issue with the broken icon of the dat-input field is fixed. You may have to clean the browser cache for it to take effect.
Default stack has been translated to expansion-resources
This release introduces the concept of the default stack expansion-resource. This expansion-resource is empty, but includes dependencies on all resources necessary to expand a regular application.
These dependencies include the following:
- prime-data: includes standard data such as layers, technologies and libraries
- Expanders: the default expanders control structure and all basic expanders
- web-styles: resource files used by the frontend
- base-components: provides models for the base-components and other related functionality
This default stack replaces custom logic in nsx-prime that included these resources based on the versions defined in the nsfInstallation.xml. This separation is a big step in the direction of making the expanders more universally applicable, as developers can then define their own version of the default stack or their own set of expanders. In the future, the expanders will be more cleanly separated to allow the expansion to be run without the default expanders stack.
How to use the default stack
To use this setup, you must:
- Set the expandersVersion in the applicationInstance to
PROVIDED. In your expansionSettings.xml files, remove the
<expandersVersion>if it was defined, or set it to PROVIDED as well.
net.democritus:email@example.com an expansion-resource on the expansion-resources tab of the expand page or directy to the expansionSettings.xml.
Your expansion should now run the same as before.
How to define specific versions of the Expanders or other resources
Let’s say we want to use the
2020.7.0 default stack, but use a newer expanders version.
In that case, we can add the resource explicitly:
By defining the version explicitly, nsx-prime will prefer the defined version. Note that you can only force newer versions. Using an older version will result in a conflict with the nsx-default-stack dependency!
See full article
Together with the conversion of the web-styles to an expansion-resource, it has been made easier to extend the web-styles with custom layouts or extra web resources.
The StringLong value-field-type uses TinyMCE to render an editor. The library in the web-styles has been updated to the latest version.
Experimental: JPA configuration
Several options have been added to control the naming of data-sources and the naming of entities. To know more, check the expanders changelog
It is also possible to force the use of a single schema for the entire application.
singleDataBaseSchema forces all data-elements to use the schema defined in the option value (leave empty for default schema).