gemmellr commented on issue #31: AMQNET-612: ObjectMessage shouldn't have jms-msg-type set URL: https://github.com/apache/activemq-nms-amqp/pull/31#issuecomment-530996473 The new check for serialized dotnet content type should never be true while the annotation is set to reflect a JMS Object Message, it would be an error if it were. That was the starting point of the discussion, that the client originally did that and should not. Neither the NMS client or any other should set the annotation to that value along with a content type which is other than "application/x-java-serialized-object", so you cant positively check for the dotnet serialized case, only that it is "application/x-java-serialized-object" or that there is none set.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
