Major
Detail
Major
Detail
#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.
Enhancement
Currently Top-Logic uses Log4j version 1.2.17. But the 1s versions are not supported anymore. And the 2s versions of Log4j before 2.1.15 have a critical security vulnerability. Either Log4j needs to be replaced entirely or upgraded to a current version.
Implementation
Log4j 1.2.17 has been replaced by version 2.17.2.
Code migration
- Note: If there are problems, Log4j can be switched to debug mode:
- To do this, define the following property empty: log4j2.debug, i.e.: -Dlog4j2.debug
- See also: https: //logging.apache.org/log4j/2.x/faq.html#troubleshooting
- The Log4j configuration must be changed to XML format.
- The standard configuration of the framework serves as a template: /com.top_logic/src/main/webapp/WEB-INF/conf/logging/default.xml
- Official documentation:
- There is no longer an automatism that creates a logging configuration during deployment. This must be created manually.
- The Ganymede plugin for Eclipse no longer works with Log4J2. Instead, the Ganymede2 plugin can be used, which can be installed via this update site: https://dbusche.github.io/Ganymede2/
Test
- Toggle logging settings and check if e.g. stacktraces are logged with debug.xml.