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.
Clebert
Clebert Suconic wrote:
Currently JBoss messaging has some dependencies to JBoss AS,
specially
jbossxs, commons, j2ee and jboss.jar
Looking at
http://repository.jboss.com/jbossas/core-libs/4.2.0.GA/, I
only see these libraries:
jboss-common.jar
jboss-j2ee.jar
jboss-jmx.jar
jboss-system.jar
jboss-xml-binding.jar
I don't see jboss.jar, jbosssx.jar and jnp-client.jar.
I'm still not sure If I need jnp-client but jboss.jar and jbosssx.jar I
do need to compile security stuff and transaction integrations.
Anyone sees any problem if I add these libraries into that repository...
or anyone know if there is another place I should be looking at on the
repository?
Anyway, I don't think anyone is using that as the component-info.xml was
completely broken, making references to inexistent components.
Clebert
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development