[
https://issues.apache.org/jira/browse/CAMEL-9394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-9394.
--------------------------------
Resolution: Fixed
This is activemq-camel component in AMQ project. The 5.13.2 release will have a
option to allow all packages easily.
> Automate "org.apache.activemq.SERIALIZABLE_PACKAGES" setup for camel-activemq
> -----------------------------------------------------------------------------
>
> Key: CAMEL-9394
> URL: https://issues.apache.org/jira/browse/CAMEL-9394
> Project: Camel
> Issue Type: Improvement
> Components: camel-activemq, camel-jms
> Reporter: Brett E. Meyer
> Fix For: 2.17.0
>
>
> For ActiveMQ object message (de)serialization, AMQ-6013 tightly restricts
> accepted classes to a small set of absolutely necessary packages. Although
> I'm not clear on why that change was necessary, it's easily overcome by
> setting the "org.apache.activemq.SERIALIZABLE_PACKAGES" system property.
> We recently hit the Exception ActiveMQ throws if this isn't set, when you use
> your own object as a message body. I'm guessing other camel-activemq users
> will be caught offguard by the change as well.
> Suggestion: during runtime, camel-activemq chould set/update that system
> property, as object messages are sent.
> Alternatively, as a bare minimum, we should document this on the
> camel-activemq wiki...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
