[
https://issues.apache.org/jira/browse/OPENJPA-2762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16725585#comment-16725585
]
Matt Pavlovich commented on OPENJPA-2762:
-----------------------------------------
In what way does openjpa forbid using JMS v2.0 API or would this cause a leaky
API? The JMS v2.0 API allows for all v1.1 classes and methods to work as-is.
OpenJPA choosing to stay w/ the v1.1 classes and method signatures ensures that
it will continue to work with v1.1 brokers, but does not preclude it from
working with JMS v2.0 brokers.
> 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)
