TopLogic - the automated application engine
  • Releases
  • Dokumentation
  • Github
  • Discord
  1. Home
  2. Releases
  3. TL_8.0.0-alpha6
  4. #29269

8.0.0-alpha6
TopLogic Release

2026-07-14

enhancement

minor
#29334
Status code as argument for responses in REST requests

defect

major
#29223
Commands configured directly in the dialog cannot be granted permissions.
#29269
Kafka: Error when handling null messages
#29272
Import in help editor does not work
#29325
Generated JSON schema marks a non-nullable layout-template property (dialog title) as nullable/optional
#29338
CreateTLSingletonProcessor creates duplicate annotations
#29373
Buttons Do Not Respond to Programmatic DOM Clicks (UI Test Automation with Playwright)
minor
#28685
Authorization Issues in Model-Based Search
#29009
Selection in tree invisible if "Expand on selection" is not selected
#29322
Configuration Command Undo vs List of changes
#29330
TreeTableComponent / TreeComponent loses state on invalidate
#29331
Zoom level to be retained
#29339
Failed migration in #28305
#29340
TL Script: Optimizing database queries with transient objects fails
#29367
Error in the TL Script Compiler when parsing HTML literals as the first expression in a block
#29371
Values of macro attributes are not displayed
#29372
Flowchart: Problems with a compact tree layout and overlapping elements in combination with a zigzag display
#29379
Script Recorder: Details Can No Longer Be Edited After Moving a Selected Action
defect

major

#29269

Kafka: Error when handling null messages

IntegrationAPI

Currently, an empty message (value = null) on a Kafka topic in the consumer leads to a NullpointerException and thus blocks further message processing.

Cause:
The ConsumerDispatcher logs the processing of each message ('record') and forwards the content (record.value()) of the message to the KafkaStringLogWriter. In the writeMetaData() method, a NullpointerException occurs when accessing the value ('message') of the message.

The message then remains on the topic and the consumer tries to process it again and again, which always leads to the same problem. The processing of further messages is thus blocked.

  • Get Started
  • Github
  • Discord
  • Das Unternehmen hinter TopLogic
  • Softwareentwicklung heute
  • Kontakt

© Copyright – Business Operation Systems GmbH

  • top-logic.com
  • Nutzungsbedingungen
  • Impressum
  • Rechtlicher Hinweis
  • Datenschutz
  • DE
  • Login