No response till now from Jboss forum. But I made some more experiments to
help understand what happens.
As the original error came from
org.springframework.beans.factory.xml.DefaultNamespaceHandlerResolver I set
the whole org.springframework.beans.factory.xml package at the log4j DEBUG
level and discovered that the problems seems related that this class when
loading namespace mappings  will find reference to activemq and
XBeanNamespaceHandler in every Spring application when the activeMQ JCA rar
is deployed in JBoss:
2007-02-11 15:05:56,484 DEBUG
[org.springframework.beans.factory.xml.DefaultNamespaceHandlerResolver]
 Loaded mappings [{

http://www.springframework.org/schema/p=org.springframework.beans.factory.xml.SimplePropertyNamespaceHandler,
 

http://www.springframework.org/schema/lang=org.springframework.scripting.config.LangNamespaceHandler,
 

http://activemq.org/config/1.0=org.apache.xbean.spring.context.v2.XBeanNamespaceHandler,
 

http://www.springframework.org/schema/jee=org.springframework.ejb.config.JeeNamespaceHandler,
 

http://activemq.org/ra/1.0=org.apache.xbean.spring.context.v2.XBeanNamespaceHandler,
 

http://www.springframework.org/schema/aop=org.springframework.aop.config.AopNamespaceHandler,
 

http://www.springframework.org/schema/util=org.springframework.beans.factory.xml.UtilNamespaceHandler,
 

http://www.springframework.org/schema/tx=org.springframework.transaction.config.TxNamespaceHandler
 }]

 So DefaultNamespaceHandlerResolver will try to load the
XBeanNamespaceHandler class generating the original problem. The workaround
of deleting the spring-2.0 jar that I found previously revealed not a good
solution as with DEBUG on revealed to generate this error:

2007-02-11 15:12:42,484 DEBUG
[org.springframework.beans.factory.xml.DefaultNamespaceHandlerResolver]
Ignoring handler [org.apache.xbean.spring.context.v2.XBeanNamespaceHandler]:
class not found
java.lang.ClassNotFoundException:
org.apache.xbean.spring.context.v2.XBeanNamespaceHandler
        at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1332)

Supposing the problem is to load correctly the XBeanNamespaceHandler I tryed
another workaround adding the xbean-spring-2.8.jar to the Spring app an
effectively all run fine and this shoul work even for an embedded broker.
The real solution would be not to have unneeded namespace mappings  visible
in the app, but I don't know how to do it.
Any further idea?

Luciano

Luciano wrote:
> 
> I posted the problem on JBoss forum:
>  http://www.jboss.com/index.html?module=bb&op=viewtopic&t=101156
> http://www.jboss.com/index.html?module=bb&op=viewtopic&t=101156 
> Luciano
> 

-- 
View this message in context: 
http://www.nabble.com/JCA-adapter-and-Spring-2-application-conflict-in-JBoss-tf3189496s2354.html#a8911574
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Reply via email to