[GitHub] [activemq-nms-amqp] michaelandrepearce edited a comment on issue #31: AMQNET-612: ObjectMessage shouldn't have jms-msg-type set

michaelandrepearce edited a comment on issue #31: AMQNET-612: ObjectMessage shouldn't have jms-msg-type set URL: https://github.com/apache/activemq-nms-amqp/pull/31#issuecomment-531005790 right, so what we can do then, is first check content type, (before any of the switching) if co

[GitHub] [activemq-nms-amqp] michaelandrepearce edited a comment on issue #31: AMQNET-612: ObjectMessage shouldn't have jms-msg-type set

michaelandrepearce edited a comment on issue #31: AMQNET-612: ObjectMessage shouldn't have jms-msg-type set URL: https://github.com/apache/activemq-nms-amqp/pull/31#issuecomment-530970373 Well you can invert the logic, you return object only if also the .net content type. Thus then you are

[GitHub] [activemq-nms-amqp] michaelandrepearce edited a comment on issue #31: AMQNET-612: ObjectMessage shouldn't have jms-msg-type set

michaelandrepearce edited a comment on issue #31: AMQNET-612: ObjectMessage shouldn't have jms-msg-type set URL: https://github.com/apache/activemq-nms-amqp/pull/31#issuecomment-530969794 x-opt-jms-msg-type should be honoured, his suggestion was when msg type =obj then also key on the cont