major
minor
major
minor
#26382
Error messages "Duplicate tag name..." when starting an application in the IDE from a TL-Studio
#26405
TTypeRewriter logs warning "Unable to resolve items by external reference" also unnecessarily
#26431
Changed superclass relationship leads to changed attribute list in the form editor only after a restart
#26484
In-app template for grid and tables: Function "Verifier for use as list item" does not get component model
#26536
When rendering HTML from TLScript expressions, configured renderers are not taken into account
#26797
Transaction with user input: invisible properties of the form model cannot be assigned values (initialized)
#26885
Constraints on declarative forms with arguments from a container reference lead to errors for new elements
#26921
ClassCastException when evaluating security rules that refer to (non-structuredElement) singletons of a module.
#26922
With generated subject classes, a default provider of an attribute in a non-structure class does not get a create context
#26988
In-app documentation generator does not extract documentation for overwritten config properties
#27027
Declarative forms: SelectField disappears after upload if option list depends on mandatory property
#27042
MaintenanceJspBase should write to the log first, then to the client, instead of the other way around.
defect
minor
#26529
Model transfer to development environment: ResKeys remain in dynamic properties
When the model is imported into the development environment, dynamic ResKeys are imported into the module-specific translation tables (e.g., attribute names), but are not yet removed from the dynamic translation tables.
However, this should occur in order to distinguish between static and dynamic translations.
Code Migration
In application configurations, the <static-bundles> tag must be removed from the resource bundle definition:
From
#!xml
<config service-class="com.top_logic.basic.util.ResourcesModule">
<instance class="com.top_logic.util.resource.analyzer.IDEResources">
<static-bundles>
<bundles>
<bundle name="test.polymorphismMessages"/>
</bundles>
</static-bundles>
</instance>
</config>
make
#!xml
<config service-class="com.top_logic.basic.util.ResourcesModule">
<instance class="com.top_logic.util.resource.analyzer.IDEResources">
<bundles>
<bundle name="test.polymorphismMessages"/>
</bundles>
</instance>
</config>
Test
- Create a new module in the app with its own translation.
- Log out and log back in, then verify that the translations are still present.
- Reboot and verify that the translations are still present.
- Deploy the module to the development environment.
- Verify that the translations are still present.
- Shut down, make changes to the module, and update the exported translations in the files.
- Start up the system and verify that the changes have been applied.