[jboss-dev] Dependencies to JBoss as core libs

[Adrian]

Integration code does not need to be shared.

Integration should be written in the 
JBossAS codebase (integration project) not in 
JBoss Messaging (implementation project).

http://jira.jboss.com/jira/browse/JBAS-1796

I closed JBAS-4499 since even if we were going to make
this a "public spi" we would want to change it anyway
to not necessarily be dependent on jndi for JMS integration.

On Fri, 2007-06-22 at 16:15 -0500, Clebert Suconic wrote:
> http://jira.jboss.com/jira/browse/JBAS-4499
> 
> Scott M Stark wrote:
> > Yes, this should be in an spi jar, and should not be referencing the
> > Service/ServiceMBean interfaces.
> > 
> > Clebert Suconic wrote:
> >> It has to be a better way to do this...
> >>
> >> The only reason JBossMessaging is dependent on jboss.jar is because
> >> org.jboss.jms.jndi.JMSProviderAdapter is only available there. (Did a
> >> search on all the other jars on JBoss 4.2)
> >>
> >> Shouldn't these Adapters be available in some sort of
> >> jboss-integration.jar or jboss-adapters.jar?
> >>
> >> I would have to add jboss.jar to core-libs just because of this class.
> >>
> >>
> > 
> > _______________________________________________
> > jboss-development mailing list
> > jboss-development at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/jboss-development
> 
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
-- 
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx