Skip to main content

expanders

9.5.0 (2026-06-11)​

Added​

  • Add optional StaticFileServlet for environments that cannot rely on the default servlet

Changed​

  • Added ResourceVersionConstraints to avoid conflicts with older versions of Expanders
  • Removed dummy module field-type-expanders
  • Removed dummy module functional-key-expanders
  • Removed Expanders module (all expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. have been moved to smaller modules in 9.4.0)
  • Enable #control.web.defaultServlet by default is standard-api is available instead of by option

9.4.0 (2026-03-31)​

Changed​

  • Moved all code from Expanders into dedicated modules:
    • jee-knockout-menu-expanders
    • jee-translation-expanders
    • jee-proxy-logic-expanders
    • jee-ear-packaging-expanders
    • Expanders will depend on all of them for backwards compatibility

9.3.0 (2026-03-03)​

Added​

  • Several expansion steps can now be disabled by providing the relevant tags:
    • #harvest.ext.disable disables ext directory harvestingHarvestingThe process of extracting and persisting custom code from anchors and ext directories back into source directories..
    • #harvest.test.disable disables test directory harvestingHarvestingThe process of extracting and persisting custom code from anchors and ext directories back into source directories..
    • #harvest.clean.disabled disables deletion of the harvest directory.
    • #overlay.disabled disables the copying of the overlay directories.
  • Added error handling in commands when fetching target details fails.

Changed​

  • Updated Maven plugins in expanded code:
    • org.apache.maven.plugins:maven-compiler-plugin: 3.14.0 -> 3.14.1
  • Updated prime-core from 2024.6.0 to 2025.11.0
  • Moved subset of Expanders to jee-ear-packaging-expanders

9.2.0 (2025-10-20)​

Added​

  • Added maven.classifier option for elements::Library elements. This allows you to specify the classifier for a Maven dependency in such a data resource.

Changed​

9.1.0 (2025-10-02)​

Fixed​

  • Updated groupId in ejb-ear POM file to be consistent with the other POM files.

Added​

  • Added support for Java 25.

9.0.2 (2025-09-22)​

Changed​

  • [NSX-606] Updated TaskInterfaceExpander to support @imports.

9.0.1 (2025-09-16)​

Fixed​

  • (runtime) Fixed operator-precedence error in IS NULL query parameters.

9.0.0 (2025-08-05)​

Due to the critical nature of CVE-2024-53677 at a 9.5 on the CVSS 4 scale, we've decided to no longer support the interceptor fileUpload in Struts2. Version 8.3.0 of ExpandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. previously migrated all code using this interceptor to its replacement, the actionFileUpload interceptor and the UploadedFilesAware interface. All custom upload actions must be migrated when upgrading to ExpandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. 9.x.

Added​

  • Introduced new application-shared-struts2-jakarta library to target Jakarta EE. Currently intended only for testing with Struts2 7.0.3.

Changed​

  • The application-shared-struts2 library is now built against JEE 6 instead of JEE 5, since we already dropped support for JEE 5.

Removed​

  • Removed deprecated fileUpload interceptor. (CVE-2024-53677) (See WW-5386)

8.5.1 (2025-07-29)​

Fixed​

  • Replaced dependency on commons-lang3 in Struts2 with version 3.18.0. (CVE-2025-48924)

8.5.0 (2025-07-10)​

Changed​

  • Updated dependencies in expanded code:
    • org.apache.maven.plugins:maven-ear-plugin: 3.0.2 > 3.4.0
    • org.codehaus.mojo:build-helper-maven-plugin: 3.4.0 > 3.6.1
  • Updated nsx-runtime: 2024.3.0 -> 2025.0.0

8.4.1 (2025-06-10)​

Changed​

  • Updated nsx-runtime: 2024.1.0 -> 2024.3.0

8.4.0 (2025-05-12)​

Added​

  • Added custom and feature anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. to struts-conversion.properties and struts-validators.xml.

8.3.1 (2025-04-23)​

Fixed​

  • Added missing coordinate redirection for jakarta.ejb.NoSuchObjectLocalException.

8.3.0 (2025-04-22)​

Added​

  • Added the actionFileUpload Struts interceptor to the jsonEntererStack and jsonCommandStack interceptor stacks.
  • Added interfaces feature anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion. to the EntererAction class.
  • Added the option experimental.struts.security.enforceAnnotatedParameters to enable strict use of fieldsFieldA property of a DataElement expanded to a database column and user interface input element. in Struts actions that are annotated with @StrutsParameter.

Changed​

  • Updated ImporterAction to use the actionFileUpload interceptor, as the fileUpload interceptor was deprecated in Struts 6.4.0.
  • Marked fieldsFieldA property of a DataElement expanded to a database column and user interface input element. that take input for requests with @StrutsParameter interface in preparation to allow the use of input filtering for additional security:
    • CommandPerformerAction
    • EntererAction
    • FindAction
    • FullProfileAccessRightsAction
    • GetApplicationPropertiesAction
    • GetComponentMetaDataAction
    • GetDataElementMetaDataAction
    • GetFindersForDataElementAction
    • GetMenuAction
    • ImporterAction
    • ProjectorAction
    • TranslateTextAction
  • Updated dependencies:
    • org.apache.maven.plugins:maven-assembly-plugin: 3.6.0 > 3.7.1
    • org.apache.maven.plugins:maven-ear-plugin: 2.9.1 > 2.10.1
    • org.apache.maven.plugins:maven-ejb-plugin: 3.0.1 > 3.2.1
    • org.apache.maven.plugins:maven-surefire-plugin: 3.1.2 > 3.5.3
    • org.apache.maven.plugins:maven-war-plugin: 3.3.2 > 3.4.0

Removed​

  • Removed unused fieldsFieldA property of a DataElement expanded to a database column and user interface input element. from ImporterAction:
    • uploadDataContentType
    • uploadDataFileName
    • downloadDirectory
  • Removed file upload interceptor from jsonFinderStack interceptor stack in struts-header.xml.

8.2.0 (2025-04-14)​

Changed​

  • Replaced deprecated interfaces in Struts2 runtime and expanded code:
    • com.opensymphony.xwork2.Action > org.apache.struts2.action.Action
    • com.opensymphony.xwork2.ActionSupport > org.apache.struts2.ActionSupport
    • com.opensymphony.xwork2.ActionContext > org.apache.struts2.ActionContext
    • com.opensymphony.xwork2.ActionInvocation > org.apache.struts2.ActionInvocation
    • com.opensymphony.xwork2.Preparable > org.apache.struts2.Preparable
    • com.opensymphony.xwork2.interceptor.AbstractInterceptor > org.apache.struts2.interceptor.AbstractInterceptor
    • com.opensymphony.xwork2.util.ValueStack > org.apache.struts2.util.ValueStack

8.1.0 (2025-03-07)​

Fixed​

  • Added a temporary dependency on the latest version of Freemarker in application-shared-struts2, because struts2-core depends on a version that is picked up by the maven-enforcer-plugin as a false positive for J8 bytecode incompatibility.

Changed​

8.0.5 (2025-02-20)​

Changed​

  • Merged v7.7.4 into v8.0.1.
  • Fixed noXLayer optionType descriptions to be more consistent.

Fixed​

  • Updated SNAPSHOT dependency to data-layerLayerLogical separation of functionality within a single system/application, focused on code organization.-jpa-expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. to released version (1.1.0).

8.0.4 (2025-02-06)​

Fixed​

  • Replaced snapshot version for data-layer-jpa-expanders with release.

8.0.3 (2025-02-06)​

Fixed​

  • Added dummy expansion resourcesExpansion Resource (ExpansionResource). A reusable resource bundle containing expanders and features that provide specific application capabilities, defined in the expansion settings and added to the classpath during expansion. for field-type-expanders and functional-key-expanders which were removed in 8.0.0, so they override older versions in the dependency tree that still contain expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. that were moved to other bundles.

8.0.2 (2024-12-05)​

  • Merged v7.7.4 into v8.0.1.

Changed​

  • Updated applicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution.-data-protocol to v1.1.0 to port changes to ExpandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. from v7.7.4.

8.0.1 (2024-11-25)​

  • Re-release 8.0.0 due to error in maven setup.

8.0.0 (2024-11-25)​

Changed​

  • Changed pom expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. so that dependencies from LayerImplementations are only added once (Does not work if 2 layerImplementations with different technologies include the same library.)
  • Moved expanders-core and expanders-test-utils to expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact.-core repository.
  • Moved several knockout expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. to web-styles.
  • Moved data and io features to application-data-addons.
  • Moved projectionProjectionA tailored subset of fields on a DataElement designed to encapsulate data for a specific technical or functional view. and other pojo class expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. to application-data-protocol.
  • Expanders is no longer a fat jar.

7.8.3 (2025-02-13)​

Fixed​

  • Fix ElementChildRetriever not using interface method for abstract parents.

7.8.2 (2024-11-07)​

Fixed​

  • Added option maven.layer.module on LayerType to indicate that the layerLayerLogical separation of functionality within a single system/application, focused on code organization. type must be included as a Maven module for a component in the JEE applicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution. project.

7.8.1 (2024-11-06)​

Added​

  • [NSX-285][NSX-550] Added option legacy.view.knockout.forceStruts2 to force the use of Struts2 for the Knockout UI when the JAX-RS standard APIStandard API (stdAPI). A fully generated JAX-RS REST API expanding JSON:API compliant endpoints directly from JEE element models. is enabled.

7.8.0 (2024-11-05)​

Changed​

  • Updated Struts2 from 6.4.0 to 6.6.1.
  • The applicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution. root POM and component root POM now add dependencies on layerLayerLogical separation of functionality within a single system/application, focused on code organization. modules based on the model instead of a hardcoded template.

Removed​

  • Removed experimental option experimental.maven.noViewPom.

7.7.4 (2024-12-05)​

Changed​

  • [VEGA-393] Reverted change to Validator and Converter interfaces from 7.7.3.
  • [VEGA-394] Reverted deprecations on DataElement artifactsArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project. from 7.7.3.

7.7.3 (2024-10-08)​

Changed​

  • [VEGA-392] Unique Constraints are now implemented in separate {DataElement}Uniqueness classes.
  • [VEGA-392] Unique Constraints will now ignore instances deleted with a soft delete (disabled fieldFieldA property of a DataElement expanded to a database column and user interface input element.).
  • [VEGA-390] Fixed an issue with the hasBridgeClass option where the wrong method name would be used on a Local Agent.
  • [VEGA-383] Added @Deprecated to getDetails() and getDataRef() methods in several locations.
  • Added @Deprecated to remaining delete(Long), getInfo(), getName() and getId() methods.
  • Usage of deprecated interfaces, such as IFieldValidator and several specific converter interfaces has been removed.
  • Changed Struts validator classes to make use of the api provided by Struts instead of a handmade solution relying on reflection.
  • Refactored logic in several places that still relied on deprecated methods.

7.7.2 (2024-08-12)​

Fixed​

  • [NSX-454][VEGA-382] Fixed issues with null values in UniqueConstraint query.

Merged​

  • Merged 6.2.8 into master.

7.7.1 (2024-08-09)​

Added​

  • Added feature anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. to calculate methods
  • Added option type for feature.mapping.doNotInheritExpanderMapping and elementType on Feature.
  • Added option type for isFindAll on FinderFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement..
  • Added option type for parentLayer on LayerType.

7.7.0 (2024-08-03)​

Changed​

  • The option projection.detailsWithoutRefs is now cascading and available on Component and Application as well.
  • Moved JAX-RS standard APIStandard API (stdAPI). A fully generated JAX-RS REST API expanding JSON:API compliant endpoints directly from JEE element models. modules to separate project.
  • Updated nsx-runtime: 2024.0.0 -> 2024.1.0
  • Updated hamcrest: 2.2 > 3.0
  • Updated prime-core: 2024.4.2 > 2024.4.3

7.6.0 (2024-07-24)​

Fixed​

  • Added distinctive translation for Ne finderFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement. operator.

Added​

  • [NSX-285][NSX-411] Added openapi documentation for upload and download endpoints.
  • [NSX-285][NSX-411] Description for included property of resource documents.
  • Added Sne finderFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement. operation as negated variant of Se.

Changed​

  • [NSX-285] Changed response code for successful file uploads to 200 OK.
  • [NSX-285] Retain file extension of uploads to improve file type identification with tika.
  • [NSX-285][NSX-411] The JSON:API type parameter is now also specified with a single-value enum in the OpenAPI spec.
  • [NSX-285][NSX-411] Now expanding representation of reference and relationship schemas for specific DataElements instead of using a common schema in order to provide sufficient documentation depending on the context of where it is used.
  • Updated prime-core to version 2024.4.2.

7.5.0 (2024-07-10)​

Added​

  • Added syntax for custom anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion.. In the ExpanderExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact./Feature template, you can use @custom:my-anchor-name, which will be translated to // anchor:custom-my-anchor-name:start and // anchor:custom-my-anchor-name:start, or whatever comment syntax is used in the generated artifactArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project.. (This uses the same logic for creating line comments as Features.)
  • [NSX-285][NSX-411] Added openapi documentation for applicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution.-level endpoints.

Fixed​

  • [NSX-480] ArtifactExpander now avoids resolving expanderExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. model when retrieving artifactArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project. definition to prevent issues while testing Features.
  • Updated parsing of separator option for feature anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. so newlines are always translated correctly into the template.
  • [NSX-285][NSX-411] Updated openapi specification with correct response for filter endpoints.

7.4.10 (2024-06-27)​

Added​

  • [NSX-285][NSX-411] Added error responses to openapi specification.
  • [NSX-285][NSX-411] Added security documentation anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. to openapi specification.

Changed​

  • [NSX-285][NSX-411] Split off common identifier parameter from resource endpoints in openapi specification.

7.4.9 (2024-06-26)​

Fixed​

  • Knockout bindings to link the css stylesheets were not applied on the data page for csv import/export.
  • [NSX-285][NSX-411] Added missing relationships elements where needed to the documentation of the GET endpoints.

Added​

  • [NSX-285][NSX-411] Initial documentation for POST, PATCH and DELETE endpoints.

Changed​

  • [NSX-285][NSX-411] Moved the OpenAPI specification for the new standard APIStandard API (stdAPI). A fully generated JAX-RS REST API expanding JSON:API compliant endpoints directly from JEE element models. into the control/openapi folder under the applicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution. expansion root.
  • [NSX-285][NSX-411] Split up the OpenAPI specification into multiple files per DataElement to make it more readable.

7.4.8 (2024-06-20)​

Changed​

  • [NSX-285][NSX-464] Added support for In/NotIn find operation.
  • [NSX-285] Added support for Null/NotNull find operation.

Fixed​

  • [Knockout] Fixed menu in io pages by replacing menu import with app-menu.

7.4.7 (2024-06-19)​

Fixed​

  • [NSX-285] ByteArray was incorrectly translated to OpenAPI specification.
  • [NSX-285] Support for legacy custom ValueFieldTypes in OpenAPI specification.

7.4.6 (2024-06-17)​

Merged​

  • Merged 6.2.7 into master

7.4.5 (2024-06-17)​

Fixed​

  • [NSX-285] Fixed uploading to correctly overwrite temporary file.
  • [NSX-285] Content type was not correct in upload, now inferred with Apache Tika.

7.4.4 (2024-06-14)​

Fixed​

  • [NSX-285] Added content type to asset download.

7.4.3 (2024-06-14)​

Fixed​

  • Fixed incorrect refactor of variable in claims functionality for exposed fieldsFieldA property of a DataElement expanded to a database column and user interface input element..
  • [NSX-285] Corrected access right for download endpoints.
  • Fixed an issue with next() and prev() functions in Struts2 javascript agent, which did not take into account the 0-based pagination.

Added​

  • Added perform(command) method to Struts2 agent in javascript
  • [NSX-285] Added aggregation access right for all upload or all download endpoints on a DataElement.
  • [NSX-285][NSX-486] Added support for sorting on valuefieldsFieldA property of a DataElement expanded to a database column and user interface input element. in the standard APIStandard API (stdAPI). A fully generated JAX-RS REST API expanding JSON:API compliant endpoints directly from JEE element models..

7.4.2 (2024-06-11)​

Re-release with fix for merge conflict.

7.4.1 (2024-06-11)​

Fixed​

  • [NSX-285] File up- and download endpoints now also marked as producing application/vnd.api+json to return errors.
  • [NSX-285] Added the type of a resource to the resource not found error message.

Changed​

  • [NSX-285] Added Content-Length header for file downloads.
  • Replaced use of deprecated net.democritus.mapping.Base64 class in shared mapper class with java.util.Base64.
  • Replaced usage of applicationInstance.name is several new ExpandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. with application.shortName
  • [NSX-285][NSX-485] When a search fails due to a technical error, there's now a dedicated exception for that.
  • [NSX-285][NSX-485] IllegalStateException exceptions are now caught and returned as an internal server error.

Removed​

  • Removed import for deprecated net.democritus.io.ByteArrayConverter class from ImporterAction.
  • [NSX-285][NSX-485] Removed placeholder OopsSomethingWentWrongException.

7.4.0 (2024-06-10)​

Added​

  • [NSX-285] Implemented StandardApiRootFeature to register JAX-RS providers at applicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution. level.
  • [NSX-285][NSX-423] Implemented file IO connector with up- and download endpoints for file uploads in the context of a specific fieldFieldA property of a DataElement expanded to a database column and user interface input element..

7.3.1 (2024-05-21)​

Fixed​

  • Added missing control.cruds.jaxrs tag to the expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. for DataCommands.

7.3.0 (2024-05-17)​

Added​

  • [NSX-285][NSX-420] Implemented connectors to call commands through the JAX-RS standard APIStandard API (stdAPI). A fully generated JAX-RS REST API expanding JSON:API compliant endpoints directly from JEE element models..
  • Added options projection.projector.provided and projection.projection.provided for DataProjectionsProjectionA tailored subset of fields on a DataElement designed to encapsulate data for a specific technical or functional view.. When added, they disable the standard expansion for the Projector and ProjectionPojo respectively.
  • [NSX-397] Added option 'view.details.excludeId' for DataElement, which hides the id fieldFieldA property of a DataElement expanded to a database column and user interface input element. in the view template.
  • [NSX-397] Added option 'view.details.exclude' for FieldFieldA property of a DataElement expanded to a database column and user interface input element., which hides a fieldFieldA property of a DataElement expanded to a database column and user interface input element. in the view template.

Changed​

  • [NSX-285] Moved registration of API connectors in JAX-RS standard APIStandard API (stdAPI). A fully generated JAX-RS REST API expanding JSON:API compliant endpoints directly from JEE element models. for DataElements/Connectors to feature classes instead of web.xml

Merged​

  • Merged 6.2.6 into master

7.2.0 (2024-05-13)​

Changed​

  • Moved KnockoutToJaxrsClient, JaxRsApplicationActionsJsExpander and JaxRsAgentJsExpander to new knockout-jaxrs-stdapi-expanders resource in web-styles.
  • Split off all expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. related to the standard JAX-RS API into a new jaxrs-standard-api-expanders resource.
  • Moved standalone knockout features to new knockout-ui-addons-expanders resource:
    • BulkDelete
    • Multiselect
    • DefaultValue
    • FormLayoutConfig
    • SearchBar
    • TablePageSize
    • CommandButtons
    • Waterfall

7.1.4 (2024-05-06)​

Merged​

  • Merged 6.2.5 into master

7.1.3 (2024-05-06)​

Merged​

  • Merged 6.2.4 into master
  • Reverted removal of Example2Expander

