[ 
https://issues.apache.org/jira/browse/OPENJPA-2762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16725132#comment-16725132
 ] 

Matt Pavlovich edited comment on OPENJPA-2762 at 12/19/18 4:02 PM:
-------------------------------------------------------------------

The transitive dependency on jms v1.1 is dated, and causes headaches when 
working with v2.0 JMS brokers (IBM MQ, TibcoEMS, ActiveMQ Artemis.. etc)

It also better aligns with other framework dependencies out there.. Apache 
Camel.. etc.. all supporting v2.0 specs.

IMHO ActiveMQ 5.x should be considered the JMS spec outlier, not the other way 
around. Also-- this shouldn't cause any headaches with ActiveMQ 5.x.. JMS v2.0 
is backwards compatible and ActiveMQ 5.x clients are able to function with a 
JMS v2.0 spec in the CP.




was (Author: mattrpav):
The transitive dependency on jms v1.1 is dated, and causes headaches when 
working with v2.0 JMS brokers (IBM MQ, TibcoEMS, ActiveMQ Artemis.. etc)

It also better aligns with other framework dependencies out there.. Apache 
Camel.. etc.. all supporting v2.0 specs.

This shouldn't cause any headaches with ActiveMQ 5.x.. JMS v2.0 is backwards 
compatible and ActiveMQ 5.x clients are able to function with a JMS v2.0 spec 
in the CP.



> Upgrade to JMS 2.0. spec
> ------------------------
>
>                 Key: OPENJPA-2762
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-2762
>             Project: OpenJPA
>          Issue Type: Task
>          Components: build / infrastructure
>    Affects Versions: 3.0.0
>            Reporter: Matt Pavlovich
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> JMS 2.0 is backwards compatible with JMS v1.1



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to