[GitHub] [activemq] tabish121 commented on pull request #682: [AMQ-7309] Update to jakarta.jms/jakarta.jms-api:2.0.3

[GitBox <gi...@apache.org>]

tabish121 commented on pull request #682:
URL: https://github.com/apache/activemq/pull/682#issuecomment-892970530


   > It’s not about qpid its that you’re breaking cross protocol stuff. Qpid is just showing those breaks up. The fact the activemq test didn’t pick up, is just a miss but thankfully the qpid projects tests did. I think it ties back to trying to fudge in jms 2.0 client side without proper changes broker side, e.g. maybe this could be sorted by adding the correct jms 2.0 mapping to AMQP broker side to sort correct protocol support. 
   
   For clarity this has nothing to do with broker side AMQP support, the issue seen from Qpid bridging tests simply exposes an issue with the proposed Openwire client changes which don't represent a complete implementation of the JMS 2.0 specification.  It's quite likely that other libraries such as PooledJMS would similarly encounter unexpected situations as it also uses a similar mechanism as the Qpid client does to detect JMS 1.1 clients operating with JMS 2.0 API jars on the classpath.   
   
   


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

To unsubscribe, e-mail: gitbox-unsubscribe@activemq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org