[CAMEL-9394] Automate "org.apache.activemq.SERIALIZABLE_PACKAGES" setup for camel-activemq

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.17.0
• Component/s: camel-activemq, camel-jms
• Estimated Complexity: Unknown
• Assignee: Unassigned
• Reporter: Brett E. Meyer
• Created: 04/Dec/15 17:53
• Updated: 16/Feb/16 08:13
• Resolved: 16/Feb/16 08:13

Description

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...