You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@geronimo.apache.org by "Romain Manni-Bucau (JIRA)" <ji...@apache.org> on 2016/11/12 13:27:58 UTC

[jira] [Commented] (GERONIMO-6557) Enhance JMS 2.0 API jar

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

Romain Manni-Bucau commented on GERONIMO-6557:
----------------------------------------------

If we do and it links this way a runtime can fail when supporting multiple versions of jms api - common in libraries. Not sure it is as good as it can seem. Wdyt?

> Enhance JMS 2.0 API jar
> -----------------------
>
>                 Key: GERONIMO-6557
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-6557
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>            Reporter: Benjamin Graf
>
> The actual implementation exports javax.jms package as version 2.0.
> Many OSGi dependencies only import javax.jms without explicit version causing problems while mixing messaging systems. (e.g. ActiveMQ vs. WMQ) The actual API is 100% backward compatible therefor it should be consider exporting it either under version 1.1 to have only one JMS API jar under OSGi environments.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)