[
https://issues.apache.org/jira/browse/CAMEL-26505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-26505.
---------------------------------
Resolution: Fixed
Fixed by https://github.com/apache/camel/pull/28987 (merged to main as
403acb0ca8c18d1f607698c28b077bf4c0f3f8d9).
_Claude Code on behalf of Claus Ibsen (davsclaus)_
> camel-jms / camel-sjms - a body that maps to no JMS message type is sent as
> an empty message instead of failing
> ---------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-26505
> URL: https://issues.apache.org/jira/browse/CAMEL-26505
> Project: Camel
> Issue Type: Bug
> Components: camel-jms, camel-sjms
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 4.24.0
>
>
> Follow-up of CAMEL-26152 (PR #28925).
> When the body cannot be mapped to a JMS message type (for example a POJO that
> is not Serializable), JmsBinding in camel-jms and in camel-sjms sends a
> generic, empty jakarta.jms.Message and only logs a WARN ("Cannot determine
> specific JmsMessage type to use from body class. Will use generic JmsMessage.
> ..."). The exchange succeeds, so the payload is lost without an error.
> Fail the exchange instead, in both components, with an exception that keeps
> the hint of the WARN (implement java.io.Serializable, or set the
> jmsMessageType option, or marshal the body). Upgrade guide entry, as this
> changes what happens today.
> _Claude Code on behalf of Claus Ibsen (davsclaus)_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
