[
https://issues.apache.org/jira/browse/GERONIMO-6557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15659738#comment-15659738
]
Benjamin Graf commented on GERONIMO-6557:
-----------------------------------------
Well, that 's right. Actually I have the same Problem from the other side. Some
libraries needs JMS 1.1 API and some some need 2.0 and some are linking without
explicit version or broad version [1,1;3] causing problems. (e.g. ActiveMQ, or
Camel). With 2.0 also exporting 1.1 it might be possible to replace both
versions with only one. If the various features that reference the jms api with
the dependency="true" flag will use the new bundle instead the runtime problem
you describe should be gone.
> 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)