Changed​

  • Updated dependencies:
    • net.democritus:nsx-jackson-support: 1.0.0 > 1.1.0
    • net.democritus:nsx-jaxrs-jersey-support: 1.1.0 > 1.2.0

7.1.2 (2024-05-03)​

Merged​

  • Merged 6.2.3 into master

Changed​

  • Struts app-actions now maps canAll for DataAccess.

7.1.1 (2024-04-29)​

Fixed​

  • Include source/target properties for compiler plugin alongside release.

7.1.0 (2024-04-29)​

Fixed​

  • Fixed missing imports in Cruds for Ln06 relations.

Changed​

  • [NSX-285] Moved Jersey dependencies into nsx-jaxrs-jersey-support library.
  • [NSX-285][QSEARCH-29] Added feature anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. to route connector.
  • Updated Struts2 from 6.3.0.2 to 6.4.0.
  • Updated ognl:ognl: 3.4.2 -> 3.4.3

7.0.8 (2024-04-19)​

Added​

  • Added session-properties custom anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion. to app-menu

7.0.7 (2024-04-17)​

Changed​

  • Moved Jackson dependencies into nsx-jackson-support library.
  • Tag resolution logging is now optional. Add option expansion.tags.logResolution to expansionSettings to generate log files.

Added​

  • Added custom anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. to app-menu expanderExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact..

7.0.6 (2024-04-09)​

Fixed​

  • [NSX-285][NSX-459] Deny all anonymous access to JAX-RS API unless explicitly allowed.
  • [NSX-285] Handle endpoint not found errors.
  • [NSX-285] Handle unauthorized errors.
  • [NSX-285] Handle method not allowed errors.
  • [NSX-285] Handle method unauthorized errors.

7.0.5 (2024-04-03)​

Added​

  • Added Endpoint for public properties at /api/app/publicProperty. This can be used to retrieve OIDC configuration.
  • Added option experimental.control.web.defaultServlet, which replaces the Struts2 for static files and pages.

Changed​

  • Access-rights now uses app-actions#getDataAccessRights(). JAX-RS implementation is stubbed to show all buttons.

Fixed​

  • [NSX-457] Fixed logout link.
  • Added missing native type for Short type when used with OpenAPI 3.

7.0.4 (2024-03-22)​

Changed​

  • Updated Jersey from 2.41 to 2.42.

7.0.3 (2024-03-21)​

Added​

  • [NSX-285] Added annotation feature anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. to the endpoints for the JAX-RS API.

7.0.2 (2024-03-19)​

Fixed​

  • [NSX-285] Moved all JAX-RS related runtime classes from net.democritus.jaxrs to net.democritus.control.jaxrs to avoid conflicts.

7.0.1 (2024-03-18)​

Fixed​

  • [NSX-453] Added a fix to the Struts2AgentJsExpander so that it can provide 1-based pagination where needed (e.g. with the new pagination in web-styles).

7.0.0 (2024-03-15)​

Added​

  • [NSX-285] New experimental (and unfinished) JAX-RS API to replace Struts2 as the underlying generated API, which can be enabled with the option experimental.control.cruds.jaxrs.
  • [NSX-285] Added expanderExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. for view agent in knockout. This agent can communicate with either Knockout or JAX-RS. In several javascript files, the agent is now instantiated.

Changed​

  • net.palver.navigation.GetMenuAction.findMenu() is now marked private.
  • net.palver.navigation.ApplicationMenuParser.parseComponents2() is now marked private.
  • net.palver.navigation.ApplicationMenuParser.parseComponents2() was renamed to net.palver.navigation.ApplicationMenuParser.parseComponents().

Several ExpandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. have been moved to common:

  • ComponentDefaultTranslationExpander
  • ComponentDutchTranslationExpander
  • ComponentEnglishTranslationExpander
  • ApplicationMenuExpander
  • ComponentMenuExpander

Removed​

  • net.palver.navigation.MenuPartEnum

6.6.1 (2024-03-27)​

Fixed​

  • Fix an issue with #view.list.multiselect tag not being present on DataProjectionsProjectionA tailored subset of fields on a DataElement designed to encapsulate data for a specific technical or functional view.

6.6.0 (2024-03-15)​

Added​

  • Added support for static import in java. Define a static import as <uses type="static" eval="'my.class.myStaticProperty'"/>.
  • Import anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. in templates can now pass parameters to the ImportResolver (@imports(param1, param2=value, param3=otherValue))
  • Usage statements can now have a type, as seen with the static imports above.
  • ExpanderRelocation DataResources can now be used to describe an ExpanderExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. that moved to a new location. Features will be redirected to the new location. Harvest files will also be remapped if they still use the old artifactArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project. path.

Removed​

  • Removed implementation for expired option legacy.maven.logicLayer.includeDataTestSources.
  • Removed implementation for expired option legacy.noTaskPerform.reenable.
  • Removed implementation for expired option showLinkDetails.
  • Removed implementation for expired option vega.transient.taskBean.mImplementation.

6.5.0 (2024-02-02)​

Fixed​

  • [NSX-424] Fix change in war pom.xml causing the view/ext/common directory to be ignored
  • [NSX-412] The id of a details object is now always set to 0L at the start of the create method in the Cruds class to fix issues with the value being null. There is a legacy option legacy.cruds.disableId0OnCreate in case this somehow breaks custom code.

Changed​

  • The option maven.groupId is now automatically added if it is not defined, with the expected default value, so it is always present.

Removed​

  • Removed implementation for expired option legacy.dynamicTaskDelegation.reenable.

6.4.4 (2024-01-25)​

Fixed​

  • In tests for non-applicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution. programs, technologies are now all provided to the programComposite. This should fix some issues with layerImplementations in tests

6.4.3 (2024-01-25)​

Fixed​

  • When using the default groupId that contains the name of the applicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution., dashes are now removed if they are part of the applicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution. name..

6.4.2 (2024-01-22)​

Fixed​

  • Fixed condition of ExporterAction, which didn't work correctly after introducing tags.

6.4.1 (2024-01-16)​

Added​

  • ProgramExpansionContext and ModuleExpansionContext now have a list of LayerImplementations that are applicable.
  • Added tags for bean interfaces.

Removed​

  • Removed LayerImplementationHelper.

Changed​

  • If a condition of a LayerImplementation returns null, this is now interpreted as false instead of throwing an exception.

6.4.0 (2024-01-09)​

Added​

  • Added .kebabCase (in addition to .kebab) as an ognl String attribute for consistency with other casings.
  • Added kebabCase format and .asKebabCase string attribute support to stringtemplates.
  • Added support for tags. Tags can be supplied by tag-rules. ExpandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact., features and expansionSteps will only be enabled if all defined tags are present.

Changed​

  • Updated a number of expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. and features to use tags

6.3.0 (2024-01-03)​

Merged 5.38.1 into main branch.

Removed​

6.2.8 (2024-08-12)​

Added​

  • [VEGA-373] Added custom anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion. for maven surefire plugin configuration. (cherry-picked from 7.7.2)

Fixed​

  • [NSX-454][VEGA-382] Fixed issues with null values in UniqueConstraint query. (cherry-picked from 7.7.2)

6.2.7 (2024-06-17)​

Fixed​

  • [VEGA-379] Fixed issue in UniqueConstraint database query where ValueFieldType wrapper classes were not unwrapped.

6.2.6 (2024-05-16)​

Fixed​

  • [VEGA-377] Fix class names for StrutsValidator/Converter classes of ValueFieldTypes where the name differs from the ValueClass
  • [VEGA-375] Add userContext constructors to agents classes

6.2.5 (2024-05-06)​

Changed​

  • agentRepository.enable is no longer cascading, since cascading from applicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution. to component doesn't work yet in this prime-core version.

6.2.4 (2024-05-06)​

Reverted​

  • [VEGA-375] Reverted change which removes ComponentProxyAgentsExpander. It is now available with the option agentRepository.enable.

Changed​

  • [VEGA-370][VEGA-367][VEGA-368] Created alias common.name.alwaysPresent for option legacy.nameNotWanted.pojoName. This option ensures the name fieldFieldA property of a DataElement expanded to a database column and user interface input element. is always present, even with the nameNotWanted option. This ensures the behavior is the same as before version 5.9.2.
  • [VEGA-375] The option agentRepository.enable now also adds the AgentIf interface to the Agent class in the Proxy layerLayerLogical separation of functionality within a single system/application, focused on code organization. to prevent compile errors.

[VEGA-370][VEGA-375][VEGA-376] Removed the deadline for following options:

  • agentRepository.enable/legacy.agentRepository.enable
  • common.name.alwaysPresent/legacy.nameNotWanted.pojoName
  • legacy.proxyAgentInterface.reenable
  • legacy.dynamicTaskDelegation.reenable

Though they will still generate deprecation warnings. In addition, these options, except for agentRepository.enable, are now cascading, hence it is possible to only add the option where the problem occurs.

6.2.3 (2024-05-03)​

Changed​

  • [VEGA-376] TaskBean delegation is now part of the TaskElement BeanExpander and includes an @anchor:implementation feature anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion..
  • [VEGA-375] Created alias agentRepository.enable for option legacy.agentRepository.enable.

Reverted​

  • [VEGA-375] Reverted change which removes ComponentLocalAgentsExpander. It is now possible to enable the expanderExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. by adding the option agentRepository.enable to a Component or ApplicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution..

6.2.2 (2023-12-15)​

Fixed​

  • Added fallback in ArtifactExpander for ExpanderComposites without ElementType. This should fix some issues with backwards compatibility.
  • Fixed issue that caused the ExpanderExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. Mapping to still be resolved for Features with option feature.mapping.doNotInheritExpanderMapping, sometimes causing assert errors.

6.2.1 (2023-12-15)​

Fixed​

  • Rework of audit fieldsFieldA property of a DataElement expanded to a database column and user interface input element. no longer updated modification fieldsFieldA property of a DataElement expanded to a database column and user interface input element. on create.

6.2.0 (2023-12-14)​

Fixed​

  • Fixed issue in AdditionalExpansionStep tests not resolving ExpandableElement correctly.

Changed​

  • [NSX-398] Introduced options and cleaned implementation/features for existing auditing functionality with fieldsFieldA property of a DataElement expanded to a database column and user interface input element. such as enteredAt. These are still implicitly added based on the name, but can also be explicitly defined on other fieldsFieldA property of a DataElement expanded to a database column and user interface input element. instead. The new options introduced match the following fieldsFieldA property of a DataElement expanded to a database column and user interface input element.:
    • enteredAt: option audit.create.timestamp
    • enteredBy: option audit.create.author
    • lastModifiedAt: option audit.modify.timestamp
    • lastModifiedBy: option audit.modify.author

6.1.0 (2023-12-12)​

Changed​

  • Change ArtifactExpander to use ExpandableElement when validating expansionSource.
  • Change ModelBuilderFactory to use ExpandableElement when resolving element hierarchy.
  • Updated Struts2 from 6.3.0.1 to 6.3.0.2. (Addresses CVE-2023-50164)

Fixed​

  • [VEGA-360] Fix struts-conversion properties file for ValueFieldTypes with name that differ from the valueClass fieldFieldA property of a DataElement expanded to a database column and user interface input element..

Removed​

  • Removed support for expired legacy option legacy.dataDetailedConstructor.reenable.

6.0.2 (2023-11-16)​

Reverted​

  • Returned linkFieldTypes data-resource, since the micro-radiant can still have issues loading the model because of this change. Will be removed again once the micro-radiant is updated.

6.0.1 (2023-11-15)​

Changed​

  • Deprecated option legacy.nameNotWanted.pojoName.

Removed​

  • [VEGA-358] Removed linkFieldTypes data-resource, since it is now defined in prime-core

6.0.0 (2023-11-09)​

Fixed​

  • Fixed implementation of file comparison for copying files from expansion resourcesExpansion Resource (ExpansionResource). A reusable resource bundle containing expanders and features that provide specific application capabilities, defined in the expansion settings and added to the classpath during expansion.. The update to commons-io version 2.15.0 changed its file comparison implementation, which broke it for virtual file systemsSystemA set of interconnected components that work together to achieve a specific purpose or function..

Added​

  • Added deprecation warnings in Maven build by default. Can be disabled with maven.hideDeprecationWarnings.

Changed​

  • The expanderExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. framework now targets Java 17. (Expanded code for the JEE applicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution. stack is still Java 8 compatible.)
  • Refactored up various deprecated calls to reduce deprecation warnings.

5.39.0 (2023-11-08)​

Added​

  • Added interfaces feature anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. to the Agent- and LocalAgentExpandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact.
  • Added execute-before feature anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. to several struts actions

Fixed​

  • [VEGA-351] Moved <finalName> in ear pom.xml to <build> tag (see https://issues.apache.org/jira/browse/MEAR-260)
  • [VEGA-349] StrutsConverter and StrutsValidator classes are now correctly expanded even if a custom converter and/or validator have been defined on the ValueFieldType.

Changed​

  • Replaced use of AgentIf interfaces in FinderResolvers

Moved the expiration times of some options which were set to expire too far in the future for some reason:

  • disableStrictLinkMode: 2024-09-01 to 2024-05-01
  • disableFixNullableLn02: 2024-09-01 to 2024-05-01
  • logging.cruds.degradeErrorToInfo: 2024-12-01 to 2024-05-01
  • legacy.struts.unprotectedEndpoints: 2024-12-01 to 2024-05-01

Removed​

  • [VEGA-356] Removed the AgentIf interface from the Agent class. This can be reverted with the option legacy.proxyAgentInterface.reenable.

5.38.0 (2023-10-26)​

Fixed​

  • [NSX-381] FinderResolver did not process IN fieldFieldA property of a DataElement expanded to a database column and user interface input element. operator pairs for collection linkfieldsFieldA property of a DataElement expanded to a database column and user interface input element. correctly when null was passed for that pair.

Added​

  • Added a debugger entrypoint to the ConfigObjectMapper, allowing debuggers to attach to the mapping context.
  • Added option for Features, feature.mapping.doNotInheritExpanderMapping. This disables the inheriting of mapping values from the ExpanderExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. mapping file. It makes it easier to decouple the Feature. It also prevents issues in the tests caused by changes in the ExpanderExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. mapping file.
  • Feature Composites in Tests are now enriched, so that options on Features can be used. Note that the use of these options are reserved for logic provided by expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact.-core.

Removed​

  • Removed TechnologyMapping class.
  • Removed LayerConditionIsApplicable class.

5.37.5 (2023-10-20)​

Changed​

  • Migrated all imports for BeanExpander to the new imports systemSystemA set of interconnected components that work together to achieve a specific purpose or function..

5.37.4 (2023-10-18)​

Merged 5.30.8 into main branch.

Fixed​

  • Modules imported from model-resources are no longer harvested, even without the isBaseComponent option.

5.37.3 (2023-10-15)​

Fixed​

  • Null/Notnull fieldFieldA property of a DataElement expanded to a database column and user interface input element. operator pairs were not filtered correctly from FinderResolvers in cases where they were paired up with fieldFieldA property of a DataElement expanded to a database column and user interface input element. operator pairs that did need to be resolved.

5.37.2 (2023-10-13)​

Fixed​

  • Added import that is needed for required feature after refactoring of imports for Cruds.

5.37.1 (2023-10-12)​

Fixed​

  • Missed refactoring of imports for AgentInterfaceExpander.

5.37.0 (2023-10-12)​

Changed​

  • Migrated many large expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. to the new import systemSystemA set of interconnected components that work together to achieve a specific purpose or function. for expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact., to allow expanderExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. features to make use of it.

Removed​

  • Removed support for deprecated option experimental.valueFieldType.storageType.
  • Removed support for deprecated option legacy.logic.entityManager.

5.36.7 (2023-10-09)​

Merged​

  • Merged 5.30.7 into main.

5.36.6 (2023-10-06)​

Fixed​

  • With changes to the way imports are added, the option useLogicSecurity expanded code that was missing an import in scenarios where a DataElement had no DataCommands.

5.36.5 (2023-10-04)​

Fixed​

  • HSTSFilter was not registered correctly in some cases due to a mismatch in the package name generated for the class and its registration in web.xml.

Changed​

  • Replaced uses of deprecated methods in expanderExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. templates:
    • net.palver.util.StringUtil.join()
    • net.palver.util.StringUtil.split()

Merged​

  • Merged 5.30.6 into main.

5.36.4 (2023-09-27)​

Fixed​

  • [NSX-373] Fixed duplicate custom anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion. anchor:custom-delete-instance-button, replacing it with anchor:custom-delete-list-button for the bulk-delete button.

5.36.3 (2023-09-26)​

Fixed​

  • Fixed an issue when loading Components in a non-ApplicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution. program.

5.36.2 (2023-09-26)​

Fixed​

  • Fixed an issue where cruds.bulk.delete would only work if the option view.list.multiselect is added. The option should have been provided automatically.
  • Revert imports in knockout artifactsArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project. to use let instead of const, because this was breaking too much custom code.

5.36.1 (2023-09-23)​

Fixed​

  • Fixed db.schema and db.tableName to correctly apply alias for old naming.

5.36.0 (2023-09-22)​

Added​

  • Added model loading listener to consolidate database schema and table name options, replacing behavior from prime-core.
  • Added documentation link to all optionTypes documented on foundation.

Changed​

  • Renamed options, old name is available as an alias:
    • db.schema, previously databaseSchemaName
    • db.tableName, previously databaseTableName
  • In addition, made db.schema cascading. It can now also be applied to components.
  • Deprecated options which had very similar behavior to other options:
    • hasDataSchemaName
    • hasDataBaseSchema
    • hasDataTableName
  • Updated prime-core to 2023.8.0

5.35.1 (2023-09-22)​

Fixed​

  • Updated expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. for options, so they correctly works on ApplicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution. and not just ApplicationInstance:
    • security.hstsHeader
    • experimental.maven.speedOverSize
    • cruds.bulk.delete
    • view.list.multiselect
    • cruds.softDeleteOnModify
    • struts.disableStrutsErrorsToCommandResult
    • struts.unauthorized
  • Fixed dependency on snapshot build.

Added​

  • Added pascalCase format and toPascalCase string property to ST4 templating engine.
  • Added pascalCase format to OGNL expression engine.

Changed​

  • Updated options to use cascading functionality of OptionType:
    • cruds.table.pageSize
    • cruds.table.csvExportButton

5.35.0 (2023-09-21)​

Fixed​

  • Changed groupId of every Maven module to org.normalizedsystems.<Application.shortName> by default to avoid collisions between projects.

Added​

  • Added option maven.groupId to set the groupId for all Maven modules in the project.

5.34.1 (2023-09-21)​

Fixed​

  • Fixed issue in InstanceModelJsExpander that caused ln03 fieldsFieldA property of a DataElement expanded to a database column and user interface input element. to be initialized incorrectly.
  • Reverted change in CreateDialogJsExpander and EditDialogJsExpander that changed the form variable to a const. This was incompatible with custom code in some places, e.g. the assets component.

5.34.0 (2023-09-19)​

Added​

  • Added ApplicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution. option ejb.logic.dataSourcesFix. This changes the logic layerLayerLogical separation of functionality within a single system/application, focused on code organization. build to use the maven-assembly-plugin to include class files from the data layerLayerLogical separation of functionality within a single system/application, focused on code organization. instead including the source directories directly. This prevents the same source files from being compiled twice. It also fixes issues IntelliJ has with the multi-module project.

Fixed​

  • Fixed mapping that still using the DataRef(String) constructor.

Changed​

  • Updated Struts2 from 6.3.0 to 6.3.0.1.
  • Marked option finders.enableTypedFinders as redundant.

5.33.2 (2023-09-18)​

Fixed​

  • [NSX-372] Fixed imports for Ln03 ConnectorFieldsFieldA property of a DataElement expanded to a database column and user interface input element. in CommandPojoExpander

5.33.1 (2023-09-12)​

Fixed​

  • Replaced a left-over use in the Cruds class of new DataRef(Long) when using Ln05 fieldsFieldA property of a DataElement expanded to a database column and user interface input element..

5.33.0 (2023-09-11)​

Added​

Added new syntax to mapping files (use xmlns="https://schemas.normalizedsystems.org/xsd/expanders/2023/1/0/mapping")

  • A new syntax has been added to simplify imports First, add an artifactArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project. definition. It defines the current artifactArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project. location and import resolution strategy. 
    <artifact this="dataElement.qualifiedName + 'Bean'" importStrategy="java"/>
    Next, add uses statements to start adding imports. These statements can be interleaved with list and group statements. 
    <uses eval="'jakarta.ejb.Stateless'"/>
    In the template, add @imports to insert the imports.
  • group statements will now insert a null value in the model if their condition returns false and no other value with that name exists. The previous behaviour was to skip this value entirely. The result is that you can now use <if(group)> in the templates, even at root level.

Added 2 ArtifactImportStrategies, which can be selected in the artifactArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project. definition in the mapping file:

  • java: resolves imports for java files. Includes filters for duplicates, java.lang classes and same package.
  • AMD: resolves imports for AMD styles js modules. The @imports line will be replaced with define([...], function(...) {.

Changed​

  • Marked methods for deprecation:
    • Bean.getDataRef(Long)
    • Bean.getDetails(Long)
    • Bean.getDetails(DataRef)
  • Refactored various uses of deprecated methods of ParameterContext.
  • In many places, the imports of files have been streamlined to reduce the number of redundant imports. This can mean that will need to add an import with custom code if the code made use of the import.
  • All struts endpoints in the nsx-json-application now require authentication.
  • Updated Struts2 from 6.2.0 to 6.3.0.
  • All expansion runners were refactored to implemented Consumable<T> instead of IExecutor<T>:
    • AdditionalExpansionStepRunner
    • ArtifactExpanderRunner
    • ArtifactHarvester
  • Marked net.democritus.acl.struts2.UserContextRetriever as final.

Removed​

  • Removed all uses of ParameterContextFactory. The option legacy.parameterContextFactory.enable can temporarily be added on the ApplicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution. to re-enable it. (Expires 2024-03-01)
  • Removed Bean.getInfo(Long). (Deprecated since 2019-03-11)
  • Removed {Component}Agents classes. The option legacy.agentRepository.enable can temporarily be added on the ApplicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution. to re-enable it. (Expires 2024-03-01)
  • Removed option expanders.mappingReader.useSingleEqualsComparator, which was part of the original experimental mapping setup and not used anywhere.
  • Removed options disableStrictLinkMode and disableFixNullableLn02. These options had been added in version 4.0.1 to remain backwards compatible, but have now been officially removed.
  • Removed expired option experimental.openjpa.CharacterColumnSize.
  • Removed expired option legacy.cruds.getProjection.emptyOnError.
  • Removed expired option legacy.projectionDetailedConstructor.reenable.
  • Removed deprecated method ExpansionJobManager.runForAll(). (Deprecated since 2022-02-21)

5.32.1 (2023-08-29)​

Changed​

  • Pushed back the expiration date of the option showLinkDetails by 3 months to 2024-01-01.

5.32.0 (2023-08-28)​

Added​

  • Added FinderResolver class, which is called from the logic bean find() method to resolve the DataRefs for fieldsFieldA property of a DataElement expanded to a database column and user interface input element. in FieldOperatorPairs, so it is not required for the database identifier to be in the DataRef ahead of calling find().

Changed​

  • Updated ognl:ognl: 3.3.4 -> 3.4.2
  • Typed findersFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement. are now enabled by default. The option legacy.typedFinders.disable can temporarily be added on the ApplicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution. to disable this behavior. (Expires 2024-03-01)
  • Moved maven-surefire-plugin to plugin management in root POM, as it is included by default by Maven.
  • Marked methods as deprecated for removal:
    • Agent.getDataRef(Long)
    • Agent.getInfo(Long)
    • Agent.getDetails_old(Long)
    • Agent.getDetails(Long)
  • [NSX-215] Agent.getDetails(DataRef) now calls getProjection() so it is consistent with the implementation in LocalAgent, which works with an unresolved DataRef.
  • Moved IParamTargetValueProvider from nsx-runtime to application-shared-struts2.
  • Updated nsx-runtime: 2023.5.0 -> 2023.6.1

Removed​

  • The option finders.enableTypedFinders was removed as it is now the default behavior.
  • [NSX-323] Removed deprecated constructors LocalAgent(Local, UserContext) and LocalAgent(Local, UserContext, Context).
  • [NSX-323] Removed deprecated method LocalAgent.getDataElementAgent(UserContext). (Deprecated since 2019-03-20)
  • [NSX-323] Removed deprecated fieldFieldA property of a DataElement expanded to a database column and user interface input element. LocalAgent.userContext.
  • [NSX-323] Removed deprecated constructor Agent(Local, UserContext).
  • [NSX-323] Removed deprecated method Agent.getDataElementAgent(UserContext). (Deprecated since 2019-03-20)
  • [NSX-323] Removed deprecated method Agent.getDataElementAgent(). (Deprecated since 2019-01-18)
  • [NSX-323] Removed deprecated method Agent.getUserContext().
  • [NSX-323] Removed deprecated fieldFieldA property of a DataElement expanded to a database column and user interface input element. Agent.mUserContext.
  • [NSX-323] Removed deprecated constructor Agents(UserContext).
  • [NSX-323] Removed deprecated method Agents.getDataElementLocalAgents(UserContext). (Deprecated since 2019-04-02)
  • [NSX-323] Removed deprecated constructor ProxyAgents(UserContext).
  • [NSX-323] Removed deprecated method ProxyAgents.getDataElementAgents(UserContext). (Deprecated since 2019-04-02)
  • [NSX-323] Removed deprecated method CommandPerformer.getUserContext(). (Deprecated since 2022-03-16)
  • [NSX-323] Removed deprecated method CommandPreparer.getUserContext(). (Deprecated since 2022-03-16)
  • [NSX-323] Removed deprecated method DetailsPreparer.getUserContext(). (Deprecated since 2022-03-16)
  • [NSX-323] Removed deprecated method FindAction.getUserContext(). (Deprecated since 2022-03-16)
  • [NSX-323] Removed deprecated method ModifyAction.getUserContext(). (Deprecated since 2022-03-16)
  • [NSX-323] Removed deprecated method ProjectorAction.getUserContext(). (Deprecated since 2022-03-16)
  • [NSX-323] Removed imports for net.democritus.sys.UserContext. Should be added by custom code if needed:
    • Agent class
    • Agents interface
    • CommandPerformer class
    • CommandPreparer class
    • DetailsPreparer class
    • FindAction class
    • LocalAgent class
    • LocalAgents class
    • ModifyAction class
    • ProjectorAction class
    • ProxyAgents class
  • [NSX-323] Removed imports for net.democritus.acl.struts2.UserContextRetriever where relevant. ContextRetriever should be used instead.

5.31.0 (2023-08-08)​

Added​

  • Added feature anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. *-<field>-after to command forms, tables and detail views.

5.30.8 (2023-10-17)​

Merged 5.24.0.4 into 5.30.x branch.

5.30.7 (2023-10-09)​

  • [VEGA-345] Extend legacy.dynamicTaskDelegation.reenable to 2024-04-01.

5.30.6 (2023-10-04)​

Merged 5.24.0.3 into 5.30.x branch.

Merged​

  • [VEGA-334] Added options jpa.column.disableInsert and jpa.column.disableUpdate to add insertable = false and/or updatable = false to the @Column annotation of a fieldFieldA property of a DataElement expanded to a database column and user interface input element. in the Data class.
  • [VEGA-332] Removed regex validation for option isLinkDriver.

5.30.5 (2023-08-01)​

Merged​

Merged 5.24.0.2 into main.

Temporary fix for struts validators. The name of the validator is defined by the ValueFieldType fullType. There was an attempt to change this to the name of the type instead, but this causes a conflict between validation::Email and the struts email type.

5.30.4 (2023-07-26)​

Fixed​

  • Option vega.transient.taskBean.mImplementation did not get through the model loading process as it was not marked as applicable to ApplicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution..

Changed​

  • The test sources and resources for the data layerLayerLogical separation of functionality within a single system/application, focused on code organization. are no longer included in the build of the logic layerLayerLogical separation of functionality within a single system/application, focused on code organization.. This behavior can temporarily be re-enabled using the legacy option legacy.maven.logicLayer.includeDataTestSources, which will expire on 2024-01-01.

Removed​

  • Marked option experimental.maven.logicLayer.noDataTestSources as expired legacy option.

5.30.3 (2023-07-19)​

Fixed​

  • Changed names of CSP interceptors in Struts following a breaking change in Struts 6.2.0. Listed in bugfix issue WW-5263.

5.30.2 (2023-07-18)​

Fixed​

  • Removed remaining imports for net.palver.Options.Option in:
    • CommandPreparer
    • DetailsPreparer

Changed​

  • Refactored some code in the expansion framework to use Optional instead of Option.
  • ApplicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution. menu files for applicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution. are now read as UTF-8 encoded files.

Removed​

  • Removed deprecated method ApplicationMenuResolver.getApplicationNavigation(). (Has been deprecated for two years.)

5.30.1 (2023-07-13)​

Changed​

  • Legacy option legacy.dynamicTaskDelegation.reenable now includes the new switch-case to allow for a better migration path.

5.30.0 (2023-07-12)​

Added​

  • Added temporary deprecated method Optional<String> some(String) to the Cruds class, for backwards compatibility of the getCustomDisplayName() method. This method will be removed in the future, but this will allow some time to transition the implementation of that method to use Optional.of() instead of some().

Changed​

  • Replaced the Options.Option return type of private methods with Optional in several expanded Struts actions:
    • <dataElement>ExporterAction
    • <dataElement>FindAction
    • <dataElement>ModifyAction
  • Changed the return type of <component>ApplicationSettings.getProperty(String) from Options.Option to Optional.

Removed​

  • Removed imports for Options.Option in Cruds and Bean classes. (If they are still in use by custom code, either immediately refactor to java.util.Optional, or add the imports in custom anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion..)

5.29.0 (2023-07-11)​

Fixed​

  • Fixed link to struts dtd file in all struts XML files, as it was still targeting http instead of https.

Changed​

  • Updated Struts2 from 6.1.2.1 to 6.2.0.

Removed​

  • Removed all supporting code and expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. for Struts2 versions 2.3 and 2.5, given that the option struts.version has expired on July 1st.
  • The net.democritus.utils.action.StrutsParameterRetriever class was removed, as it was only used in base-components.

5.28.1 (2023-06-30)​

Fixed​

  • Fixed StrutsValidatorXmlExpander for ValueFieldTypes where the fullType starts with uppercase. The validators will now be registered with the first letter in lowercase.

5.28.0 (2023-06-30)​

Added​

  • Added support for TaskOutcomes, expands an enum as return type.
  • Added noDelegation TaskElement option to opt-out of Task delegation.
  • Added Legacy options to revert to old Task behavior:
    • legacy.dynamicTaskDelegation.reenable to keep dynamic task implementation lookup and Impl2 class.
    • legacy.noTaskPerform.reenable to disable the default perform method on tasks.
  • Added snake_case formatting attributes for expanderExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. mapping and templates.

Changed​

  • Task implementation lookup is no longer dynamic (Class.forName) and instead uses a switch with all known implementation classes.
  • Deprecated the following options, these are now default behavior:
    • includePerform TaskElement option (expires 01-01-2024)
    • includeDelegation TaskElement option (expires 01-01-2024)

Removed​

  • Removed Example2Expander for the <TaskElement>Impl2 class (unless legacy option is used).

Fixed​

  • Fixed typo in optionType restriction.translation.en.

5.27.1 (2023-06-27)​

Fixed​

  • Replaced some leftover uses of Context.getContext() to Context.find().

5.27.0 (2023-06-26)​

Changed​

  • Updated nsx-runtime: 2023.3.1 > 2023.4.0
  • Replaced SearchResult.getFirst() with SearchResult.getFirstResult() in expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact..

5.26.1 (2023-06-22)​

Added​

  • Added js-to-model, model-to-js, before feature anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. to FinderMapperExpandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact.

5.26.0 (2023-06-19)​

Fixed​

  • Fixed packageName for HstsFilter in struts-header if applicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution. shortname starts with uppercase (not recommended).

Added​

  • Added form-field-<field.name>-after feature anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion. to InstanceFormHtmlExpander
  • Improved mapping scope trace for helper classes
  • Defined restriction.translation.(nl|en) optionTypes

Changed​

  • Replaced the use of net.democritus.sys.Context.getContext() with net.democritus.sys.Context.find() in much of the expansion framework.
  • Replaced the use of net.democritus.sys.Options.Option with java.util.Optional in much of the expansion framework.
  • Refactoring to java.util.Optional in some expanded code where it cannot impact any custom code.
  • Added UTF-8 sourceEncoding for expanded maven projects.

Removed​

  • Removed undocumented legacy mindmap functionality from the stack. This includes all code under net.palver.mindmap and the struts action GetMindmapAction.

5.25.1 (2023-06-14)​

Changed​

  • Updated Struts2 from 6.1.2 to 6.1.2.1. (Addresses CVE-2023-34149 and CVE-2023-34396)

5.25.0 (2023-06-13)​

Fixed​

  • Fixed issue with nullable fieldFieldA property of a DataElement expanded to a database column and user interface input element. operators not handling the 0L (invalid dataRef) case for Ln02
  • Fixed FileNotFoundException for ehcache configuration file on TOMEE applicationServer
  • Fixed ExpanderTester so that the ExpansionContext contains the MappingContext and DataRegistry of the TestModelBuilder.

Changed​

  • Updated nsx-runtime: 2023.1.1 > 2023.2.1
  • Deprecated option experimental.openjpa.CharacterColumnSize. Will be removed on 2023-09-01.

5.24.1 (2023-06-06)​

  • Erroneous release

5.24.0.4 (2023-10-17)​

Changed​

  • [VEGA-348] (Backport 5.32.0) Pushed back the expiration date of the option showLinkDetails by 3 months to 2024-01-01.

5.24.0.3 (2023-09-11)​

Added​

  • [VEGA-334] Added options jpa.column.disableInsert and jpa.column.disableUpdate to add insertable = false and/or updatable = false to the @Column annotation of a fieldFieldA property of a DataElement expanded to a database column and user interface input element. in the Data class.
  • [VEGA-332] Removed regex validation for option isLinkDriver.

5.24.0.2 (2023-07-31)​

Fixed​

  • Temporary fix for struts validators. The name of the validator is defined by the ValueFieldType fullType. There was an attempt to change this to the name of the type instead, but this causes a conflict between validation::Email and the struts email type.

5.24.0.1 (2023-07-20)​

Fixed​

  • (Backport 5.25.1) Updated Struts2 from 6.1.2 to 6.1.2.1. (Addresses CVE-2023-34149 and CVE-2023-34396)
  • (Backport 5.28.1) Fixed StrutsValidatorXmlExpander for ValueFieldTypes where the fullType starts with uppercase. The validators will now be registered with the first letter in lowercase.

Changed​

  • Updated prime-core to version 2023.4.0 to be in line with nsx-default-stack version 2023.9.0 and resolve issue with struts.version option expiration.

5.24.0 (2023-05-31)​

Changed​

  • Marked options as deprecated:
    • Valid until 2023-12-01:
      • ejb3.useEjbInControl

Removed​

  • Removed secondary constructor in data pojo. (Re-enable with option legacy.dataDetailedConstructor.reenable until 2023-12-01)

Added​

  • Added SCM information to deployed pom.xml artifactsArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project.

5.23.2 (2023-05-24)​

Fixed​

  • Fixed issue in EntererValidationXmlExpander that included calculated fieldsFieldA property of a DataElement expanded to a database column and user interface input element. in fieldsFieldA property of a DataElement expanded to a database column and user interface input element. to validate.

5.23.1 (2023-05-24)​

Fixed​

  • Removed jetty-schemas dependency from pom file for war module, as it is no longer being provided by prime-data.

5.23.0 (2023-05-23)​

Fixed​

  • Expand correct XML header depending on JEE version set in technical infrastructure.

Changed​

  • Use version 8.0.1 of javaee-api when targeting JEE 8 (instead of 8.0).

Removed​

  • All remaining legacy code targeting EJB2 has been removed following the same update of prime-data.

5.22.8 (2023-05-23)​

Added​

  • Added feature anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. around default implementation of id-accessors in DataExpander

Changed​

  • Added @Deprecated annotation to removed secondary constructor in data pojo.

5.22.7 (2023-05-17)​

Changed​

  • Removed restrictions from fieldsFieldA property of a DataElement expanded to a database column and user interface input element. in finderFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement. forms.
  • Reverted ComponentMetadata to use the name of the ValueFieldType of FieldsFieldA property of a DataElement expanded to a database column and user interface input element., since generic code in projects is making use of this.

5.22.6 (2023-05-11)​

Changed​

  • Updated org.hibernate:hibernate-core: 5.4.32.Final > 5.6.15.Final (applies only to l2 caching)
  • Updated net.democritus.metamodels:prime-core: 2023.2.1 > 2023.2.3

Added​

  • Added before-find and after-find feature anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. to BeanExpander

Fixed​

  • Fixed package of HstsFilter for ApplicationsApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution. where shortName is not camelcase.
  • Fixed default sorting always being name
  • Fixed casing of the bean variable in LogicValidator

5.22.5 (2023-04-27)​

Fixed​

  • Fixed JPA constraints failing on empty Strings for nullable ValueTypes
  • Fixed some mismatched translation keys for validations

5.22.4 (2023-04-27)​

Fixed​

  • Fixed StringLength and StringPattern failing on empty or null Strings

5.22.3 (2023-04-27)​

Fixed​

  • Fixed NumberBounds validations in shared validator to correctly implement includeMin/Max

5.22.2 (2023-04-21)​

Fixed​

  • Changed Hyperlink form fieldFieldA property of a DataElement expanded to a database column and user interface input element. to text input

5.22.1 (2023-04-20)​

Fixed​

  • Added missing Password ValueType
  • Added missing java.util.Date imports for validations of future/past restrictions

5.22.0 (2023-04-20)​

caution

As part of our initiative to modernise existing APIs, we have started replacing net.palver.util.Options.Option with java.util.Optional in this release. As a result, there are some breaking changes. We are rolling out these changes in stages to minimize the impact.

Changed​

  • Updated nsx-runtime: 2023.0.0 > 2023.1.0
  • Changes for compatibility with breaking changes in nsx-runtime.

Removed​

  • Removed options that expired on 2023-04-07:
    • legacy.editorconfig.disabled
    • legacy.valueFieldType.hashCodeMethod.disable

Fixed​

  • Fixed issue with file fieldsFieldA property of a DataElement expanded to a database column and user interface input element. because of a missing template in the finderFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement. forms

5.21.1 (2023-04-14)​

Fixed​

  • Added missing closing bracket to NotNull validation

5.21.0 (2023-04-13)​

Added​

  • Added support for ArtifactListeners. Register an ArtifactListener data-resource and provide an implementation that implements the ArtifactListener interface.

Fixed​

  • Fixed logger name in logic validator bean
  • Fixed custom-restriction validations not being inserted into the ValidatorBean

5.20.4 (2023-04-12)​

Added​

  • Added option jpa.columnDefinition for SimpleValueTypes. You can add this to provide a columnDefinition to all fieldsFieldA property of a DataElement expanded to a database column and user interface input element. of that type.
  • Added Text ValueType, which can be used for unlimited Strings

5.20.3 (2023-04-11)​

Fixed​

  • Added support for Short ValueType

Removed​

Removed expired legacy options:

  • legacy.vectorCollectionType.reenable
  • legacy.multilingual.enable
  • legacy.ui.rootPages.reenable
  • jpa.optimization.skipDataQuery.disable

5.20.2 (2023-04-06)​

Fixed​

  • Fix getStatusAsEnum() appearing in projectionsProjectionA tailored subset of fields on a DataElement designed to encapsulate data for a specific technical or functional view. not including the status fieldFieldA property of a DataElement expanded to a database column and user interface input element.

5.20.1 (2023-04-03)​

Fixed​

  • Fixed html form template for textarea fieldsFieldA property of a DataElement expanded to a database column and user interface input element.

5.20.0 (2023-04-03)​

Changed​

  • Reimplemented ValueFieldTypes. Types of ValueFieldsFieldA property of a DataElement expanded to a database column and user interface input element. are now defined by ValueField::type.

Fixed​

  • Removed model-transmutations dependency, which was causing dependency issues in tests of projects depending on ExpandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact..

Removed​

  • Removed special case for DB2 that set the maximum length of big strings to 4000.
  • Projects should now use a specialized ValueType or add a StringLength restriction to BigString with a separate expansion-resource.
  • Removed several unused imports in BeanExpander.
  • Moved Upgrade transmutation to prime-transmutations.
  • Removed deprecated net.democritus.expander.CustomAnchorConstants class that was left over from old expansion framework.
  • Removed deprecated instantiation of SearchResult.SearchError.

5.19.6 (2023-03-23)​

Fixed​

  • Fixed UniqueConstraint query for Ln01 fieldsFieldA property of a DataElement expanded to a database column and user interface input element..

5.19.5 (2023-03-21)​

Changed​

  • Updated Struts2 from 6.1.1 to 6.1.2. (Addresses CVE-2023-24998 in commons-fileupload)

5.19.4 (2023-03-16)​

Added​

  • Added feature anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. to replace the default implementation of a FinderFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement. in the FinderBean.

Feature AnchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion.:

  • Feature anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. can now be placed within the default content of another Feature anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion. (in the same ExpanderExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact.). Note that this does not support feature anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. within a feature.

Fixed​

  • Fixed typing of fetchData(ParameterContext, QueryBuilder) method in FinderBean. The method can now be called without requiring type conversion. This also removes the need for many of the SuppressWarning annotations in the class.
  • Fixed createOrModify() not working with UniqueConstraint/uniqueKey

Fixed a mistake in the deadlines for legacy options.

  • Deadline of experimental.cruds.failOnProjectionNotFound is set to 2023-06-15
  • Deadline of legacy.projectionDetailedConstructor.reenable is set to 2023-09-01

Changed​

  • application-shared-struts2:
    • Rewrote net.democritus.security.action.NonceBuilder.getRandomString() to use SecureRandom and not depend on commons-lang3.
    • Now logging exceptions for methods in net.democritus.json.NullHandlingJsonPopulator as error instead of just printing stack traces.
    • Now logging exceptions for methods in net.palver.struts2.action.DownloadAction as error instead of just printing stack traces.
  • Added @Deprecated annotation to removed secondary constructor in projectionProjectionA tailored subset of fields on a DataElement designed to encapsulate data for a specific technical or functional view. pojo.
  • entityManager in FinderBean is now final.
  • Option showLinkDetails is now marked as legacy. (expiry on 2023-09-01)

5.19.3 (2023-03-09)​

Added​

  • [VEGA-290] Upgrade transmutation now removes values from DataOptions and FinderOptions that should not have any value defined.
  • [VEGA-289] Extended deadline for removing option legacy.projectionDetailedConstructor.reenable till 2023-06-15

5.19.2 (2023-03-01)​

Fixed​

  • [VEGA-296] The option legacy.vectorCollectionType.reenable resulted in code that did not compile correctly after changes to the projectionProjectionA tailored subset of fields on a DataElement designed to encapsulate data for a specific technical or functional view. pojo expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. for collection link fieldsFieldA property of a DataElement expanded to a database column and user interface input element..

5.19.1 (2023-02-22)​

Fixed​

  • Fixed the enable-condition for the Remote interface expanderExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. to only be expanded when option ejb.interfaces.localOnly is not present on the applicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution..

Added​

  • Added resources feature anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion. to ComponentMetaData.buildResources().

5.19.0 (2023-02-20)​

Added​

  • Added legacy option legacy.projectionDetailedConstructor.reenable on ApplicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution. to re-enable expansion of the legacy "detailed constructor" in the projectionProjectionA tailored subset of fields on a DataElement designed to encapsulate data for a specific technical or functional view. POJO classes. (Expires 2023-09-01)
  • Added UTF-8 default encoding property to expanded .editorconfig file.

Changed​

  • Updated nsx-runtime: 2022.5.2 > 2023.0.0
  • Updated prime-core: 2023.0.2 > 2023.0.3

Removed​

  • Removed legacy "detailed constructor" from projectionProjectionA tailored subset of fields on a DataElement designed to encapsulate data for a specific technical or functional view. POJO classes. The use of this constructor violates the Action Version Transparency theorem of the NS theory. There is no longer any technical reason for this constructor to exist.
  • Removed last remaining imports of net.democritus.sys.SearchDataRef, net.democritus.support.ejb3.SearchDataRefToSearchDetailsMapper and net.democritus.support.Paging, as all functionality related to it has been removed in a previous release.
  • Removed imports of net.democritus.io.SimpleUriFormat and net.democritus.io.NioFileCopier from FileUploadFeature.EntererExpander as they are no longer used and both classes are deprecated.

5.18.0 (2023-02-15)​

Added​

  • Added legacy option legacy.cruds.getProjection.emptyOnError on ApplicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution. to revert to the old behaviour of returning null when the requested element was not found by getProjection. (Expires 2023-08-01)
  • FieldFieldA property of a DataElement expanded to a database column and user interface input element. operator Null now displays as a checkbox in the UI findersFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement..

Changed​

  • Changed getProjection in cruds to report an error when the requested element is not found.

Removed​

  • Option experimental.cruds.failOnProjectionNotFound has been removed, as this is now default behaviour.

5.17.1 (2023-02-07)​

Added​

  • Added option cruds.table.hide for FieldFieldA property of a DataElement expanded to a database column and user interface input element., ReferenceField and CalculatedField to remove a fieldFieldA property of a DataElement expanded to a database column and user interface input element. from the table view in *-ko-list.html. This option applies to both the old and new UI.
  • Added CSS files that are automatically appended to the page-model for the new UI on Component and DataElement level, to add both custom and expanded css.

5.17.0 (2023-02-01)​

Added​

  • It is now possible to add a default implementation in a feature anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion.. If any feature insert something in the anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion., the default implementation will be replaced. But if no feature adds anything, the default content will be used.

Fixed​

  • Fixed UniqueConstraint for null-values in Ln02 LinkFieldsFieldA property of a DataElement expanded to a database column and user interface input element.

5.16.5 (2023-01-27)​

Fixed​

  • Fixed columnNames in UniqueConstraint annotations

5.16.4 (2023-01-27)​

Fixed​

  • Pruned dependencies to fix issues for projects depending on ExpandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact.

5.16.3 (2023-01-25)​

Fixed​

  • [VEGA-268] Added prime-data dependency to expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact.-test-utils to prevent issues with missing technologies.

Added​

  • [VEGA-252][VEGA-250][VEGA-259] Added option csv.disable to remove all CSV import and export options
  • [VEGA-235] Added uppercase and lowercase as options for db.tableName.format

Changed​

  • Renamed includeCsvImport and includeCsvExport options to csv.import and csv.export.

5.16.2 (2023-01-21)​

Added​

  • Added several data resources defined in prime-data, which relate specifically to the JEE stack, into Expanders.

Changed​

  • Updated nsx-runtime: 2022.4.0 > 2022.5.1

5.16.1 (2023-01-20)​

Added​

  • filter attribute in <list> mapping can now also be a Predicate
  • filters variable is now available in mapping scope

Fixed​

  • Added missing modify implementation for UniqueConstraints
  • [VEGA-232] Now filtering out componentDependencies on Components that have a no_Layer option

5.16.0 (2023-01-04)​

Fixed​

  • Fixed FileSystemNotFoundException causing stacktrace printer to fail, giving vague errors
  • Fixed description of jndi.appName option, which does not receive a value

Changed​

  • [VEGA-240] Changed behavior of ArtifactHarvester so that it does not fail on missing ArtifactsArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project.. It is possible to reenable this behavior with the ExpansionSettings option harvest.failOnMissingArtifact.

Removed​

  • Removed options that expired on 2023-01-01:
    • legacy.logicDataMethods.reenable
    • legacy.oldCollectionMethods.reenable
    • legacy.oldSearchMethods.reenable
    • legacy.relationRetrievalMethods.reenable
    • legacy.searchDataRefMethods.reenable
    • legacy.struts.defaultStyle

5.15.2 (2022-12-01)​

Changed​

  • Added support to enable schema validation with the selected persistence framework (Hibernate or OpenJPA only), instead of migration or doing nothing.

5.15.1 (2022-11-29)​

Changed​

  • Updated Struts2 from 6.0.3 to 6.1.1. (Addresses CVE-2022-42889 in commons-text)

5.15.0 (2022-11-25)​

Added​

  • Added support for struts 6.0.

Removed​

  • Removed GlobalCounter feature (activated by setting counterDefault to GLOBAL)

Changed​

  • Renamed options:
    • experimental.persistence.identifier and experimental.persistence.defaultIdentifier to persistence.identifier.
    • experimental.persistence.sequence.name and experimental.persistence.sequence.defaultName to persistence.sequence.name.
    • experimental.persistence.sequence.schema and experimental.persistence.sequence.defaultSchema to persistence.sequence.schema.
  • Updated prime-core: 2022.10.5 > 2022.10.9.
  • Struts 6.0 is now the default version, both 2.3 and 2.5 are still supported through the struts.version option.
  • Moved all struts libraries from nsx-runtime and struts-stack to a new library in the expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. project for struts 6.0 and up.
  • Moved all data resource related to struts into the ExpandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact..
  • The option struts.version is now marked as deprecated and will be removed (along with support for struts 2.3 and 2.5) on 2023-07-01.
  • GlobalOptionSettings:
    • beanInterfacePolicy=LOCAL: represented with option ejb.interfaces.localOnly instead. beanInterfacePolicy=REMOTE is no longer supported.
    • enforceHttpMethod: replaced by option struts.security.enforceHttpMethod
    • useCsrfProtection: replaced by option struts.security.csrfProtection
    • generateArtifactLabel: replaced by option mvn.version.appendUniqueLabel, appends applicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution. name instead of settings names
    • useJavaEESecurity: replaced by option struts.security.custom, or simply remove account Component from the ApplicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution.
    • baseCompsMode=GENERATE: replaced by option legacy.struts.defaultStyle
tip

Use the transmutation Upgrade to migrate the GlobalOptionSettings to the replacement options. This transmutation should be available after updating to this ExpandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. version.

mvn expanders:transmute-model -Dtransmutation=Upgrade

Fixed​

  • Fixed classloading for isApplicable and artifactArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project. path resolution so that they use the Thread's context classLoader.
  • [NSX-316] Fixed CSRF protection to support parallel calls.
  • Added missing option persistence.schemaUpdating to data resources. Now only allows values update or none as originally intended.

5.14.4 (2022-11-02)​

Fixed​

  • Added option 'view.updateFormFix' to fix fieldsFieldA property of a DataElement expanded to a database column and user interface input element. not updating in edit forms by reworking triggers.

5.14.3 (2022-10-27)​

Fixed​

  • Fixed duplicate anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. in testBase() when using dashes in an inline feature anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion.

5.14.2 (2022-10-14)​

Changed​

  • Renamed options (with alias to maintain backwards compatibility):
    • editorconfig.disabled > legacy.editorconfig.disabled
    • isMultilingual > legacy.multilingual.enable
    • useGlobalCounter > legacy.globalCounter.enable
    • transient.ui.expandRootPages > legacy.ui.rootPages.reenable
    • valueFieldType.disableHashCodeMethod > legacy.valueFieldType.hashCodeMethod.disable
  • Marked options as deprecated:
    • Valid until 2023-04-07:
      • legacy.editorconfig.disabled
      • legacy.globalCounter.enable
      • legacy.multilingual.enable
      • legacy.ui.rootPages.reenable
      • legacy.valueFieldType.hashCodeMethod.disable
      • legacy.vectorCollectionType.reenable
    • Valid until 2023-01-01 (these have been legacy for a very long time):
      • legacy.logicDataMethods.reenable
      • legacy.oldCollectionMethods.reenable
      • legacy.oldSearchMethods.reenable
      • legacy.relationRetrievalMethods.reenable
      • legacy.searchDataRefMethods.reenable

5.14.1 (2022-09-29)​

Added​

  • Added custom-annotations anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. to DataExpander.

5.14.0 (2022-09-21)​

Added​

  • Added technology fieldFieldA property of a DataElement expanded to a database column and user interface input element. to AdditionalExpansionStep and Feature. This will deactivate these steps and features if the technology is not present.

Changed​

  • Hibernate now defaults to version 5 is not otherwise specified as support for Hibernate 4 is being phased out everywhere.

Removed​

  • Removed some remaining support for Jonas applicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution. server.
  • Removed old code from the ExpansionContextCreator class

5.13.3 (2022-09-14)​

Removed​

  • Removed snakeyaml dependency

5.13.2 (2022-09-07)​

Fixed​

  • Added missing option value custom to validation expression for option type experimental.persistence.identifier.

5.13.1 (2022-09-06)​

Changed​

  • Updated 3rd party dependencies in expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. project (not in expanded code):
    • Libraries:
      • org.yaml:snakeyaml: 1.30 -> 1.31 (CVE-2022-25857)
      • org.antlr:ST4: 4.3.3 -> 4.3.4
      • ognl:ognl: 3.3.3 -> 3.3.4
    • Maven plugins:
      • org.apache.maven.plugins:maven-assembly-plugin: 3.3.0 -> 3.4.2

5.13.0 (2022-08-30)​

Fixed​

  • Added missing @Override annotation to the execute() method in several subclasses of ActionSupport.
  • Added missing @Override annotation to the prepare() method in several implementations of Preparable.

Changed​

The following ExpandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. and Features have been moved to base-components:

  • Engine(Bean|Local|Remote)ExpanderExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. (flowElement and serviceElement)
  • ClaimCleanerExpander
  • InterruptRecovererExpander
  • StateTransitionerExpander
  • StateViewerExpander
  • Claimable feature
  • ClaimElement feature
  • WorkflowTaskStatus feature
  • Service feature
  • EngineShutdown feature
  • TaskTimers feature

These ExpandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. have been modified to move the findByClaimed options to a separate feature in the base-components:

  • FinderBeanExpander
  • FinderDetailsExpander

Other changes:

  • Cleaned up more generic type specifications where they were not required.
  • Cleaned up some minor code style inconsistencies. (){ -> ) {)
  • Replaced deprecated new Long(String) call with Long.parseLong(String).
  • Replaced implementation of <DataElement>Cruds.getDetailsListFromData() with Java stream.
  • Replaced implementation of <DataElement><Projection>.get<TargetElement>Ids() and <DataElement><Projection>.set<TargetElement>Ids(String[]) with Java streams.
  • Replaced implementation of <DataElement>State.get<DataElement>State() with Java stream.
  • Updated nsx-runtime: 2022.2.0 > 2022.3.0
  • Updated hamcrest: 1.3 > 2.2
  • Updated <dataElement>CommandValidator.getValidator() to use Options.Option.notNull().
  • Updated routing of commands in logic bean to use a map with method references analogous to the implementation of the findersFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement. in the finderFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement. bean.

Removed​

  • Removed deprecated support for Java 7 in expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact., as Java 8 is now enforced as the minimum.
  • Removed deprecated elementProjectorMap fieldFieldA property of a DataElement expanded to a database column and user interface input element. in the logic Bean classes, as well as the custom-projection-mapping anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion..
  • Removed redundant unboxing call to in <DataElement>Cruds.getData()
  • Removed redundant warning suppressions for <DataElement>Cruds.getElementProjector().

5.12.1 (2022-08-11)​

Fixed​

  • Updated prime-core: 2022.6.0 > 2022.6.1. (2022.6.0 still depended on a SNAPSHOT version)

5.12.0 (2022-08-10)​

Fixed​

  • Fixed Cruds.getElementDetails, which used the wrong details class.

Changed​

  • Replaced new Long(0) in projectionProjectionA tailored subset of fields on a DataElement designed to encapsulate data for a specific technical or functional view. pojo classes with 0L.
  • Qualified generics in collection types where showLinkDetails is used.
  • Cleaned up generic type specifications where not needed.
  • Replaced all uses of java.util.Vector with java.util.(Array)List. The old behavior can be re-enabled with the transient option legacy.vectorCollectionType.reenable.
  • Qualified generic of result variable definition in DataRefConverter.fromString() and DataRefConverter.toString().
  • Replaced all uses of deprecated new DataRef() constructor with functional equivalent DataRef.withId(0L).
  • Refactored private method Cruds.project(Context,List,IDataElementProjector) to use the Java streams API.
  • Updated prime-core: 2022.5.4 > 2022.6.0.

5.11.0 (2022-08-08)​

Changed​

  • Updated OGNL (for use in expanderExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. mappings) to version 3.3.3.
  • Updated ST4 StringTemplate library (for use in expanderExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. templates) to version 4.3.3.

5.10.0 (2022-08-03)​

Added​

  • Explicit definition of org.apache.maven.plugins:maven-surefire-plugin in expanded root POM file to decouple it from the Maven version used to compile the applicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution..
  • Added assert to ensure no versions of Java older than 8 are targeted to expand a JEE applicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution..

Changed​

  • Updated nsx-parent to 2022.1.0.
  • Updated Maven plugins in expanded code:
    • org.apache.maven.plugins:maven-compiler-plugin: 3.8.1 -> 3.10.1
    • org.codehaus.mojo:build-helper-maven-plugin: 3.0.0 -> 3.3.0
  • All templates, artifactsArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project. and harvest files are now read and written in UTF-8 encoding.

5.9.9 (2022-07-26)​

Fixed​

  • [VEGA-234] Fix implicit name fieldFieldA property of a DataElement expanded to a database column and user interface input element. not being initialized correctly

5.9.8 (2022-06-22)​

Fixed​

  • Added missing expanderExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. comment to ContextRetriever
  • Use UserContextRetriever to fetch UserContext in ContextRetriever

5.9.7 (2022-06-20)​

Fixed​

Fixed some issues with the ContextRetriever:

  • Fixed context resulting in a null if no context is set in session
  • If no UserContext is defined, a UserContext will be retrieved from the session, if available (this is required to keep things backwards compatible)

5.9.6 (2022-06-14)​

Fixed​

  • Adding property tomee.jpa.factory.lazy=true to persistence.xml when expanding for TomEE with Hibernate 5, to avoid CDI loading issues. This is advised by Apache in the TomEE documentation.

5.9.5 (2022-06-09)​

Added​

  • Added FinderOperatorMapping.xml for expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. still using this file

Note: including mapping xml files from other expansion-resources is considered dirty and is prone to break

5.9.4 (2022-06-09)​

Changed​

  • Updated nsx-parent to 2022.0.0.

Added​

  • Added context to user session next to userContext
  • [NSX-220] Add support for OIDC logout
  • [FLOW-43] Add custom anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. to claiming methods
  • Added anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. to FindAction

Fixed​

  • Provided better error message if the harvester fails to read the artifactArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project. file

5.9.3 (2022-05-25)​

Changed​

  • Updated 3rd party dependencies in expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. project (not in expanded code):
    • Libraries:
      • ognl:ognl: 3.1.28 -> 3.1.29
      • org.apache.commons:commons-lang3: 3.5 -> 3.12.0
      • commons-io:commons-io: 2.7 -> 2.11.0
      • org.slf4j:commons-io: 1.7.30 -> 1.7.36 (test only)
    • Maven plugins:
      • org.apache.maven.plugins:maven-assembly-plugin: 3.2.0 -> 3.3.0
      • org.apache.maven.plugins:maven-compiler-plugin: 3.8.1 -> 3.10.1
      • org.codehaus.mojo:flatten-maven-plugin: 1.1.0 -> 1.2.7
      • org.jacoco:jacoco-maven-plugin: 0.8.2 -> 0.8.8
      • org.sonarsource.scanner.maven:jacoco-maven-plugin: 3.7.0.1746 -> 3.9.1.2184
  • Updated NSX Maven plugin in expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. project (not in expanded code):
    • net.democritus.maven.plugins:expansion-validation-maven-plugin: 2021.1.0 -> 2022.0.0

5.9.2 (2022-05-23)​

Fixed​

  • [VEGA-219] Removed name fieldFieldA property of a DataElement expanded to a database column and user interface input element. from ProjectionPojoExpander with option nameNotWanted. To revert this behaviour, use legacy.nameNotWanted.pojoName.
  • Added missing import for workflowRemote

5.9.1 (2022-05-19)​

Reverted​

  • Reinsert workflowRemote in EngineBean

Updated​

  • Removed direct dependency in metamodel-runtime to prevent issues with classloading conflicts in tests
  • Updated dependency:
    • prime-core: 2022.1.0 => 2022.5.4

5.9.0 (2022-05-16)​

Added​

  • [FLOW-19] Added option projection.detailsWithoutRefs, this adds a projectionProjectionA tailored subset of fields on a DataElement designed to encapsulate data for a specific technical or functional view. detailsWithoutRefs which contains the same fieldsFieldA property of a DataElement expanded to a database column and user interface input element. as the details projectionProjectionA tailored subset of fields on a DataElement designed to encapsulate data for a specific technical or functional view., but where the linkFieldsFieldA property of a DataElement expanded to a database column and user interface input element. are represented as ids. This projectionProjectionA tailored subset of fields on a DataElement designed to encapsulate data for a specific technical or functional view. is more performant than the details projectionProjectionA tailored subset of fields on a DataElement designed to encapsulate data for a specific technical or functional view. as no extra database queries are needed to resolve the DataRefs for the link fieldsFieldA property of a DataElement expanded to a database column and user interface input element..
  • Update recovery claim timeout to 5mins
  • Added InterruptRecoverer error handling

Changed​

  • [FLOW-16] Use cached workflow runtime configuration to reduce the number of database queries
  • [FLOW-16] Use detailsWithoutRefs projectionProjectionA tailored subset of fields on a DataElement designed to encapsulate data for a specific technical or functional view. in workflow orchestration to reduce the number of database queries
  • [FLOW-22] Add support for stateTask timeout

Fixed​

  • Fixed workflow claiming not working with Se findersFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement.
  • [FLOW-38] Fix status capitalization in FlowStateTransitioner

5.8.1 (2022-04-14)​

Fixed​

  • [useClaims] Fixed recovery failing because recovered instances were not claimed

5.8.0 (2022-03-16)​

Added​

  • Added ContextRetriever, which is expanded for each Component in the control layerLayerLogical separation of functionality within a single system/application, focused on code organization. and allows features and customizations to add additional context groups to the Context object.

5.7.5 (2022-02-28)​

Revert​

  • Revert removing IExecutor interface from ArtifactExpanderRunner

5.7.4 (2022-02-25)​

Added​

  • Added expansion option expansion.failFast to fail at the first error
  • [CommandFormJsExpander] Expose messages from CommandResult

Changed​

  • BlockingJobManager now executes all tasks by default and only fails fast if the option expansion.failFast is provided

Removed​

  • Removed IExecutor interface from ArtifactExpanderRunner
  • Removed ExpansionResourceXmlGenerator. Instead, use the expansionResource goal of the expanders-maven-plugin
  • Removed ComponentDirectoryFinder (the source directory is now part of the ModuleExpansionContext)
  • Removed HarvestReader (has been replaced with ArtifactHarvestFileReader)
  • Removed PrimeDataLoaderHotfix (use net.democritus.data.PrimeDataLoader instead)
  • Removed public access to net.democritus.expander.ArtifactPathBuilder#cache
  • Removed public access to net.democritus.testing.CoverageCollector#callsMap
  • Removed several methods from AssertUtil
  • Removed TemplateType

5.7.3 (2022-02-18)​

Fixed​

  • Fixed expansion failure due to mapping error when no dataBaseSchemaName is provided for a component

Added​

  • Added some support for harvestingHarvestingThe process of extracting and persisting custom code from anchors and ext directories back into source directories. base-components
    • Added expansion option harvest.force to ignore harvest.skip
    • Added expansion option harvest.modelDirectory.override to set a single directory for harvest files

5.7.2 (2022-02-18)​

Fixed​

  • Fixed Context not being passed by StateTransitioner, causing compareAndSet() to fail if claims are used

5.7.1 (2022-02-18)​

Fixed​

  • [NSX-214] Simplified logic around in operators wrt linkFieldsFieldA property of a DataElement expanded to a database column and user interface input element. in finderFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement.-mappers

5.7.0 (2022-02-17)​

Added​

  • [NSX-224] Added applicationInstance/component/data option cruds.table.csvExportButton, which adds a button to the cruds table to export instances, which takes into account the selected finderFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement..
  • [NSX-214][VEGA-194] Added support for findersFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement. with in operator in combination with linkFieldsFieldA property of a DataElement expanded to a database column and user interface input element.
  • Added support for linkfieldInput binding in finderFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement. forms
  • [NSX-207] Added ehcache.xml stub file with anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. to configure caching with Hibernate 5.

Removed​

  • Option editorconfig.global has been removed and .editorconfig file now always applies globally to both gen and ext sources.

5.6.0 (2022-02-07)​

Added​

  • [VEGA-209] Added @Deprecated and comments to methods in legacy features
  • Added expansion option expanders.traceFeatures to enable feature tracing

Changed​

  • Merged expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact.-common into expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact.-core

Fixed​

  • [VEGA-171] Added checkClaims() to compareAndSet() method for claimable DataElements

5.5.4 (2022-02-02)​

Fixed​

  • Fixed another duplication of _FindByNotClaimed in InterruptRecovererExpander

5.5.3 (2022-02-01)​

Changed​

  • Only render linkfield binding when visible

Fixed​

  • Fixed InterruptRecovererExpander duplicating _FindByNotClaimed postfix if finderFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement. with postfix is not present in the model

5.5.2 (2022-01-24)​

Fixed​

  • [NSX-212] Projector class did not add imports for types of local calculated fieldsFieldA property of a DataElement expanded to a database column and user interface input element..

5.5.1 (2022-01-18)​

Changed​

  • [NSX-197] Render waterfall tab only once an instance is selected

5.5.0 (2022-01-12)​

Changed​

  • [TaskElement] The following options are now supported for modifying the input type of a task:
    • target.element.projection: Changes the projectionProjectionA tailored subset of fields on a DataElement designed to encapsulate data for a specific technical or functional view. used from Details to the provided value
    • target.class.custom: Overrides the parameter type with the value (takes a fully qualified name)
  • [Logging] Changed how LoggingAspects are created:
    • In mapping files, the logging aspect can be defined with: 
      <value name="logging" eval="@net.democritus.common.logging.LoggingAspects@getLoggingAspect(expansionContext, {name})"/>
    • Logging aspects can now be changed with some ApplicationInstance options: logging.none and logging.custom
    • Enabled logging in several action classes where it was disabled

Fixed​

  • [generateArtifactLabel] Fixed artifactLabel not being included in the applicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution. root pom

Removed​

  • Removed long-obsolete ReporterExpander hidden behind now removed dataOption struts.reporter.enable
  • Removed JndiProperties and ComponentJNDI imports from BeanExpander as neither was relevant since 4.0 rewrite
  • Removed support for MonoLogger

These artifactsArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project. have been removed. Since they are internal artifactsArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project., no issues are expected

  • Removed expanders-skeleton module
  • Removed ValueFieldTypeMapping.xml
  • Removed FlowElementExpanderMapping.xml

For clones of the ValueFieldTypeMapping.xml file, here is a newly optimized version of the properties:

<?xml version="1.0" encoding="UTF-8" ?>
<mapping xmlns="https://schemas.normalizedsystems.org/xsd/expanders/2021/0/0/mapping">
  <let name="valueTypeClass" eval="classBuilder.from(valueFieldType)"/>
  <let name="storageType" eval="valueFieldType.storageType.toLowerCase()"/>
  <let name="displayType" eval="valueFieldType.displayType.toLowerCase()"/>

  <value name="className" eval="valueTypeClass.className"/>
  <value name="packageName" eval="valueTypeClass.packageName"/>
  <value name="variableName" eval="valueTypeClass.varName"/>

  <value name="requiresImport" eval="valueFieldType.requiresImport()"/>

  <value name="isBuiltin" eval="valueFieldType.builtin"/>
  <value name="isDate" eval="storageType.equals('date')"/>
  <value name="isDateTime" eval="displayType.equals('datelong')"/>
  <value name="isBigDecimal" eval="storageType.equals('bigdecimal')"/>
  <value name="isStringLike" eval="valueFieldType.isStringLike"/>
  <value name="isBigString" eval="displayType.equals('memo') or displayType.equals('multiline')"/>
  <value name="isByteArray" eval="storageType.equals('byte[]')"/>
  <value name="isNumber" eval="valueFieldType.isNumberLike"/>

  <value name="internalType" eval="classBuilder.from(valueFieldType.storageTypeClass)"/>
</mapping>

5.4.3 (2022-01-04)​

Added​

  • [NSX-204] Add fieldFieldA property of a DataElement expanded to a database column and user interface input element. option view.linkfield.displayField which specifies the fieldFieldA property of a DataElement expanded to a database column and user interface input element. to use in the experimental linkFieldInput through the experimental.view.linkFieldInput option.

5.4.2 (2021-12-17)​

Added​

[NSX-161] Option persistence.secondLevelCache on DataElement to enable second level cache. Currently only available for Hibernate 5 and is activated with SearchDetails.setAllowCaching(true).

5.4.1 (2021-12-13)​

Fixed​

  • [VEGA-200] Fixed FinderBean not using {DataElement}Data.ENTITY_NAME and not applying jpa.entity.name.format option
    • requires peer-dependency net.democritus:base-components:2021.6.1 for a custom harvest fix

5.4.0 (2021-12-06)​

Removed​

  • [VEGA-193] Removed unused/obsolete @PostConstruct from BeanExpander
    • requires peer-dependency net.democritus:base-components:2021.6.0
  • Removed unused/obsolete uninitialized initalContext attributes from BeanExpander, EngineBeanExpander, and ProxyExpander
  • Removed original onion/test specs; only expanded (prime-core) test-specs are now available

Fixed​

  • [VEGA-186] Fixed some copying steps (ext, harvest) not following active layerLayerLogical separation of functionality within a single system/application, focused on code organization. configuration (copying no{X}LayerLayerLogical separation of functionality within a single system/application, focused on code organization. files)

5.3.4 (2021-12-06)​

Fixed​

  • Fixed linkfieldInput rendering dataElements with nameNotWanted, hasDisplayName and functionalKey as [Object object]

5.3.3 (2021-11-24)​

Fixed​

  • [NSX-193] Fixed getStatus(), getStatusAsEnum() return type in case of noDataLayer

5.3.2 (2021-11-24)​

Added​

  • [NSX-161] Added fetch-after-create-queries anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. to FinderBean.fetchData().

Fixed​

  • [NSX-198][UI][NG] Hide tabs in waterfall setup for elements to which the users does not have view access

5.3.1 (2021-11-22)​

Fixed​

  • [VEGA-196] Fixed expansion option hideAnchors failing on .properties expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact.

5.3.0 (2021-11-22)​

Changed​

  • [tests] The method FeatureExpanderTester#testAnchor() has been changed. In previous versions, the method would ignore the name of the test method and instead construct the template name based on the anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion. name ( e.g. test_anchor_myAnchor).
    This has now been changed to use the name of the test method instead, which is more in line with the other methods. Note that this only affects feature tests, not regular expanderExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. tests, where the ExpanderTester#testAnchor() method already had this behaviour.
  • [NSX-194] Move the getData-strategy anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. in the Cruds classes to a separate method, so that the getData-after anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. are reached in case of a defined strategy.
  • [NSX-195] Made Cruds.getName() opt-in. Add transient.cruds.useGetName to add getName() to the Cruds classes.

Added​

  • Added option harvest.skip that skips harvest for that component/module. (primarily useful for model resources)

Fixed​

  • before-harvest and after-harvest are now correctly ignored for base-components. This prevents issues with harvest files in base-components being cleaned during harvest. [VEGA-195]

Removed​

  • Temporarily removed model information (number of elements, harvests, etc.) from ApplicationPropertiesExpander for technical reasons
  • Removed expansion trace from core, it now lives in net.democritus:expansion-tracer expansion bundle instead

5.2.10 (2021-11-22)​

Fixed​

  • Fixed getStatus(), getStatusAsEnum(), setStatus(), setStatusAsEnum() method in case of noDataLayer

5.2.9 (2021-11-16)​

Fixed​

  • Fixed compareAndSetStatus() method in case of noDataLayer

5.2.8 (2021-11-02)​

Changed​

  • Moved logic of patch method to separate class so feature can be injected

5.2.7 (2021-10-28)​

Fixed​

  • Add backwards compatible methods in LayerSourceFinder because it was used in other bundles

5.2.6 (2021-10-25)​

Fixed​

  • Fixed ext directories for some layerImplementations not being generated because of missing variables when resolving the conditions

5.2.5 (2021-10-22)​

Added​

  • [NSX-189] Enable findAll to be used as searchMethod on the find-json struts endpoint
  • [NSX-189] Implement hasDisplayName option in experimental.view.linkFieldInput
  • [NSX-190] Enable experimental.view.linkFieldInput for commands
  • Added Data Option view.buttons.commands, which adds buttons to NG pages to open command forms. Primarily useful for prototyping and quickly testing new DataCommand features

5.2.4 (2021-10-18)​

Fixed​

  • Moved ApplicationSettings to shared layerLayerLogical separation of functionality within a single system/application, focused on code organization..

5.2.3 (2021-10-18)​

Added​

  • Component option configuration.properties to expand ApplicationSettings class for component which can load settings from a properties file on the classpath.

5.2.2 (2021-10-11)​

Fixed​

  • Fixed issues when trying to use Component in program other than ApplicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution.
  • Improved CsvMerger feature so that update happens in one call per instance.
  • Fixed CsvMerger not creating new instances on import

Added​

  • Added more custom anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. to CsvMerger feature

5.2.1 (2021-10-07)​

Fixed​

  • It was no longer possible to expand export() and importFile() pipelines without the use of the includeCsvImport and includeCsvExport options. This functionality is now available separately with the io.import and io.export options for the DataElement.
  • Now using correct classLoader in ArtifactPathModelBuilder

Removed​

  • Removed deprecated transient option io.strutsAction.

5.2.0 (2021-10-01)​

Added​

  • [NSX-152] Added applicationInstanceOption csv.import.merge, which changes the CSV import so that the imported fieldsFieldA property of a DataElement expanded to a database column and user interface input element. are merged into the existing data, as opposed to the original implementation, which overwrites all fieldsFieldA property of a DataElement expanded to a database column and user interface input element..

5.1.6 (2021-10-01)​

Fixed​

  • Fixed issue where dataRegistry would not be filled in for expansionContexts in tests with external metamodels

5.1.5 (2021-09-30)​

Fixed​

  • Fixed ComponentRootPomExpander so that it creates a valid pom.xml file when one of the layersLayerLogical separation of functionality within a single system/application, focused on code organization. is not included in the expansionContext (based on moduleType+options).

5.1.4 (2021-09-30)​

Fixed​

  • Fixed ExpansionContextCreator for metamodels like scripts metamodel (see examples), where the expansionContext is not rooted in a custom ExpansionContextFactory

5.1.3 (2021-09-29)​

Fixed​

  • Fixed issues with maven selecting wrong onion-spec-runtime version when adding expanders-test-utils as dependency alongside another dependency depending on onion-spec-runtime

5.1.2 (2021-09-25)​

Fixed​

  • Fixed ExpansionContextCreator so it can be used without custom ExpansionContextFactory classes

5.1.1 (2021-09-24)​

Fixed​

  • Fixed issue in ApplicationPropertiesExpander with technologies where concernType=null

Removed​

  • Removed ANT file mapping from ArtifactPathBuilderMapping

5.1.0 (2021-09-22)​

Added​

  • ApplicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution. option experimental.view.linkFieldInput will activate a new knockout implementation for many-to-one linkFieldsFieldA property of a DataElement expanded to a database column and user interface input element.. For now, options for the binding will have to be provided with custom code in the -form.js file.
  • Added camelCase format option and asCamelCase shorthand for expanderExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. templates.
  • Implemented cruds.bulk.delete for knockout v1 (NSX KNOCKOUT OG)

Changed​

  • Changed view layerLayerLogical separation of functionality within a single system/application, focused on code organization. expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. to use NSX KNOCKOUT OG/NG technologies, which replace the version on PresentationSettings. PresentationVersionHelper is now obsolete.
  • Updated ApplicationPropertiesExpander to use more of the modern composite API
  • Bean methods importFile/exportFile are now only expanded when includeCsvImport/includeCsvExport option is defined [VEGA-178]

Removed​

  • Removed some obsolete references to COCOON

Fixed​

  • Fixed some logic still using ApplicationExpansionSettings
  • Fixed support for elementType any
  • Fixed external metamodel expansions being run twice (once by generic ExpansionRunner classes and once in dedicated ExpansionStep)
  • Fixed ExpansionRunner causing ConcurrentModificationException in some cases

5.0.2 (2021-08-25)​

Fixed​

  • Fixed ClassNotFoundException with some external metamodels

5.0.1 (2021-08-23)​

Fixed​

  • Fixed issue with loading of ValueFieldTemplates
  • Fixed isDetailsOnly option still expanding findersFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement. etc.

5.0.0 (2021-08-23)​

Added​

  • Added support for driving expansion based on programTypes, moduleTypes and expandableElements.

Changed​

  • ApplicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution. is now an expandable element, and Component now has ApplicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution. as its parent in the expansion hierarchy. Expanding with ApplicationInstance still works as before.
  • Expansion now uses specialized ExpansionRunner classes instead of expanded classes. Old setups using expansionSteps should still work, but easier alternatives are now available using dataResources describing expandable elements.
  • ApplicationExpansionSettingsComposite has been replaced with the ExpansionSettingsComposite. A stubbed object is still available, but it is highly recommended switching to the new composite class.
  • ExpansionJobManager has a new method submit(Consumer<T>, Iterable<T>) to submit new tasks, which replaces the outdated IExecutor interface with the java 8 Consumer interface.

Technologies and LayersLayerLogical separation of functionality within a single system/application, focused on code organization.

  • LayersLayerLogical separation of functionality within a single system/application, focused on code organization. are decided by the ModuleType and ProgramType configuration. These include all applicable layersLayerLogical separation of functionality within a single system/application, focused on code organization.. In case you have expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. that introduce a new layerLayerLogical separation of functionality within a single system/application, focused on code organization., the correct way to add the layerLayerLogical separation of functionality within a single system/application, focused on code organization. is to define a new ModuleType and ProgramType with your new layerLayerLogical separation of functionality within a single system/application, focused on code organization. included.
  • Technologies are decide by the linked TechnologyStacks. If your expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. introduce a new Technology, users will have to add it to their technologyStacks.

Removed​

  • Removed ANT expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact.

4.19.5 (in 5.0.0)​

Changed​

  • [presentationSettings 2.*] Individual root html pages (with <head>, etc.) are no longer expanded for each dataElement
    • instead struts direct the requests to a a single jsp page that launches an appropriate input model
  • [presentationSettings 2.*] DataElement's HTML page no longer contains inline scripts to allow for strict CSP
  • Changed favicon URL path /$application$/images/pageIcon.ico to ../../images/favicon.ico (both paths normalize to the same location)
    • place your favicon to applications/$application$/ext/view-ext/knockout/images/favicon.ico

Removed​

  • [presentationSettings 2.*] Removed obsolete jqplot loading, and dead graph features (hasCountByStatusGraph and hasCountPerHourGraph)
  • [presentationSettings 2.*] removed inline script setting obsolete window['NSX']
    • requires peer-dependency web-styles 2021.2.0
  • [presentationSettings 2.*] removed root HTML pages for each dataElement and its IO
    • to force their expansion, use applicationInstanceOption transient.ui.expandRootPages
    • ext pages created by copy-pasting regular ones can mostly be removed and replaced in struts with /jsp/ps2/page.jsp?pageModel={path-to-ext-page-model-js-file} (without extension), e.g. /jsp/ps2/page.jsp?pageModel=testComp/Person/custom-page-model

Fixed​

  • [NSX-131] uniqueKey validation in Bean moved from @preCreate, @preModify, and @preCreateOrModify to their @pre-validation anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion. counterparts.
  • [NSX-144] isRequired validation in Cruds moved from @preCreate, @preCreate-projection, @preModify, and @preModify-projection to their @pre-validation anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion. counterparts.
  • [NSX-166] Data projector in Struts UI now does not show a "find failed" warning after element deletion.
  • [NSX-180] Added missing details method variable within the find method of a customizable finderFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement. without fieldFieldA property of a DataElement expanded to a database column and user interface input element. operator pairs.
  • [NSX-181] Added custom anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. to the form html file of a customizable finderFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement..
  • [expansionTrace] fixed double-expansion needlessly failing expansionTrace

4.19.4 (2021-07-19)​

Added​

  • Added applicationInstanceOption vega.transient.taskBean.mImplementation to provide TaskBean implementation under previous variable name [VEGA-162]
  • Marked implementation variable in TaskBean as final

4.19.3 (2021-07-15)​

Added​

  • [JPA] Ln04 linkFieldsFieldA property of a DataElement expanded to a database column and user interface input element. now support fieldOption hasOtmMappedBy [NSX-172]

4.19.2 (2021-07-15)​

Fixed​

  • [cruds] resolveDataRef and findData now returns error if the the functional key is malformed (such as having null or empty fieldsFieldA property of a DataElement expanded to a database column and user interface input element.) [NSX-69]
  • [findersFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement.] functional key no longer requires explicit findBy<fk_fields> finderFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement. (also requires prime-core 2021.3.1+)

4.19.1 (2021-07-08)​

Reverted​

  • [findersFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement.] Reverted FinderBean generics signatures (<T>) back to wildcard signatures (<?>) due to downstream incompatibility

4.19.0 (2021-07-05)​

Added​

  • [findersFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement.] Added customizable findersFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement. via finderOption isCustomizableFinder [NSX-164]
    • customizable finderFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement. expands like a regular finderFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement., however it provides customization anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. within the FinderBean
  • [findersFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement.] Added finderOption noViewLayer to exclude a finderFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement. from the UI
    • supported by both 2.x and 1.x UI
  • [findersFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement.] Added Gte and Lte operators [NSX-157]
  • [findersFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement.] Added Null, Notnull, In, and Nin (not in) operators [NSX-117],[NSX-157]
    • no UI support yet; use them with customizable, custom, or noViewLayer findersFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement.
    • see foundation for the semantics of these findersFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement.
  • [core] Added support for SQL anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion. comment formats (line -- %s, block /*%s*/)
  • [maven] Added applicationInstanceOption experimental.maven.logicLayer.noDataTestSources to no longer compile data layerLayerLogical separation of functionality within a single system/application, focused on code organization. test sources and test resources second time within the logic layerLayerLogical separation of functionality within a single system/application, focused on code organization. pom
  • [NSX-163] Added fieldFieldA property of a DataElement expanded to a database column and user interface input element. option validation.listField. This option adds a validation in the bean class, which matches incoming values of that fieldFieldA property of a DataElement expanded to a database column and user interface input element. with the options configured in the TagValuePair table. If the value is not a valid option, the validation will return an error.

Fixed​

  • [NSX-130] Added missing uniqueKey validation to createOrModify method in the bean

4.17.1 (2022-01-19)​

Fixed​

  • Fixed web.xml containing duplicate @servlets and custom-servlets anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion.

4.17.0 (2021-06-15)​

Added​

  • Added valueListTag to connectorField. By provided a value, the fieldFieldA property of a DataElement expanded to a database column and user interface input element. will be rendered as a dropdown, where the options will be selected based on the matching instances in the TagValuePair table. (Only for expanded command form)

4.16.3 (2021-06-08)​

Fixed​

  • Fixed some issues with the experimental.workflow.batchLess option:
    • Exclude duplicate instances
    • Prevent double check if initial find did not return any results

4.16.2 (2021-06-08)​

Changed​

  • Changed SQL Server dialect for Hibernate to SQLServer2012Dialect to have support for native sequences. Versions of SQL server older than 2012 are no longer supported by Microsoft as af May 2020.

4.16.1 (2021-05-17)​

Added​

  • Added clean-harvest support for harvest and test directories; fixed some edge cases for ext harvestingHarvestingThe process of extracting and persisting custom code from anchors and ext directories back into source directories.
  • Added DataElement option vega.localInterface.enableExtends to enable extending DataElement's Local interface
    • note that vega.*, rigel.*, and other star-named options are not be used without prior consultation

4.16.0 (2021-05-07)​

Added​

  • [experimental] Added applicationInstance option experimental.workflow.useExecutorService, which enables the workflow to run with an executorService. The api of the executorService allows us to more efficiently chain tasks. This can improve throughput for workflows where there is a large difference between the time for each task in the batch.

    To get this to work on TomEE, you will also need to add the following to your tomee.xml:

    <Resource id="executorService" type="ManagedExecutorService">
      Core = 10
      Max = 25
      KeepAlive = 5 s
      Queue = 15
      ThreadFactory = org.apache.openejb.threads.impl.ManagedThreadFactoryImpl
      Lazy = true
    </Resource>

    Also note that the queue size should be correctly configures for all workflows. Otherwise, the executorService might start rejecting tasks from simultaneous workflow runs.

    To get this to work on another applicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution. server, configure the ManagedExecutorService and then add a ParamTargetValue with paramName workflow.executorService.jndiName, target ExecutorServiceTaskProcessor and value equal to the jndiName of the ManagedExecutorService.

  • [experimental] Added flowElement option experimental.workflow.batchLess. This will change the EngineBean so that it fetches new instances when executing tasks. With this change, the EngineBean will relentlessly try to execute all possible tasks for each StateTask in one run. Note that this feature can create issues, so keep these considerations in mind:

    • If there is a cycle in the workflow, this can cause the run to go on endlessly .
    • Each StateTask is still executed sequentially, meaning it can take a while before the 2nd, 3rd etc. task are executed. You can combine this option with sequencingStrategy=greedy to improve the response time.
    • The settings works best with claims, since that prevents the same instance from being fetched twice. Though without, there will not be any functional problems. (The count of tasks processed may yield strange results though)

Changed​

  • The EngineBeanExpander now prefers a finderFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement. with Se to Eq when selecting the correct finderFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement..
  • The EngineBeanExpander will explicitly check for the existence of the finderFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement. used when fetching a new batch during expansion.

4.15.5 (2021-05-06)​

Changed​

  • When Hibernate 5 is selected with an Oracle Database as target, the Oracle 12c dialect is now used.

4.15.4 (2021-05-03)​

Fixed​

  • Fixed artifactArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project. file naming in expansionTrace not being relative
  • Fixed featureSegments in expansionTrace to also contain expanderFeature reference and feature anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion. name (with @ prefix)

4.15.3 (2021-04-30)​

Reverted​

  • Revert change that made ExporterActionExpander and ImporterActionExpander always expand, not just with options includeCsvExport and includeCsvImport. While this change was made to promote the usage of expanded code for exporting/importing, it can create collisions with existing custom code. Hence, the actions are now only expanded with the csv options, or with the component option io.strutsAction.

4.15.2 (2021-04-27)​

Fixed​

  • Fixed error when expanding ExporterActionExpander with a DataElement without findersFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement.. Note: This has only been added for backwards compatibility. To ensure regular behaviour, it is required to at least add a findAll finderFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement..

4.15.1 (2021-04-22)​

Added​

  • Added several feature anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. for noDataLayer in BeanExpander

4.15.0 (2021-04-15)​

Added​

  • Added some variables to artifactArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project. path scope for easier customization:
    • isHarvest: a boolean value that is true iff running a harvest. You can use this to specify where the harvest files should end up. E.g <artifactPath>$if(isHarvest)$$componentRoot.directory$/foo$else$$application.root$/foo/components/$element.component.name$$endif$/sub/path</artifactPath
    • technologyDir: the subdirectory for the expanderExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact.'s technology setting. E.g. build/$technologyDir$/ will translate to build/common or build/ejb etc.
    • sourceDir: the subdirectory for the expanderExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact.'s sourceType setting. E.g. main/$sourceType$ will translate to main/src or main/js
    • genDir: will translate to gen/ during expansion, or an empty string during harvest
    • expansionRoot.directory: the root directory of the expansion
  • Added kebab format for stringtemplates (and artifactPath), which converts camelcase to dashed lowercase
  • Added ApplicationOptionType/ComponentOptionType experimental.persistence.defaultIdentifier to be used with values sequence or identityColumn to consistently specify the use of a sequence or identity column for id generation in the database
  • Added ApplicationOptionType/ComponentOptionType experimental.persistence.sequence.defaultSchema to set a custom schema when experimental.persistence.defaultIdentifier: sequence is used, instead of defaulting to the component schema
  • Added ApplicationOptionType/ComponentOptionType experimental.persistence.sequence.defaultName to set a custom sequence name when experimental.persistence.defaultIdentifier: sequence is used, instead of defaulting to NS_SEQUENCE

4.14.1 (2021-04-09)​

Reverted​

  • Reverted addition of combined sources jars due to deployment conflicts

4.14.0 (2021-04-09)​

Added​

  • Added build config for complete sources jar
  • Added FieldOptionType experimental.instanceView.stringDisplayHandler for String fieldsFieldA property of a DataElement expanded to a database column and user interface input element. to provide custom fieldFieldA property of a DataElement expanded to a database column and user interface input element. binding for InstanceViewHtml pages
    • e.g. fieldOption("experimental.instanceView.stringDisplayHandler : markdown")
  • Added FieldOptionType experimental.valueFieldType.storageType for String fieldsFieldA property of a DataElement expanded to a database column and user interface input element. to customize database representation
    • e.g. fieldOption("experimental.valueFieldType.storageType : varchar : 1024")
  • Merged v4.11.9

Changed​

  • [struts2] Agents are now initialized in a prepare step for most struts actions, so that interceptors have the chance to run first.
  • [knockout] Rearranged anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. in finderFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement. forms to make more sense

Fixed​

  • Add more information to exceptions occurring during isApplicable mapping
  • [expansionTrace] Fixed ext file missing content
  • [expansionTrace] Fixed inconsistent URI paths
  • Fixed FeatureInjector producing method groups for segments with blank content
  • Removed print statements from StrutsValidatorExpander
  • Fixed an import for branching tasks in BeanExpander (task)

Removed​

  • Dropped support for nsfInstallation file
  • Removed PrimeRadiant-specific expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. and features
  • Removed obsolete expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact.
    • net.democritus.expander.ejb3.serviceElement.TaskLocalExpander
    • net.democritus.expander.ejb3.serviceElement.TaskRemoteExpander

4.13.5 (2021-03-05)​

Fixed​

  • Fixed issue where custom feature anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. would be removed when expanding

4.13.4 (2021-03-01)​

Fixed​

  • Fixed ArtifactFeatureExpander not using ModelBuildFactory correctly

4.13.3 (2021-02-18)​

Fixed​

  • Fixed linkFieldsFieldA property of a DataElement expanded to a database column and user interface input element. in functional key DataRefs not being resolved before find.

4.13.2 (2021-02-15)​

Added​

  • Merged v4.12.4

Fixed​

  • Fixed default-complete applicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution..menu adding noViewLayer elements

4.13.1 (2021-02-11)​

Added​

  • Merged v4.12.3

4.13.0 (2021-02-11)​

Added​

  • Page title in ko2 UI is now translated property
  • SearchDetails now has a fieldFieldA property of a DataElement expanded to a database column and user interface input element. skipCount that can be set to true to skip the count query during a find
  • Added a new default-complete profile to applicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution. menu listing all applicable components/dataElements
    • nsx-runtime v2021.0.0 will fallback to this default-complete, if no other profile is available
    • both ApplicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution. and Component navigations now have XSDs

Changed​

  • The title in the menu of a page has been changed to a separate property (<component>.<element>.menu.title)
  • Renamed expansionOption disableExpansionTrace to expansion.trace.enable (and flipped the logic)
  • Renamed expansionOption exportTraceZip to expansion.trace.exportToZip
    • if defined, relative paths are now resolved against expansionSettings.expansionDirectory

Fixed​

  • Fixed issue with bulk delete dialog throwing error when delete action is not allowed
  • Fixed imports for CascadeDelete
  • Fixed ComponentRootPomExpander ignoring applicationInstanceOption no{name}Layer
  • Added experimental applicationInstanceOption experimental.maven.noViewPom to exclude view from maven reactor

4.12.4 (2021-02-11)​

Fixed​

  • Fixed ModifyAction expanderExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. and struts reference option conditions not in sync

4.12.3 (2021-02-11)​

Fixed​

  • Fixed ModifyAction being referenced in struts element xml without cruds.modifyWithProjection option

4.12.2 (2021-02-09)​

Changed​

  • Made createWithProjection() and modifyWithProjection() optional.
    • Add cruds.createWithProjection to add createWithProjection(). This will move the create anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. in the cruds class, so check for any broken custom code.
    • Add cruds.modifyWithProjection to add modifyWithProjection(). This was the behaviour for the previous versions.
  • The createOrModify() method implementation will be different depending on which methods are available (see options above).

Removed​

  • Removed BeanAnchor expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact.

4.12.1 (2021-01-26)​

Fixed​

  • Fixed issue with legacy.searchDataRefMethods.reenable
  • Do not expand for legacy.oldCollectionMethods.reenable and legacy.oldSearchMethods.reenable with noDataLayer
  • Using finders.enableTypedFinders resulted in a compilation error

4.12.0 (2021-01-14)​

Added​

  • Added createOrModify() method that updates an instance if it already exists in the database and creates it otherwise.
  • Added createWithProjection() method to create an instance with a projectionProjectionA tailored subset of fields on a DataElement designed to encapsulate data for a specific technical or functional view.
  • Added resolveDataRef() method that takes any DataRef and returns a DataRef with database values, if it exists.
  • Added delete(dataRef) method to replace the delete based on id
  • Added ApplicationInstance options to replace settings in GlobalOptionSettings:
    • struts.security.custom replaces useJavaEESecurity=TRUE, or, don't have account component in your applicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution.
    • struts.security.csrfProtection replaces useCsrfProtection
    • struts.security.enforceHttpMethod replaces enforceHttpMethod
    • baseCompsMode=NONE can be replaced with leaving out the account component Old behaviour is kept backwards compatible:
    • useJavaEESecurity=TRUE and baseCompsModel=NONE always activate, even if there is an account component present
    • csrfProtection and enforceHttpMethod can be activated both with the new options and the GlobalOptionSettings
  • To enable soft delete, cruds.softDelete can be used instead of naming a fieldFieldA property of a DataElement expanded to a database column and user interface input element. disabled
  • Added DataElementFindDetails interface for every DataElement, which is implemented by the FindDetails class of every FinderFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement. when using the ApplicationInstance option finders.enableTypedFinders
  • Constraint on type of the finderFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement. in all find() methods to prevent the use of findersFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement. with agents of different DataElements when using the ApplicationInstance option finders.enableTypedFinders
  • New implementation for mapping findersFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement. to their implementation without reflection when targeting at least Java 8 and using the ApplicationInstance option finders.enableTypedFinders
  • Added a number of descriptions to expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact., expansionSteps and expansionResources
  • Added several feature anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. to task artifactsArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project.
  • Added several feature anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. for commands

Fixed​

  • Cleaned up inconsistencies in html templates
  • Removed some redundant imports
  • Fixed an issue with using strictly equals for flowElement in InterruptRecoverer

Changed​

  • Projector classes now use resolveDataRef() to resolve linkFieldsFieldA property of a DataElement expanded to a database column and user interface input element. during create/modify, meaning functionalKeys will also be resolved. (This previously worked only for Ln02)
  • Projector classes now return projection.getDataRef() in the getDataRef() method, which should include more data
  • As a result of the previous change, modify() now correctly fetches the target instance based on name or functionalKey, not just on id

Removed​

Removed several outdated methods. To revert them, use the following options:

  • legacy.oldCollectionMethods.reenable: raw methods to fetch collections
  • legacy.oldSearchMethods.reenable: raw methods to search instances
  • legacy.logicDataMethods.reenable: methods in bean using Data class or other data layerLayerLogical separation of functionality within a single system/application, focused on code organization. artifactsArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project.
  • legacy.relationRetrievalMethods.reenable: methods in agent to fetch instances of related dataElements
  • legacy.searchDataRefMethods.reenable: methods to search instances with a SearchDataRef object instead of the more modern finderFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement. objects

Note​

  • nsx-actions.js:performSearch() uses the searchDataRef-based find action. So if you wish to use this method, enable legacy.searchDataRefMethods.reenable

4.11.9 (2021-02-08)​

Fixed​

  • Fixed an issue with artifactPath caching for delegating composites

4.11.8 (2021-01-21)​

Fixed​

  • Fixed having a single option for pageSize generating a pageSize picker with a single option

4.11.7 (2021-01-15)​

Fixed​

  • Fixed issue where getName() on Data object of a DataElement with option nameNotWanted could throw a NullPointerException

4.11.6 (2021-01-04)​

Fixed​

  • Fixed feature anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. with option separator: '\n' to work as expected

4.11.5 (2020-12-18)​

Fixed​

  • Fixed an issue where runWorkflowWithTargets() would be interrupted because of the status of an engineService
  • Fixed bulk delete in combination with ejbPolicy=LOCAL

4.11.4 (2020-12-08)​

Fixed​

  • Fixed issue with any expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. during harvest

4.11.3 (2020-11-27)​

Added​

Added fieldFieldA property of a DataElement expanded to a database column and user interface input element. options for second generation UI:

  • cruds.form.hide: Hide this fieldFieldA property of a DataElement expanded to a database column and user interface input element. in all forms

  • cruds.form.hideOnCreate: Hide this fieldFieldA property of a DataElement expanded to a database column and user interface input element. on the create form

  • cruds.form.hideOnModify: Hide this fieldFieldA property of a DataElement expanded to a database column and user interface input element. on the edit form

  • cruds.form.disable: Disable this fieldFieldA property of a DataElement expanded to a database column and user interface input element. in all forms

  • cruds.form.disableOnCreate: Disable this fieldFieldA property of a DataElement expanded to a database column and user interface input element. on the create form

  • cruds.form.disableOnModify: Disable this fieldFieldA property of a DataElement expanded to a database column and user interface input element. on the edit form

Added data/component/applicationInstance option cruds.table.pageSize, which can be configured as follows:

  • cruds.table.pageSize: 10: set the pageSize to specific number (10 in this case)
  • cruds.table.pageSize: unlimited: disable paging
  • cruds.table.pageSize: 10, 25, 50: add a dropdown to the table to select the pageSize (her with options 10, 25 and 50)

Fixed​

  • Fixed issue where fieldFieldA property of a DataElement expanded to a database column and user interface input element. errors would not show

4.11.2 (2020-11-25)​

Fixed​

  • Fixed bulk delete for waterfall tables

4.11.1 (2020-11-24)​

Fixed​

  • Fixed issue in form.js with fileUpload features

4.11.0 (2020-11-24)​

Changed​

  • expansionTrace zip: Replace :: with // when using dataRefs as value to avoid parsing ambiguity

Added​

  • [phase] Added initialize phase, which is present for both harvest and expand and runs at the start
  • [cruds] Added bulk delete feature, activated by appInstance option cruds.bulk.delete
  • [UI] Added expanderExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. for -actions.js file, which contains functions for UI actions sent to the backend
  • [TreeToPrime] Added feature for PrimeToTree to automatically provision missing option types in PR

4.10.6 (2020-11-24)​

Fixed​

  • Fixed issue where artifactPathModifiers were being calculated before isApplicable

4.10.5 (2020-11-12)​

  • Merged v4.9.4

4.10.4 (2020-11-10)​

Added​

  • Applied changes to mapping parameters and delegates to isApplicable conditions as well

Fixed​

  • Fixed issue with 4.10.3 where calculating the artifactPath would throw an exception at runtime

4.10.3 (2020-11-09)​

Changed​

  • Changed how delegating and extendable composites work:
    • delegating: changes the variable named after the element to the 'model' object, adds <elementName>Wrapper variable for the composite object
    • extendable: extensions can be accessed with <parent>.getExtension['<extensionName>']

Added​

  • Added feature as parameter in mapping files for features
  • Added expansionResource as parameter in any mapping file
  • Added parent element and other ancestors as parameter in any mapping file (e.g. use component in DataElement expanderExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact.)

4.10.2 (2020-11-05)​

Fixed​

  • Additional fix for issues with missing dependencies

4.10.1 (2020-11-04)​

Fixed​

  • Removed scope provided for multiple dependencies so that other projects can depend on just Expanders instead of all related artifactsArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project.. Instead, build is managed with assembly descriptor.

Updated​

  • Merged changes from v4.8.2 release

4.10.0 (2020-10-29)​

Added​

  • [mapping] Any property or method calls to a composite implementing DelegatingComposite are delegated to the internal model object.
  • [mapping] Extensions can be added to ExtendableComposites to use them as regular properties in the mapping files

Updated​

  • Uses prime-core 2020.13.2 as source for elements classes instead of elements-shared etc.

4.9.4 (2020-10-30)​

Changed​

  • [fileUpload feature] Fixed improper handling of URI/File in file upload; improved error reporting

Fixed​

  • Fixed expansion using different encoding than harvestingHarvestingThe process of extracting and persisting custom code from anchors and ext directories back into source directories.

4.9.3 (2020-10-29)​

Added​

  • [persistence.xml] Use Hibernate 5's org.hibernate.jpa.HibernatePersistenceProvider when configured
    • to enable, add applicationInstanceOption hibernate.version : 5
    • by default (or when version is set to 4), we use the current org.hibernate.ejb.HibernatePersistence

4.9.2 (2020-10-20)​

Changed​

  • [internal] Internal reorganization
    • Moved src under ExpandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. module
    • Fixed expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact.-test-utils depending on expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact.-core instead of e-common + e-skeleton (to avoid cyclic dependency)

4.9.1 (2020-10-09)​

Added​

  • [maven] The component option maven.component.isJarModule will make sure the logic layerLayerLogical separation of functionality within a single system/application, focused on code organization. of your component is built as a jar module instead of an ejb module.
  • [internal] Added BlockingJobManager to run single-threaded for debugging
  • [perf] Added caching for ArtifactPathBuilder
  • [perf] Bunch of caching and general performance improvements

Fixed​

  • [utils] Updated isApplicable on ReporterExpander to only expand if the component has a dependency on utils

Changed​

  • [TreeToPrime] TreeToPrime expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. are now only active if the applicationInstance option enableTreeToPrime is defined
  • [js] plain AMD/RequireJS returns replaced with CommonJS-like exports
    • return { a : a }; vs var exports = {}; exports.a = a; return exports;
    • has no impact on runtime functionality
    • enables better module detection for VSCode+tsc+JS combination

Updated​

  • [internal] expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact.-skeleton updated expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. 4.0.2.2 -> 4.7.0
  • [internal] updated nsx-parent 2019.5 -> 2020.9.1

Removed​

  • [test] Removed deprecated ArtifactExpander#getContent
    • use ArtifactExpander#getContentWithoutFeatures or ArtifactExpander#getArtifact#getContent

4.9.0 (2020-09-30)​

This version releases changes made to make the metamodel-stack possible.
The most important feature is the introduction of expanders-core, which includes only the expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. infrastructure needed to expand anything.

Updated​

  • Merged changes from v4.6.x,v4.7.x, and v4.8.x (v4.8.1) releases

4.8.2 (2020-11-02)​

Added​

  • [valueFieldType] Added error message when referencing a valueFieldType that is not from the same component or from a componentDependency
  • [valueFieldType] Added error message finding a valueFieldType template which is not mapped to any valueFieldType in the model

Fixed​

  • [version fieldFieldA property of a DataElement expanded to a database column and user interface input element.] Added missing VersionField feature, which adds optimistic locking to a dataElement

4.8.1 (2020-09-25)​

Fixed​

  • [claims] Fixed some compile issues with java 7

4.8.0 (2020-09-24)​

  • [anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion.] Added several feature anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. to ProjectionPojoExpander
  • [workflow] Added claimInstances() method to claimable dataElements
  • [workflow] Added support in engineBean for runWorkflowWithEngineService() and runWorkflowWithTargets() methods

Changed​

  • [ui] Modified defineSearchBar() function to return an object containing the search fieldFieldA property of a DataElement expanded to a database column and user interface input element. value observable + calling it and storing the result in the page-after anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion..

4.7.1 (2020-09-30)​

Fixed​

  • Fixed issues with java_pojo.stg or ValueFieldTypeMapping.xml not being available in tests

4.7.0 (2020-09-08)​

Fixed​

  • Fixed css class of finderFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement. button in UI2
  • Fixed valueFieldType template loading to search for both name and fullType. (This fixes issues with DateTime on Linux)

4.6.0 (2020-06-29)​

Added​

  • The FinderBean will now skip any data queries where the result is expected to be an empty set, based on the count result or if the rowsPerPage is set to 0. Can be disabled with the option jpa.optimization.skipDataQuery.disable.

Changed​

  • All essential expanderExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. classes are now gathered in expanders-core. Expansion-resources should depend on this as much as possible instead of Expanders, so that they can be expanded without the need of the default expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. stack.
  • field-type-expanders contains essentials for value-fieldFieldA property of a DataElement expanded to a database column and user interface input element.-types
  • functional-key-expanders contains essentials for functional key dataRefs
  • Tester classes now use PrimeDataLoader from elements-ioxml, since it provides better support for additional data-resources outside prime-data.

4.5.6 (2020-08-26)​

Fixed​

  • [expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact.-tests-utils] Fixed loading of external DataResources when testing ExpandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact.

4.5.5 (2020-08-21)​

Updated​

  • Merged changes from v4.4.7-v4.4.12 to v4.5.5

4.5.4 (2020-08-17)​

Fixed​

  • Fixed css class of finderFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement. button in UI2
  • Fixed valueFieldType template loading to search for both name and fullType. (This fixes issues with DateTime on Linux)

4.5.3 (2020-07-03)​

Fixed​

  • Fixed java 11 warning about illegal reflective access

4.5.2 (2020-07-01)​

Fixed​

  • Fixed Ln03 setter in CrudsExpander by removing a reference to non-existent exception

4.5.1 (2020-06-16)​

Changed​

  • Updated commons-io to 2.7

Fixed​

  • Fixed read streams not being closed when comparing files for overriding

4.5.0 (2020-05-29)​

Added​

  • Added FeatureTester.isApplicable and FeatureTester.isNotApplicable

Changed​

  • Updated dependencies

4.4.12 (2020-07-02)​

Fixed​

  • Fixed Ln03 setter in CrudsExpander by removing a reference to non-existent exception

4.4.11 (2020-06-25)​

Fixed​

  • DataRefConverter now checks for empty Strings instead of just null values before parsing functional keys

4.4.10 (2020-06-15)​

Added​

  • Added custom and feature anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. to FinderBeanExpander

4.4.9 (2020-06-15)​

Added​

  • Added feature anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. to FinderBean

4.4.8 (2020-05-28)​

  • Internal cleanup

4.4.7 (2020-05-28)​

Changed​

  • Updated dependencies

4.4.6 (2020-05-28)​

Added​

  • Added several anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. to getData() and getDataRef() methods in the CrudsExpander
  • Added @anchor:includes to component struts XML

Fixed​

  • Fixed issue where DateLong fieldsFieldA property of a DataElement expanded to a database column and user interface input element. were not initialized as Date fieldsFieldA property of a DataElement expanded to a database column and user interface input element. in the forms, which created issues with the timezone conversions.

4.4.5 (2020-05-11)​

Added​

  • Ln03 fieldsFieldA property of a DataElement expanded to a database column and user interface input element. can now be imported and exported with csv files.

Fixed​

  • The shouldEngineRun method in engineBeans should now fail correctly is the engineService can not be found.

4.4.3 (2020-05-04)​

Changed​

  • EditorConfig now applied to all file types + some additional rules.

Fixed​

  • Fixed issue with graph options using the wrong page template
  • Fixed isRequired option for Ln03 fieldsFieldA property of a DataElement expanded to a database column and user interface input element.

4.4.1 (2020-04-27)​

Fixed​

  • Fixed OGNL List.exists not being registered for let inside included mappings.

4.4.0 (2020-04-24)​

Added​

  • ApplicationInstance or component options jpa.datasource will set the data-sources in the persistence.xml file. The value of the option should refer to the name of the custom data-source. The option jpa.datasource.nonjta can be added to define a specific non-jta data-source.
  • ApplicationInstance option jpa.entity.name.format will define the naming strategy for jpa entities. By default, this is the fully qualified java name. Alternative formats are:
    • java_underscore: fully qualified java name, but with . replaced with _
    • element: <component.name>.<element.name>
    • underscore: <component.name>_<element.name>

Changed​

  • RecursiveDirectoryCopier can now handle copying from zip files

Removed​

  • WebStylesDirectoryCopier has been moved to web-styles

4.3.10 (2020-04-27)​

Fixed​

  • (backport) Fixed OGNL List.exists not being registered for let inside included mappings.

4.3.9 (2020-04-16)​

Added​

  • Added jetty-schemas to WAR pom to go with JEE6+

Changed​

  • JavaEE version (technicalInfrastructure.jeeVersion) must be the spec name (5, 6, ...), and not a patch version ( 6.0.15)

4.3.8 (2020-04-14)​

Fixed​

  • [internal] Updated OGNL and removed use of single-equals comparator pre-processing of OGNL statements
    • ==/eq should now work as expected even on nulls (null == 'string') and non-Comparable objects (by using .equals() method instead of identity comparison)
    • OGNL assignment (=) is no longer broken, although its excessive use is not recommended

4.3.7 (2020-04-14)​

Fixed​

  • [internal] Fixed pre-compiled OGNL expressions being ignored sometimes

Changed​

  • [internal] Enabled mapping cache by default
    • disable with flag expanders.mappingReader.useCache in case of issues
    • if error occurs, the XML stacktrace is still likely incorrect, but expansion can be re-run with the cache disabled to (temporarily) get correct stacktrace

4.3.6 (2020-04-14)​

Added​

  • Added multiple anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. to InstanceViewHtmlExpander and ListHtmlExpander
  • Added multiple anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. to WebXmlExpander
  • Added support for src directories in applicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution. control directory. (disable with applicationInstance option disableControlSources)
  • Added HSTSFilterExpander, which adds a Strict-Transport-Security header to each response, which is activated by the applicationInstance option security.hstsHeader. The value of this option can set the content of the header if the default content does not suffice.

Fixed​

  • Fixed EngineBeanExpander missing extra imports for taskStatus and timerStatus where necessary
  • Fixed dataElement.LocalExpander running for REMOTE ejb policy.
  • Fixed dataElement.AgentLocalExpander running for REMOTE ejb policy.

Changed​

  • [elements-ioxml] ImportRunners now print the result of an import to the console
  • [elements-ioxml] TreeToPrime now correctly logs errors when updating instances during imports

4.3.5 (2020-04-02)​

Added​

  • Added isService flow option which adds logic to make a flow into a service.

Changed​

  • flag switch expanders.artifactPathBuilder.useJavaMapping is now enabled by default

Fixed​

  • Fixed EngineBeanExpander missing flowElement.targetClass imports when in a different package
  • Fixed EngineBeanExpander missing shutdown check in processBatch method
  • Fixed StateTransitioner's endTransition() not updating taskStatus

4.3.4 (2020-03-30)​

Fixed​

  • [knockout] fixed custom value field typesValue Field Type (ValueFieldType). [Deprecated] A deprecated specification defining how to store and represent the values of a ValueField, superseded by ValueTypes. rendering as [Object object]
  • Fixed duplication for defaultValue feature
  • Fixed issue with long types for defaultValue feature

4.3.3 (2020-03-30)​

Fixed​

  • Fixed KoListHtmlExpander not processing calculated fieldsFieldA property of a DataElement expanded to a database column and user interface input element.
  • Unfixed KoListHtmlExpander to match 3.x behavior
    • when name is not in isInfoField projectionProjectionA tailored subset of fields on a DataElement designed to encapsulate data for a specific technical or functional view., it is now ignored for all projectionsProjectionA tailored subset of fields on a DataElement designed to encapsulate data for a specific technical or functional view.
    • name fieldFieldA property of a DataElement expanded to a database column and user interface input element. is always forced first irrespective of declared fieldFieldA property of a DataElement expanded to a database column and user interface input element. order

4.3.2 (2020-03-26)​

Changed​

  • Updated maven plugins to their latest versions
    • compiler-plugin 3.8.1, maven-ear-plugin 3.0.2, maven-war-plugin 3.2.3, maven-ejb-plugin 3.0.1, build-helper-maven-plugin 3.0.0, maven-assembly-plugin 3.2.0
  • Added support for targeting JDK9 and higher
    • not specifying technicalInfrastructure.javaVersion now throws an exception instead of silently defaulting to 1.6
  • [experimental] added applicationInstanceOption experimental.maven.useIncrementalCompilation to speed up repeated builds
  • [experimental] added applicationInstanceOption experimental.maven.speedOverSize to enable caching and disable compression of ear/war builds
  • [experimental] set flag switches via expansionOption javaProperty.my.propertyName

4.3.1 (2020-03-26)​

Added​

  • [experimental] property flags can be set via environment variables as well
    • e.g. property 'expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact..artifactPathBuilder.useJavaMapping' or env 'EXPANDERS_ARTIFACTPATHBUILDER_USEJAVAMAPPING'
  • ApplicationInstanceOption struts.unauthorized will define the behaviour of the applicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution. when the user is unauthorized. If undefined or set to redirect, the applicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution. will redirect unauthorized users to the relogin page. If set to error-page, a dedicated unauthorized error-page will be expanded.
  • ApplicationInstanceOption struts.unauthorized.json will define the response on an unauthorized json request. The option value should be status <statusCode> where statusCode is 401 or another http status code. A result will be added to struts that returns this status code.
  • Feature anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. can add a sort option with the fully qualified name of a sorter class. This sorter class should implement Comparator<FeatureSegmentComposite>. Adding this will make sure the feature segments are sorted by the provided sorter class before being injected.
  • Added several custom and feature anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. in InstanceFormHtmlExpander and InstanceFormJsExpander

Changed​

  • ExpandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. will now generate more /gen/ directories on applicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution. level to prevent build failures if those directories are added to layerImplementations, but none of the related expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. were activated.

Fixed​

  • Fixed KoListHtmlExpander running only on info projectionProjectionA tailored subset of fields on a DataElement designed to encapsulate data for a specific technical or functional view. (fixes missing dataElement-dataProjection-ko-list.html files)

4.3.0 (2020-03-19)​

Added​

  • [experimental] The fieldFieldA property of a DataElement expanded to a database column and user interface input element. option defaultValue will provide a default fieldFieldA property of a DataElement expanded to a database column and user interface input element. value for all new instances. E.g. add defaultValue: true to a Boolean fieldFieldA property of a DataElement expanded to a database column and user interface input element. to set it to true by default or add defaultValue: 'new name' to a String fieldFieldA property of a DataElement expanded to a database column and user interface input element. to provide 'new name' as initial value.

Changed​

  • ExpandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. now require Java 8+
  • Struts ExpandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. now target either Struts 2.3 or Struts 2.5, with Struts 2.5 being the default
    • to use struts 2.3, add applicationInstanceOption struts.version with value 2.3
    • requires nsx-runtime, baseComponents, and prime-data 2020.5.0+
  • Soft delete on modify with disabled=yes is now opt-in behind applicationInstanceOption('cruds.softDeleteOnModify')

Fixed​

  • Applicable layersLayerLogical separation of functionality within a single system/application, focused on code organization., layerLayerLogical separation of functionality within a single system/application, focused on code organization. implementation technologies, and library technologies are now properly filtered when building POM dependency/dependencyManagement lists.

Removed​

  • Removed Struts2View feature for unused Struts view layerLayerLogical separation of functionality within a single system/application, focused on code organization.

4.2.7 (2020-03-16)​

Added​

  • New anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. in BeanExpander (CsvFeature):

    • anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion.:custom-post-import
    • anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion.:custom-post-export
    • anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion.:custom-import-unsupported
    • anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion.:custom-export-unsupported

  • New anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. in CsvExporterImplExpander:

    • anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion.:custom-post-export
    • anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion.:custom-map-instance

  • New anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. in CsvImporterImplExpander:

    • anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion.:custom-post-import
    • anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion.:custom-post-persist

Changed​

  • Methods importFile() and export() in bean now define an importResult or exportResult, which is returned at the end of the method. This allows for new anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion.. Though usual customisations should not be broken, it might be worthwhile to check whether the code may need to be cleaned up.

4.2.4 (2020-02-26)​

Added​

  • custom-access-info-stack and custom-access-info-default-style-stack anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. added to account security stack in struts header xml.

Changed​

  • Loosened encoding generated artifactsArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project..

4.2.2 (2020-02-21)​

Changed​

  • ioxml client expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. now use CliParser from nsx-runtime/nsx-shared-cli
  • Moved initialization of agent in CommandPerformer to prepare method to allow custom interceptors to provide an alternative UserContext.
  • Adjusted the encoding so that all templates are read as UTF-8 and all artifactsArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project. are generated to the same encoding.

Added​

  • Struts fieldFieldA property of a DataElement expanded to a database column and user interface input element. errors are now translated to CommandResult errors in the CommandPerformer action class.
    • Disable with applicationInstance option struts.disableStrutsErrorsToCommandResult.

4.2.1 (2020-02-11)​

Changed​

  • If the fieldFieldA property of a DataElement expanded to a database column and user interface input element. option generateUuid is given the value if_empty, the fieldFieldA property of a DataElement expanded to a database column and user interface input element. will only be set with a new UUID (on create) if the fieldFieldA property of a DataElement expanded to a database column and user interface input element. was empty.
  • Expanded EditorConfig now includes support for .html files.

4.2.0 (2020-02-07)​

Added​

  • Added runExpansionStep() method to ExpanderTester and FeatureTester to run expansionSteps before testing. This can be useful if the expansionStep adds an option to the model or applies some other modification necessary for the test.
  • ProjectionProjectionA tailored subset of fields on a DataElement designed to encapsulate data for a specific technical or functional view. pojo's getDataRef() methods now return typed DataRef classes if functionalKey is defined
  • Otherwise, the getDataRef() methods return DataRefs with component, packageName and className filled in
  • EditorConfig file, which is applied to all gen (and gen_test) folders to ensure a consistent code formatting. This can be disabled using the ApplicationInstance option editorconfig.disabled. The rules can also be applied globally ( also to ext and test) using the ApplicationInstance option editorconfig.global.
  • The fieldFieldA property of a DataElement expanded to a database column and user interface input element. option generateUuid will inject code to generate a new UUID in the create-afterProjection feature anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion. of the cruds create method. This will ensure that a new UUID is generated and stored for these fieldsFieldA property of a DataElement expanded to a database column and user interface input element. when an instance of the DataElement is created. The option is applicable to fieldsFieldA property of a DataElement expanded to a database column and user interface input element. with a String or byte[] storage type.
  • For all active technologies a gen_test folder will be expanded with java and resources subfolders to allow expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. to expand unit tests that can be harvested.

Changed​

  • Struts ExpandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. now target Struts-2.5
    • requires baseComponents 2020.2.0+ and nsx-runtime 2020.2.0+
  • Behavior of suffix parameter for feature anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. is now the same as the behavior of the suffix parameter in inline feature anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion.. This means that the suffix will now be placed only after the last feature injected. The separator parameter is now also available, which places the separator in between all features. The combination of the separator and suffix parameters will mimic the previous behavior suffix, where it was placed after every injected feature. A prefix parameter was also added just as it is available in inline feature anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion.. The prefix is placed in front of the first feature. E.g. @anchor:featurename(suffix : ', ')' is now @anchor:featurename(separator : ', ', suffix : ', ')'.

Fixed​

  • Fixed bug in ExpansionJobManager that in some occasions would skip additional tasks added by additionalExpansionStep.

4.1.1.1 (2020-02-07)​

Fixed​

  • Fixed issue with manyToMany fieldsFieldA property of a DataElement expanded to a database column and user interface input element. in old UI. The issue was caused by initializing the fieldsFieldA property of a DataElement expanded to a database column and user interface input element. incorrectly in the <dataElement>-ko-mapper.js scripts.

4.1.1 (2020-01-22)​

Fixed​

  • Fixed TaskElement Proxy using getTaskRemoteName for LOCAL-only lookup

4.1.0 (2020-01-22)​

Removed​

  • Pre-rewrite (< v4.0.0) expanderExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. classes have been removed. If they are necessary nonetheless, add a expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. 3.2.1.7 or lower to the classpath

Added​

  • Added before-harvest and after-harvest phases to the harvest runner.
  • Added ExpansionStepTester class to facilitate the implementation of tests of applicability conditions for additional expansion steps.
  • Added custom-annotations-getter-id and custom-annotations-setter-id anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. in Data class.

Changed​

  • <Element>Cruds::project() now takes Context as input and only Data objects of the correct DataElement
  • Removed noCache result parameters from StrutsElementExpander. To reinsert them, use applicationInstance option struts.useNoCacheResult. These parameters have been removed because they overwrote the behaviour of the NoCachingInterceptor, which is more complete.
  • Value field typeValue Field Type (ValueFieldType). [Deprecated] A deprecated specification defining how to store and represent the values of a ValueField, superseded by ValueTypes. pojo comparison will now use identity comparison by default
  • Value field typeValue Field Type (ValueFieldType). [Deprecated] A deprecated specification defining how to store and represent the values of a ValueField, superseded by ValueTypes. pojo now provides a default hashcode function. Any custom implementation needs to be moved into the custom anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion.. This can be disabled by adding componentOption valueFieldType.disableHashCodeMethod.
  • Table names are now escaped in the @Table annotations in the Data classes. This prevents collisions with reserved words in certain databases, such as User in SQL Server. This behavior can be disabled with the ApplicationInstanceOption db.schema.disableEscapeTableName.

Fixed​

  • ValueFieldTypePojoExpander now only runs if valueFieldType.customTransportClass is false
  • Classes interacting with trees will now use the actual fieldFieldA property of a DataElement expanded to a database column and user interface input element. name for children instead of the name of the child dataElement.
  • Fixed names for abbreviations in translation files (e.g. 'ETB' instead of 'e t b')
  • CALCULATED_FIELD with isRequired are no longer added to Projector's checkRequired()
  • CALCULATED_FIELD with custom valueFieldType now correctly returns valueTypeClass in Cruds
  • @expanderComment in test STG templates is no longer tied to specific comment formats

4.0.9.1 (2020-01-08)​

Fixed​

  • Added missing imports for FunctionalKeyDataRefExpander
  • Functional key dataRefs toString() methods now return "" when on errors
  • Functional key dataRefs toString() methods will null-check values before converting to avoid nullPointerExceptions and "null" strings

4.0.9 (2020-01-06)​

Added​

  • Added expanderResource name to expanderComment
    • e.g. <!-- expanded with nsx-expanders:4.0.9-SNAPSHOT, expansionResource org.normalizedsystems:sand-castle-expanders:1.0-SNAPSHOT -->
  • [experimental] Updated java-mapped ArtifactPath
    • toggled by -Dexpanders.artifactPathBuilder.useJavaMapping=true|false (false by default)
  • [experimental] Updated mapping cache corrupting XML stacktrace (disabled in 4.0.7.2)
    • toggled by -Dexpanders.mappingReader|mappingFactory.useCache=true|false (both false by default)
  • [experimental] Stop expansion on first error instead of collecting all failures first
    • toggled by -Dexpanders.expansion.failFast=true|false (false by default)
  • Added basic test-template caching

Fixed​

  • ExpanderExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact./... Tester method lookup now searches for org.junit.Test or org.junit.jupiter.api.Test annotated method in stacktrace

4.0.8.2 (2019-12-17)​

Changed​

  • Always use prime-data's expansionResource.xml

Fixed​

  • Fixed <elementTypeName>any</elementTypeName> failing type validation

4.0.8 (2019-12-16)​

Fixed​

  • CompositeFinderExpander: removed exception for dataElements with a parent which does not have a reverse fieldFieldA property of a DataElement expanded to a database column and user interface input element. and replaced it with a customizable method

Added​

  • New anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. to StateTransitioner:

    • anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion.:custom-interim-before
    • anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion.:custom-interim-error
    • anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion.:custom-interim-after
    • anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion.:custom-failed-before
    • anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion.:custom-failed-error
    • anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion.:custom-failed-after
    • anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion.:custom-end-before
    • anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion.:custom-end-error
    • anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion.:custom-end-after
    • anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion.:custom-revert-before
    • anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion.:custom-revert-error
    • anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion.:custom-revert-after

  • New anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. to DataRefConverterExpander:

    • anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion.:custom-formatX

Changed​

  • Extracted creation and update of TaskStatus instances in StateTransioner to WorkflowTaskStatus feature

4.0.7.7 (2019-12-06)​

Changed​

  • Updated dependencies

4.0.7.6 (2019-12-06)​

Fixed​

  • Added encoding of the HTML document to artifactsArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project. generated by PageHtmlExpander and IoPageHtmlExpander
  • Fixed indent of PageHtmlExpander

Added​

  • New anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. to PageHtmlExpander and IoPageHtmlExpander:

    • anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion.:custom-head
    • anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion.:custom-script

4.0.7.5 (2019-12-02)​

Added​

  • Added SVG comment format

Fixed​

  • Fixed expansion and harvest directories using applicationInstance.shortName instead of application.shortName
  • <Composite>ExpansionContext is now validated against <expanderComposite.elementTypeName>

4.0.7.3 (2019-11-21)​

Added​

  • Added artifactModifiers fieldFieldA property of a DataElement expanded to a database column and user interface input element. to ExpanderExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. which allows variables to be defined in ognl which can be used in the artifactName and Path

    Example of how to use it:


<expander name="...">
  <!--...-->
  <artifactModifiers>#{
  'postfix' : taskElement.getOption('useLocalInterfaceName').defined ? 'Local' : 'Remote'
  }
  </artifactModifiers>
  <artifactName>$taskElement.name$$postfix$.java</artifactName>
</expander>
  • FieldFieldA property of a DataElement expanded to a database column and user interface input element. elements are now expandable

4.0.7.2 (2019-11-12)​

Fixed​

  • Disabled caching of mapping files to prevent stacktrace from being corrupted

4.0.7.1 (2019-11-08)​

Added​

  • DataExpander now adds length property for BigString
    • @Column(columnDefinition="varchar(X)") becomes @Column(columnDefinition="varchar(X)", length = X)

Removed​

  • Obsoleted JaxRs struts features

4.0.7 (2019-11-03)​

Added​

  • [testing] Added dependency on expanded onion specs
  • [testing] Use expanded ExpansionContext factories for tests setup

Changed​

  • [testing] Default applicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution. and component expansion directories are C:/APPLICATION_ROOT and C:/COMPONENT_ROOT

4.0.6.3 (2019-10-29)​

Fixed​

  • CommandFormHtmlExpander now correctly expands Ln03/Ln06 fieldsFieldA property of a DataElement expanded to a database column and user interface input element.
  • CommandPojoExpander initializes collections fieldsFieldA property of a DataElement expanded to a database column and user interface input element. to placate struts

4.0.6.2 (2019-10-28)​

Changed​

  • Deprecated (original) hand-written onion specs

4.0.6.1 (2019-10-25)​

Added​

  • Implemented disableExpansionTrace expansionOption to speed up expansion. This disables the gathering of meta-data, used by the codeImport, reporting and nsx-model-querying.

Changed​

  • Errors in cruds are now logged at ERROR level instead of INFO.
    • To revert the behavior, use applicationInstanceOption logging.cruds.degradeErrorToInfo. Note that this option will be eventually removed.

4.0.6 (2019-10-18)​

Added​

  • new anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. in net.democritus.expanderExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact..knockout.dataElement.SortingJsExpander:

    • anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion.:custom-variables
    • anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion.:custom-sorting-columns
    • anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion.:custom-get-sort-fields
    • anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion.:custom-after

4.0.5.3 (2019-10-14)​

Added​

  • new anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion. in net.democritus.expanderExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact..common.projectionProjectionA tailored subset of fields on a DataElement designed to encapsulate data for a specific technical or functional view..DataRefProjectorExpander:

    • anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion.:custom-toData-setters

4.0.5.2 (2019-10-11)​

Fixed​

  • Remove duplicate anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion. in CrudsExpander:

    • anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion.:custom-variables

4.0.5.1 (2019-10-10)​

Fixed​

  • Downgrade persistence.xml version for JOnAS server

4.0.5 (2019-10-08)​

Added​

  • new anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion. in net.democritus.expanderExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact..ejb3.serviceElement.EngineBeanExpander:

    • anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion.:custom-after-loop

  • new anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. in net.democritus.expanderExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact..common.projectionProjectionA tailored subset of fields on a DataElement designed to encapsulate data for a specific technical or functional view..ProjectorExpander:

    • anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion.:custom-toData-setters
    • anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion.:custom-project-setters
    • several feature anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. (used by expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact.)

  • Added OpenJPA automatic schema updating that is enabled by default

  • Added applicationInstanceOption persistence.schemaUpdating to control automatic schema generation

    • none/empty or 'update' to enable, 'none' to disable

  • Added applicationInstanceOption experimental.cruds.failOnProjectionNotFound

    • return CrudsError when elements are not found via Cruds instead of CrudsSuccess(object-with-empty-fieldsFieldA property of a DataElement expanded to a database column and user interface input element.)

  • Added ExpansionComposite to ExpansionConfigurationExpansionContext, which can be used in expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. to access meta information of the expansion (artifactsArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project., custom insertions ...).

  • Added expansion option exportTraceZip, which creates a zip which contains information on the expanded artifactsArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project., custom insertions etc. This will replace the default expansion of artifactsArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project..

  • Add expansion option skipPhase which lets you define which phases to skip during expansion (e.g overlay)

  • Added XML Schema to persistence.xml and updated version from 1.0 to 2.2

Changed​

  • Using JDNI appName lookup (java:app/AppName) is now behind jndi.appName applicationInstanceOption
  • persistence.xml version updated to 2.2
  • ECLIPSELINK schema updating changed from create-tables to create-or-extend-tables
  • [struts] PerformerExpander now returns TaskResult.error() on perform failure

4.0.4 (2019-08-27)​

Added​

  • Expansion option harvestBaseComponents will make sure the baseComponents are harvested, as they are ignored by default.
  • Component Option cascadeDelete will add cascading delete for all collection fieldsFieldA property of a DataElement expanded to a database column and user interface input element. with option aggregate: composite

    This option requires the option enableComposites to work

Fixed​

  • Used application.shortName instead of applicationInstance.shortName during expansion
  • Removed dependencies on validationImplementation
  • Fixed issues with xml tag and directory names for ioxml

4.0.2.5 (2019-08-12)​

Added​

  • new anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. in net.democritus.expanderExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact..ejb3.flowElement.EngineBeanExpander

    • anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion.:custom-orchestrate-before
    • anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion.:custom-orchestrate-after
    • anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion.:custom-batchDescription
    • anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion.:custom-processBatch-before
    • anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion.:custom-processBatch-after
    • anchorAnchorA marker within generated source code reserved for adding custom logic during re-expansion.:custom-processTask-after

  • ExpanderExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. for CompositeToTree (ioxml)

4.0.2.4 (2019-08-02)​

Fixed​

  • Fixed default constructor of functional dataRefs to set componentName, packageName and elementName
  • Migrated latest changes to ioxml expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. to composite-based expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact.

4.0.2.3 (2019-08-01)​

Fixed​

  • Fixed target paths of both *-io-page-model.js and *-io-page.html file
  • Fixed error logs for import/export

4.0.2.2 (2019-07-30)​

Fixed​

  • Fixed external meta-expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. being ignored (since 4.0.1.6)

4.0.2.1 (2019-07-19)​

Fixed​

  • Fixed StringFile not sending the uploaded file to server

4.0.2 (2019-07-12)​

Added​

  • ExpansionOptions excludeExpanders, excludeFeatures and excludeExpansionSteps to exclude expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. etc. from running.
  • ExpansionOptions includeExpanders to select specific expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. to run.
  • ExpansionOption hideAnchors to hide all non-custom anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion.
  • AdditionalExpansionSteps can introduce new jobs to the ExpansionJobManager to make external expansionRunner possible

4.0.1.7 (2019-07-10)​

Fixed​

  • Fixed issues with component-level overlay
  • Fixed issues with combination nameNotWanted + hasDisplayName not showing any names

4.0.1.3 (2019-07-04)​

Fixed​

  • Fixed issues with fieldsFieldA property of a DataElement expanded to a database column and user interface input element. with type CALCULATED_FIELD in ListHtmlExpander and InstanceViewHtmlExpander (UI2)

4.0.1.2 (2019-06-26)​

Added​

  • Added missing dynamic DEPLOYMENT_NAME in ComponentMetaData for modern applicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution. servers

Fixed​

  • Fixed nullPointerException in functionalKey dataRef to string method
  • Fixed issue with ValueFieldTypes in validators.xml

4.0.1.1 (2019-06-25)​

Fixed​

  • Fixed issues with Service Element ExpandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact.
  • Fixed noDataLayer option being ignored
  • Fixed issues with full import of a new applicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution.
  • Restored names of enums for DataState to be backwards compatible with some edge cases

4.0.1 (2019-06-21)​

Added​

  • DataElements can define the option functionalKey

  • The flow option setBatchFinder will allow you to modify the finderFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement. used to find the next batch in your EngineBean

  • FindersFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement. can now use the Se (strictly equals) operator. In this case, only the = operator will be used in JPA and not, in case of a String, the LIKE operator.

    The Se operator can be used to e.g. findByStatusSe, which can then be used in the setBatchFinder option to avoid using a slow LIKE operator in your engineBean.

Changed​

  • In previous versions, if a linkfield was set in the Cruds-class, any failure to find the linked instance would be ignored and the link would not be said. The setters have now been made stricter and will throw an exception should this occur. In order to avoid this behavior, use the application instanceApplication Instance (ApplicationInstance). A target technology configuration defining how an application's architecture layers are built and executed. option disableStrictLinkMode.

    This will prevent the cruds layerLayerLogical separation of functionality within a single system/application, focused on code organization. from silently ignoring incorrect link fieldsFieldA property of a DataElement expanded to a database column and user interface input element. during an import.

Fixed​

  • A bug has been fixed where a Ln02 link fieldFieldA property of a DataElement expanded to a database column and user interface input element. could not be set to null. This fix can be disabled with the applicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution. instance option disableFixNullableLn02.

4.0.0 (2019-06-12)​

Added​

  • Option hasTranslation now works for name fieldFieldA property of a DataElement expanded to a database column and user interface input element. and findByNameEq finderFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement.
  • Option hasTranslation on fieldFieldA property of a DataElement expanded to a database column and user interface input element. will be used for the translation of the corresponding findersFinderA search specification combining field-operator pairs to execute standard data queries on a DataElement. the translation properties for the English translation will now contain correct English translations the pom.xml files of different layersLayerLogical separation of functionality within a single system/application, focused on code organization. may contain new source and resource directories to be more consistent with the ANT build

Fixed​

  • Options no*Layer are now correctly applied, mainly when added as component options. If any artifactsArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project. are missing, check for options

Changed​

  • Rework of the expanderExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. framework. The features of the expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. have been kept the same as the previous versions. The biggest changes will be in the use and extension of the expansion. There might be some small variations/improvements to the previous versions.
  • The classes in the client layerLayerLogical separation of functionality within a single system/application, focused on code organization. have been changed to allow version transparency between changes of a dataElement
  • The order of harvested anchorsAnchorA marker within generated source code reserved for adding custom logic during re-expansion. may change. Therefore it is best to harvest and commit these changes before making any functional changes. For more information, see harvest sorting.
  • The expansion from the PR will now take the CustomRepository of your components in account when expanding the applicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution.. Which means that if this repository is different from the customRepository of the applicationInstance, the expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact. might be looking in the wrong harvest directories. To fix this, make sure that there is only one directory named after the component in all used source bases.