[jira] [Updated] (ARTEMIS-2557) Document potential JMS spec dependency issue for embedded use-cases

["Justin Bertram (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARTEMIS-2557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Bertram updated ARTEMIS-2557:
------------------------------------
    Summary: Document potential JMS spec dependency issue for embedded use-cases  (was: JMS spec dependencies)

> Document potential JMS spec dependency issue for embedded use-cases
> -------------------------------------------------------------------
>
>                 Key: ARTEMIS-2557
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2557
>             Project: ActiveMQ Artemis
>          Issue Type: Task
>          Components: Broker, OpenWire
>    Affects Versions: 2.10.1
>            Reporter: SL
>            Assignee: Justin Bertram
>            Priority: Minor
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> artemis-openwire-protocol has a dependency on geronimo-jms-1.1_spec
> {code:xml}
>        <dependency>
>          <groupId>org.apache.geronimo.specs</groupId>
>          <artifactId>geronimo-jms_1.1_spec</artifactId>
>          <version>1.1.1</version>
>       </dependency>
> {code}
> However other components such as artemis-jms-server have a dependency on geronimo-jms_2.0_spec which carry a superset of the same interfaces, but with subtle differences (such as the JMSContext in ConnectionFactory)
> If your have both components in a dependency hierarchy you may end up with a classpath including both jar which can lead to a behavior that is
> a) inconsistent, since one or the other jar may have been loaded first to resolve a given interface
> b) funny, if a component compiled against an interface from 2.0 try to use one from 1.1.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)