gnodet commented on PR #25232: URL: https://github.com/apache/camel/pull/25232#issuecomment-5141229285
_Claude Code on behalf of Guillaume Nodet_ @apupier Thanks for the review! Both points addressed in the latest push: **1. Narrowed the catch scope:** The `JMSException` catch now only applies to JMS vendor-specific properties (those with a `JMS_` prefix, per JMS spec section 3.5.1). For all other properties, the exception is re-thrown as before — so there is no behavioral change for user-defined properties. The log level has also been raised from `DEBUG` to `WARN` for better visibility. Regarding your question about a reserved properties list: there is no standard JMS API to query which vendor properties are reserved. The set varies by provider and can change between versions (IBM MQ 10.0 made `JMS_IBM_MsgToken` read-only, which was writable in 9.x). The `JMS_` prefix check is the most reliable approach — it matches exactly the vendor-specific namespace defined in the JMS specification, and only those properties can be provider-reserved. **2. Upgrade guide entries added:** Two new sections in `camel-4x-upgrade-guide-4_22.adoc`: - **camel-jms - IBM MQ client upgraded to 10.0** — documents the major version bump - **camel-jms - vendor-specific JMS properties skipped when read-only** — documents the behavioral change, noting it only affects `JMS_`-prefixed properties -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
