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

Posted to dev@activemq.apache.org by "Bernardo Gomez Palacio (JIRA)" <ji...@apache.org> on 2011/01/18 19:26:45 UTC

[jira] Created: (AMQ-3144) Even activemq-all shouldn't include the javax.jms.* specification classes.

Even activemq-all shouldn't include the javax.jms.* specification classes.
--------------------------------------------------------------------------

                 Key: AMQ-3144
                 URL: https://issues.apache.org/jira/browse/AMQ-3144
             Project: ActiveMQ
          Issue Type: Improvement
    Affects Versions: 5.2.0
            Reporter: Bernardo Gomez Palacio


Even activemq-all shouldn't include the javax.jms.* specification classes. This might cause confusion and class-loading issues with for example Tomcat and log4j when the server already provides a JMS jar ((javax.jms:jms:1.1)  and an application is deployed with activemq-all-5.2.0+. In a nutshell, and as it happens with the servlet, jsp, and xml specs, we shouldn't include them directly.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] [Closed] (AMQ-3144) Even activemq-all shouldn't include the javax.jms.* specification classes.

Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.

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

Timothy Bish closed AMQ-3144.
-----------------------------

    Resolution: Won't Fix

> Even activemq-all shouldn't include the javax.jms.* specification classes.
> --------------------------------------------------------------------------
>
>                 Key: AMQ-3144
>                 URL: https://issues.apache.org/jira/browse/AMQ-3144
>             Project: ActiveMQ
>          Issue Type: Improvement
>    Affects Versions: 5.2.0
>            Reporter: Bernardo Gomez Palacio
>
> Even activemq-all shouldn't include the javax.jms.* specification classes. This might cause confusion and class-loading issues with for example Tomcat and log4j when the server already provides a JMS jar ((javax.jms:jms:1.1)  and an application is deployed with activemq-all-5.2.0+. In a nutshell, and as it happens with the servlet, jsp, and xml specs, we shouldn't include them directly.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira