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.
enhancement
Currently, the ports for Kafka and ZooKeeper can only be changed by creating new configuration files. In particular, it is not possible to specify them externally via system properties.
Improvement
An alias, including a system property, should be introduced for both the ZooKeeper port and the Kafka port.
Implementation
| = Port Configuration = | = **Kafka** = | = **!ZooKeeper** = |
| =Default = | 9092 | 2181 |
| =Alias = | %KAFKA_PORT% | %ZOO_KEEPER_PORT% |
| =System Properties = | kafka_port | zoo_keeper_port |
| =Example = | -Dkafka_port=1234 | -Dzoo_keeper_port=5678 |
Test
- Change the Kafka and ZooKeeper ports using System Properties.
- Start ZooKeeper, Kafka, and the Kafka demo.
- Create a "node" and verify that the corresponding "remote nodes" are created.
- Verify that the new ports are actually being used instead of the old ones. To do this, configure the three components inconsistently, start them, and verify that they do not work:
- ZooKeeper port is inconsistent: Kafka aborts startup with a corresponding error message.
- Kafka port is inconsistent: The application starts, but no “remote nodes” are created.