[
https://issues.apache.org/jira/browse/OPENJPA-2762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16726023#comment-16726023
]
Matt Pavlovich edited comment on OPENJPA-2762 at 12/20/18 4:48 PM:
-------------------------------------------------------------------
[~romain.manni-bucau] I am having a hard time understanding the rationale (not
trying to be difficult!) of sticking with v1.1.
camel-jms is using the JMS v2.0 spec, but the code is all JMS v1.1 classes,
interfaces and methods.
[Camel JMS
dependency|https://github.com/apache/camel/blob/master/components/camel-jms/pom.xml#L70]
My read of the Java EE compatibility requirements does not support this
statement: "Using 2 does not guarantee 1 will work but using 1 ensures 2 will
work"
[Java EE Compatibility
Requirements|https://javaee.github.io/javaee-spec/CompatibilityRequirements]
was (Author: mattrpav):
Romain: I am having a hard time understanding the rationale (not trying to be
difficult!) of sticking with v1.1.
camel-jms is using the JMS v2.0 spec, but the code is all JMS v1.1 classes,
interfaces and methods.
[Camel JMS
dependency|https://github.com/apache/camel/blob/master/components/camel-jms/pom.xml#L70]
My read of the Java EE compatibility requirements does not support this
statement: "Using 2 does not guarantee 1 will work but using 1 ensures 2 will
work"
[Java EE Compatibility
Requirements|https://javaee.github.io/javaee-spec/CompatibilityRequirements]
> 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: 0.5h
> Remaining Estimate: 0h
>
> JMS 2.0 is backwards compatible with JMS v1.1
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
