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
#27042
MaintenanceJspBase should write to the log first, then to the client, instead of the other way around.
In tl:MaintenanceJspBase, calls to printXXX(...) should first log the message and then write it to the client, rather than the other way around as was previously the case. There is a concern that writing to the client may fail due to an exception. In particular, accessing or using the JspWriter may fail if the session no longer exists. Maintenance pages may run for so long that the session is terminated by a timeout. The problem with this is that, as a result, nothing would ultimately be sent anywhere. Even logging this exception would fail, because that is also done via one of the affected methods.
Test
No test: It is practically impossible to test where the data is written first without modifying the code.