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
If there are problems with Kafka or TL-Sync, sending and receiving is repeated indefinitely at high frequency. This floods the log.
Improvement
When a problem occurs, the interval between attempts should increase exponentially, to a maximum of perhaps once per hour, or maybe even just once per day.
Application
No migration or customization of the application is necessary. Sending and receiving slows down automatically when errors occur. A "truncated exponential backoff" is used.
If the default settings for this in an application are not suitable, they can be adjusted. See the configurations of tl:KBDataProducerTask and tl:ConsumerDispatcher.
Test
- Break sending via Kafka. For example by starting the application without Kafka.
- Create data that will be transmitted.
- Sending must fail with stacktraces in Kafka log. The stacktraces must become less frequent over time.
- Fix the sending.
- Break the receiving.
- Create data that will be transmitted.
- Receiving must fail with stacktraces in the Kafka Log. The stacktraces must become rarer with time.