[jboss-jira] [JBoss JIRA] Closed: (JBAS-4499) Distribute org.jboss.jms.jndi.JMSProviderAdapter in a separate jar for Integration

[Adrian Brock (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBAS-4499?page=all ]

Adrian Brock closed JBAS-4499.
------------------------------

    Resolution: Deferred

I'm deferring this issue. 

I don't care what policy you use for JBoss Messaging, but
for the Appserver you need to raise a discussion thread in the forums
where we can decide what JIRA issues need raising, NOT the way you have done it
which is the wrong way around.

1) The JMSProvider is an integration api of the appserver.
It is not intended to be used by other projects.
It is simply wrong to do integration work inside external projects
all integration work should be in the JBossAS codebase.

2) This api is wrong anyway. If we are going to push a shared jms provider api into core libs
then we need to rework it as plain factory for connection factories
and destinations (which could be implemented using jndi).

> Distribute org.jboss.jms.jndi.JMSProviderAdapter in a separate jar for Integration
> ----------------------------------------------------------------------------------
>
>                 Key: JBAS-4499
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4499
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Clebert Suconic
>         Assigned To: Dimitris Andreadis
>
> This should be in a separate JAR for easier integration with other projects (such as JBoss Messaging).
> Once this is created, we should add it to core libs on the repository at http://repository.jboss.com/jbossas/core-libs/

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira