enhancement
critical
major
minor
minor
#25907
Layout editor: inconsistent behavior of unfold state, selection and reaction to object creation
#25951
Application tests: CheckLabeledExecutabilityOp fails to assert non-executability of literal ResKey reasons.
#25952
Model Editor: Enum default provider does not work for enum references for which singleton link storage was explicitly selected
#26002
ConfigurationItem-valued properties with format annotations may cause an attempt to create abstract config items when deserializing null values
#26012
Help editor crashes when a user has chosen a language that is not in the supported languages of the application
#26039
Gridcomponent: Display of context menu for new (transient) row object leads to UnsupportedOperationException
#26085
An attribute of type tl.model.search:Expr is not displayed in the form above a TL script editor
#26111
Context menu commands for table rows are erroneously executed on the table model when opening the context menu in the background of the table
#26153
Migration: Replay fails if string values with line breaks are contained in the dataset where a line ends with a semicolon
#26171
A TL script expression entered in a wizard template is reformatted when transferred to the final template
#26223
TL script: Under unfavorable conditions wrong parameter values when evaluating local functions
enhancement
The `configFile` property allows you to specify an XML configuration file that should be loaded as the last overridden configuration when the application starts. This enables you to inject a configuration fragment into a deployed application "from the outside" in order to adapt the configuration to the environment.
With this approach, it is not possible to easily switch the database connection because predefined configuration snippets such as db-mysql.xml or similar cannot be loaded in this way.
Improvement
Instead of referencing an XML file, it is better to reference a configuration directory that contains a metaConf.txt file. In this file, you can then either reference deployment-specific configuration files in the same directory or load configuration fragments provided by the application.
The environment variable `configFile ` is too general, which can lead to conflicts with other environment variables. Instead, ` tl_config ` should be used.
The project.developer property should be removed. Instead, the tl_config environment variable can be set in the Eclipse settings to point to a developer-specific configuration directory (which should also no longer be checked in).
Code Migration
- The name of the environment variable ` configFile ` is now ` tl_config`. **This requires migration, particularly on installed systems.**
- The option to specify the configuration file name via the property <ContextName>.<ApplicationName>.configFile has been removed. Instead, the property <ContextPath>_tl_config must be used. For example, if the application is running on localhost:8080/myApp, the property myApp_tl_config must be used. If the application is running as root (e.g.,localhost:8080/), ROOT_tl_config must be used. **This requires a migration on installed systems in particular.**
- The option to specify the name of the configuration file via the <ApplicationName>.configFile property has been removed. Here, too, the <ContextPath>_tl_config property must be used. **This requires a migration, particularly on installed systems.**
- The property `project.developer ` has been removed. If the developer requires a specific configuration, this configuration file can be placed in a folder outside the WS, and an entry `-Dtl_config=<pathToConfig> ` can be added to the JRE arguments in Eclipse. If an even more specific file is required for a particular project, this can also be specified here. For example, if Prime is accessible via the context path /pmt, the option -Dpmt_tl_config=<pathToPrimeConfig> can be used to specify a different file for Prime.
- Deleted configurations: r303502.
Test
TestMultiProperties#testAdditionalConfigFolder()