CAMEL-24204: Fix exposeListenerSession catalog metadata wrong default value#24939
Conversation
… value Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Signed-off-by: Claus Ibsen <claus.ibsen@gmail.com>
gnodet
left a comment
There was a problem hiding this comment.
Clean metadata fix. The field exposeListenerSession has been initialized to true since 2007, and Spring's AbstractMessageListenerContainer also defaults to true, but the @UriParam annotation was missing defaultValue = "true" — causing the catalog JSON to report false as the default.
One source line change in JmsConfiguration.java, all other files (catalog JSON, component-dsl, endpoint-dsl for jms, amqp, activemq, activemq6) are correctly regenerated.
Claude Code on behalf of gnodet — AI-generated review
|
🌟 Thank you for your contribution to the Apache Camel project! 🌟 🐫 Apache Camel Committers, please review the following items:
|
|
🧪 CI tested the following changed modules:
🔬 Scalpel shadow comparison — Scalpel: 15 tested, 26 compile-only — current: 12 all testedMaveniverse Scalpel detected 41 affected modules (current approach: 12).
|
Summary
The
@UriParamannotation onJmsConfiguration.exposeListenerSessionwas missingdefaultValue = "true". The Java field initializer has beentruesince 2007, and Spring'sAbstractMessageListenerContaineralso defaults totrue, but the generated catalog metadata (jms.json) reported"defaultValue": false.This caused the Camel documentation website and any tooling reading the catalog JSON to show the wrong default value.
Fix: Added
defaultValue = "true"to the@UriParamannotation, matching the pattern used by all othertrue-default booleans in the same class (e.g.,autoStartup,deliveryPersistent,mapJmsMessage). The fix propagates to downstream components (AMQP, ActiveMQ, ActiveMQ6) via regenerated catalog, component-dsl, and endpoint-dsl artifacts.Claude Code on behalf of davsclaus
🤖 Generated with Claude Code