[
https://issues.apache.org/jira/browse/ARTEMIS-758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15529626#comment-15529626
]
ASF GitHub Bot commented on ARTEMIS-758:
----------------------------------------
Github user tabish121 commented on the issue:
https://github.com/apache/activemq-artemis/pull/810
A JMS Message sent for OpenWire / Core or wherever should contain a Binary
message body and that value can just be placed directly into a Data value as
the original Binary without need to decode it. As an extra nicety you can
throw in the 'application/x-java-serialized-object' content type value and then
for things like Qpid JMS that understand that you'd get an ObjectMessage out on
the client's consumer and treat the same as any other JMS client getting an
ObjectMessage by calling getObject and hoping you had the right classes on the
Classpath
> List/Object message sent by OpenWire JMS client can't be consumed with other
> clients
> ------------------------------------------------------------------------------------
>
> Key: ARTEMIS-758
> URL: https://issues.apache.org/jira/browse/ARTEMIS-758
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP, Broker
> Affects Versions: 1.4.0
> Reporter: Andy Taylor
> Assignee: Andy Taylor
> Fix For: 1.5.0
>
>
> something gets screwed when the object is deserialised at the broker
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
