You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Luciano <l....@almavivaitalia.it> on 2007/02/07 21:48:01 UTC
JCA adapter and Spring 2 application conflict in JBoss
If I try to deploy the ActiveMQ JCA resource adapter
(activemq-rar-4.1.0-incubator.rar) side by side with a Spring 2 war in JBoss
4.0.3 , I get the following error on server startup:
ERROR
[org.springframework.web.context.ContextLoader] Context initialization
failed
org.springframework.beans.factory.BeanDefinitionStoreException:
Unexpected exception parsing XML document from ServletContext resource
[/WEB-INF/applicationContext.xml]; nested exception is
java.lang.IllegalArgumentException: Class
[org.apache.xbean.spring.context.v2.XBeanNamespaceHandler] does not
implement the NamespaceHandler interface
Caused by:
java.lang.IllegalArgumentException: Class
[org.apache.xbean.spring.context.v2.XBeanNamespaceHandler] does not
implement the NamespaceHandler interface
at
org.springframework.beans.factory.xml.DefaultNamespaceHandlerResolver.initHandle\
rMappings(DefaultNamespaceHandlerResolver.java:119)
at
org.springframework.beans.factory.xml.DefaultNamespaceHandlerResolver.<init>(Def\
aultNamespaceHandlerResolver.java:96)
at
org.springframework.beans.factory.xml.DefaultNamespaceHandlerResolver.<init>(Def\
aultNamespaceHandlerResolver.java:82)
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.createDefaultNames\
paceHandlerResolver(XmlBeanDefinitionReader.java:526)
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.createReaderContex\
t(XmlBeanDefinitionReader.java:515)
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefini\
tions(XmlBeanDefinitionReader.java:495)
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefiniti\
ons(XmlBeanDefinitionReader.java:390)
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinition\
s(XmlBeanDefinitionReader.java:340)
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinition\
s(XmlBeanDefinitionReader.java:317)
at
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanD\
efinitions(AbstractBeanDefinitionReader.java:125)
at
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanD\
efinitions(AbstractBeanDefinitionReader.java:141)
at
org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinit\
ions(XmlWebApplicationContext.java:123)
at
org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinit\
ions(XmlWebApplicationContext.java:91)
at
org.springframework.context.support.AbstractRefreshableApplicationContext.refres\
hBeanFactory(AbstractRefreshableApplicationContext.java:94)
at
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractA\
pplicationContext.java:292)
at
org.springframework.web.context.support.AbstractRefreshableWebApplicationContext\
.refresh(AbstractRefreshableWebApplicationContext.java:156)
at
org.springframework.web.context.ContextLoader.createWebApplicationContext(Contex\
tLoader.java:246)
at
org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextL\
oader.java:184)
at
org.springframework.web.context.ContextLoaderListener.contextInitialized(Context\
LoaderListener.java:49)
The only workaround I found is to remove the Spring jar from the ActiveMQ
rar.
I didn't find any error similar to this searching on this mailing list, so i
suppose it could be a problem
of my configuration, but I can' find what is wrong.
Any idea?
Thanks
Luciano
--
View this message in context: http://www.nabble.com/JCA-adapter-and-Spring-2-application-conflict-in-JBoss-tf3189496s2354.html#a8853863
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: JCA adapter and Spring 2 application conflict in JBoss
Posted by Luciano <l....@almavivaitalia.it>.
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.
Re: JCA adapter and Spring 2 application conflict in JBoss
Posted by Luciano <l....@almavivaitalia.it>.
James.Strachan wrote:
>
> You could always make your own custom RAR.
>
> But really there is meant to be a way of isolating RAR, WAR, EAR class
> loaders to avoid exactly these kinds of problems. It might be worth
> asking on the JBoss forums on how to solve this problem generally as
> I'm sure folks will hit similar issues with RARs and WARs
>
> --
> James
> -------
> http://radio.weblogs.com/0112098/
>
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#a8893096
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: JCA adapter and Spring 2 application conflict in JBoss
Posted by James Strachan <ja...@gmail.com>.
On 2/8/07, Luciano <l....@almavivaitalia.it> wrote:
>
> It tried to insulate my war using something like this
>
> <jboss-web>
> <class-loading java2ClassLoadingCompliance="false">
> <loader-repository>
> com.example:loader=myap.war
>
> <loader-repository-config>java2ParentDelegation=false</loader-repository-config>
> </loader-repository>
> </class-loading>
> ....
> but without success. It seems that JBoss can insulate ear, war and sar but
> i didn't find any way of insulating the rar
> http://wiki.jboss.org/wiki/Wiki.jsp?page=ClassLoadingConfiguration
> http://wiki.jboss.org/wiki/Wiki.jsp?page=ClassLoadingConfiguration .
>
> The workaround of deleting spring-2.0. jar in the rar, which kind of problem
> can generate?
You could always make your own custom RAR.
But really there is meant to be a way of isolating RAR, WAR, EAR class
loaders to avoid exactly these kinds of problems. It might be worth
asking on the JBoss forums on how to solve this problem generally as
I'm sure folks will hit similar issues with RARs and WARs
--
James
-------
http://radio.weblogs.com/0112098/
Re: JCA adapter and Spring 2 application conflict in JBoss
Posted by Luciano <l....@almavivaitalia.it>.
It tried to insulate my war using something like this
<jboss-web>
<class-loading java2ClassLoadingCompliance="false">
<loader-repository>
com.example:loader=myap.war
<loader-repository-config>java2ParentDelegation=false</loader-repository-config>
</loader-repository>
</class-loading>
....
but without success. It seems that JBoss can insulate ear, war and sar but
i didn't find any way of insulating the rar
http://wiki.jboss.org/wiki/Wiki.jsp?page=ClassLoadingConfiguration
http://wiki.jboss.org/wiki/Wiki.jsp?page=ClassLoadingConfiguration .
The workaround of deleting spring-2.0. jar in the rar, which kind of problem
can generate?
Luciano
James.Strachan wrote:
>
> So its sounding like some kinda wacky classloader issue. Any chance
> you could deploy the RAR ina different classloader from your WAR?
>
> On 2/8/07, Luciano <l....@almavivaitalia.it> wrote:
>>
>> I don't use xbean-spring in my application, but however I reproduced the
>> error with an application example of the Spring 2.0.2 distribution the
>> jpetstore.
>> To try yourself these are the steps:
>> 1)Install a fresh Jboss (I tested 4.0.3 and 4.0.5) and verify it starts
>> without problems
>> 2)Stop JBoss
>> 3)Put the activemq-rar-4.1.0-incubator.rar and jpetstore.war in the
>> deploy
>> JBoss dir
>> 4)Start JBoss and you will see my stack trace
>>
>> Note that if you install only the jpetstore.war and deploy
>> activemq-rar-4.1.0-incubator.rar while
>> JBoss is running, you don't have any error, but restarting JBoss it will
>> show again.
>> It seems a classloader problem, even because if I delete the spring-2.0
>> jar
>> inside the rar, JBoss start fine, but where open a bug?. What problems I
>> could encounter with this last rar modification?
>>
>> Luciano
>>
>>
>> James.Strachan wrote:
>> >
>> > On 2/8/07, Luciano <l....@almavivaitalia.it> wrote:
>> >>
>> >> If you are referring to the ActiveMQ JCA rar, as I stated in my
>> original
>> >> post, I already use 4.1.0 version. The 4.0.3 I talked about is the
>> Jboss
>> >> version (and the last JBoss is 4.0.5).
>> >
>> > Sorry - I misread your mail :)
>> >
>> > So the stack trace you provide doesn't seem to be related to the RAR
>> > at all - it seems the error is being thrown when a WAR starts up
>> > parsing /WEB-INF/applicationContext.xml. Could you show us what it
>> > looks like? Are you using some ActiveMQ XML in there? If so what
>> > verison of xbean-spring are you using?
>> >
>> > --
>> >
>> > James
>> > -------
>> > http://radio.weblogs.com/0112098/
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/JCA-adapter-and-Spring-2-application-conflict-in-JBoss-tf3189496s2354.html#a8863428
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>>
>
>
> --
>
> James
> -------
> http://radio.weblogs.com/0112098/
>
>
--
View this message in context: http://www.nabble.com/JCA-adapter-and-Spring-2-application-conflict-in-JBoss-tf3189496s2354.html#a8867525
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: JCA adapter and Spring 2 application conflict in JBoss
Posted by James Strachan <ja...@gmail.com>.
So its sounding like some kinda wacky classloader issue. Any chance
you could deploy the RAR ina different classloader from your WAR?
On 2/8/07, Luciano <l....@almavivaitalia.it> wrote:
>
> I don't use xbean-spring in my application, but however I reproduced the
> error with an application example of the Spring 2.0.2 distribution the
> jpetstore.
> To try yourself these are the steps:
> 1)Install a fresh Jboss (I tested 4.0.3 and 4.0.5) and verify it starts
> without problems
> 2)Stop JBoss
> 3)Put the activemq-rar-4.1.0-incubator.rar and jpetstore.war in the deploy
> JBoss dir
> 4)Start JBoss and you will see my stack trace
>
> Note that if you install only the jpetstore.war and deploy
> activemq-rar-4.1.0-incubator.rar while
> JBoss is running, you don't have any error, but restarting JBoss it will
> show again.
> It seems a classloader problem, even because if I delete the spring-2.0 jar
> inside the rar, JBoss start fine, but where open a bug?. What problems I
> could encounter with this last rar modification?
>
> Luciano
>
>
> James.Strachan wrote:
> >
> > On 2/8/07, Luciano <l....@almavivaitalia.it> wrote:
> >>
> >> If you are referring to the ActiveMQ JCA rar, as I stated in my original
> >> post, I already use 4.1.0 version. The 4.0.3 I talked about is the Jboss
> >> version (and the last JBoss is 4.0.5).
> >
> > Sorry - I misread your mail :)
> >
> > So the stack trace you provide doesn't seem to be related to the RAR
> > at all - it seems the error is being thrown when a WAR starts up
> > parsing /WEB-INF/applicationContext.xml. Could you show us what it
> > looks like? Are you using some ActiveMQ XML in there? If so what
> > verison of xbean-spring are you using?
> >
> > --
> >
> > James
> > -------
> > http://radio.weblogs.com/0112098/
> >
> >
>
> --
> View this message in context: http://www.nabble.com/JCA-adapter-and-Spring-2-application-conflict-in-JBoss-tf3189496s2354.html#a8863428
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>
--
James
-------
http://radio.weblogs.com/0112098/
Re: JCA adapter and Spring 2 application conflict in JBoss
Posted by Luciano <l....@almavivaitalia.it>.
I don't use xbean-spring in my application, but however I reproduced the
error with an application example of the Spring 2.0.2 distribution the
jpetstore.
To try yourself these are the steps:
1)Install a fresh Jboss (I tested 4.0.3 and 4.0.5) and verify it starts
without problems
2)Stop JBoss
3)Put the activemq-rar-4.1.0-incubator.rar and jpetstore.war in the deploy
JBoss dir
4)Start JBoss and you will see my stack trace
Note that if you install only the jpetstore.war and deploy
activemq-rar-4.1.0-incubator.rar while
JBoss is running, you don't have any error, but restarting JBoss it will
show again.
It seems a classloader problem, even because if I delete the spring-2.0 jar
inside the rar, JBoss start fine, but where open a bug?. What problems I
could encounter with this last rar modification?
Luciano
James.Strachan wrote:
>
> On 2/8/07, Luciano <l....@almavivaitalia.it> wrote:
>>
>> If you are referring to the ActiveMQ JCA rar, as I stated in my original
>> post, I already use 4.1.0 version. The 4.0.3 I talked about is the Jboss
>> version (and the last JBoss is 4.0.5).
>
> Sorry - I misread your mail :)
>
> So the stack trace you provide doesn't seem to be related to the RAR
> at all - it seems the error is being thrown when a WAR starts up
> parsing /WEB-INF/applicationContext.xml. Could you show us what it
> looks like? Are you using some ActiveMQ XML in there? If so what
> verison of xbean-spring are you using?
>
> --
>
> James
> -------
> http://radio.weblogs.com/0112098/
>
>
--
View this message in context: http://www.nabble.com/JCA-adapter-and-Spring-2-application-conflict-in-JBoss-tf3189496s2354.html#a8863428
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: JCA adapter and Spring 2 application conflict in JBoss
Posted by James Strachan <ja...@gmail.com>.
On 2/8/07, Luciano <l....@almavivaitalia.it> wrote:
>
> If you are referring to the ActiveMQ JCA rar, as I stated in my original
> post, I already use 4.1.0 version. The 4.0.3 I talked about is the Jboss
> version (and the last JBoss is 4.0.5).
Sorry - I misread your mail :)
So the stack trace you provide doesn't seem to be related to the RAR
at all - it seems the error is being thrown when a WAR starts up
parsing /WEB-INF/applicationContext.xml. Could you show us what it
looks like? Are you using some ActiveMQ XML in there? If so what
verison of xbean-spring are you using?
--
James
-------
http://radio.weblogs.com/0112098/
Re: JCA adapter and Spring 2 application conflict in JBoss
Posted by Luciano <l....@almavivaitalia.it>.
If you are referring to the ActiveMQ JCA rar, as I stated in my original
post, I already use 4.1.0 version. The 4.0.3 I talked about is the Jboss
version (and the last JBoss is 4.0.5).
Any further idea?
Thanks
Luciano
James.Strachan wrote:
>
> IIRC 4.0.3 does not support Spring 2 namespaces. Try 4.1.0
>
> On 2/7/07, Luciano <l....@almavivaitalia.it> wrote:
>>
>> If I try to deploy the ActiveMQ JCA resource adapter
>> (activemq-rar-4.1.0-incubator.rar) side by side with a Spring 2 war in
>> JBoss
>> 4.0.3 , I get the following error on server startup:
>>
>> ERROR
>> [org.springframework.web.context.ContextLoader] Context initialization
>> failed
>> org.springframework.beans.factory.BeanDefinitionStoreException:
>> Unexpected exception parsing XML document from ServletContext resource
>> [/WEB-INF/applicationContext.xml]; nested exception is
>> java.lang.IllegalArgumentException: Class
>> [org.apache.xbean.spring.context.v2.XBeanNamespaceHandler] does not
>> implement the NamespaceHandler interface
>> Caused by:
>> java.lang.IllegalArgumentException: Class
>> [org.apache.xbean.spring.context.v2.XBeanNamespaceHandler] does not
>> implement the NamespaceHandler interface
>> at
>> org.springframework.beans.factory.xml.DefaultNamespaceHandlerResolver.initHandle\
>> rMappings(DefaultNamespaceHandlerResolver.java:119)
>> at
>> org.springframework.beans.factory.xml.DefaultNamespaceHandlerResolver.<init>(Def\
>> aultNamespaceHandlerResolver.java:96)
>> at
>> org.springframework.beans.factory.xml.DefaultNamespaceHandlerResolver.<init>(Def\
>> aultNamespaceHandlerResolver.java:82)
>> at
>> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.createDefaultNames\
>> paceHandlerResolver(XmlBeanDefinitionReader.java:526)
>> at
>> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.createReaderContex\
>> t(XmlBeanDefinitionReader.java:515)
>> at
>> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefini\
>> tions(XmlBeanDefinitionReader.java:495)
>> at
>> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefiniti\
>> ons(XmlBeanDefinitionReader.java:390)
>> at
>> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinition\
>> s(XmlBeanDefinitionReader.java:340)
>> at
>> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinition\
>> s(XmlBeanDefinitionReader.java:317)
>> at
>> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanD\
>> efinitions(AbstractBeanDefinitionReader.java:125)
>> at
>> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanD\
>> efinitions(AbstractBeanDefinitionReader.java:141)
>> at
>> org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinit\
>> ions(XmlWebApplicationContext.java:123)
>> at
>> org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinit\
>> ions(XmlWebApplicationContext.java:91)
>> at
>> org.springframework.context.support.AbstractRefreshableApplicationContext.refres\
>> hBeanFactory(AbstractRefreshableApplicationContext.java:94)
>> at
>> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractA\
>> pplicationContext.java:292)
>> at
>> org.springframework.web.context.support.AbstractRefreshableWebApplicationContext\
>> .refresh(AbstractRefreshableWebApplicationContext.java:156)
>> at
>> org.springframework.web.context.ContextLoader.createWebApplicationContext(Contex\
>> tLoader.java:246)
>> at
>> org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextL\
>> oader.java:184)
>> at
>> org.springframework.web.context.ContextLoaderListener.contextInitialized(Context\
>> LoaderListener.java:49)
>>
>> The only workaround I found is to remove the Spring jar from the ActiveMQ
>> rar.
>> I didn't find any error similar to this searching on this mailing list,
>> so i
>> suppose it could be a problem
>> of my configuration, but I can' find what is wrong.
>> Any idea?
>>
>> Thanks
>>
>> Luciano
>> --
>> View this message in context:
>> http://www.nabble.com/JCA-adapter-and-Spring-2-application-conflict-in-JBoss-tf3189496s2354.html#a8853863
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>>
>
>
> --
>
> James
> -------
> http://radio.weblogs.com/0112098/
>
>
--
View this message in context: http://www.nabble.com/JCA-adapter-and-Spring-2-application-conflict-in-JBoss-tf3189496s2354.html#a8862151
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: JCA adapter and Spring 2 application conflict in JBoss
Posted by James Strachan <ja...@gmail.com>.
IIRC 4.0.3 does not support Spring 2 namespaces. Try 4.1.0
On 2/7/07, Luciano <l....@almavivaitalia.it> wrote:
>
> If I try to deploy the ActiveMQ JCA resource adapter
> (activemq-rar-4.1.0-incubator.rar) side by side with a Spring 2 war in JBoss
> 4.0.3 , I get the following error on server startup:
>
> ERROR
> [org.springframework.web.context.ContextLoader] Context initialization
> failed
> org.springframework.beans.factory.BeanDefinitionStoreException:
> Unexpected exception parsing XML document from ServletContext resource
> [/WEB-INF/applicationContext.xml]; nested exception is
> java.lang.IllegalArgumentException: Class
> [org.apache.xbean.spring.context.v2.XBeanNamespaceHandler] does not
> implement the NamespaceHandler interface
> Caused by:
> java.lang.IllegalArgumentException: Class
> [org.apache.xbean.spring.context.v2.XBeanNamespaceHandler] does not
> implement the NamespaceHandler interface
> at
> org.springframework.beans.factory.xml.DefaultNamespaceHandlerResolver.initHandle\
> rMappings(DefaultNamespaceHandlerResolver.java:119)
> at
> org.springframework.beans.factory.xml.DefaultNamespaceHandlerResolver.<init>(Def\
> aultNamespaceHandlerResolver.java:96)
> at
> org.springframework.beans.factory.xml.DefaultNamespaceHandlerResolver.<init>(Def\
> aultNamespaceHandlerResolver.java:82)
> at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.createDefaultNames\
> paceHandlerResolver(XmlBeanDefinitionReader.java:526)
> at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.createReaderContex\
> t(XmlBeanDefinitionReader.java:515)
> at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefini\
> tions(XmlBeanDefinitionReader.java:495)
> at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefiniti\
> ons(XmlBeanDefinitionReader.java:390)
> at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinition\
> s(XmlBeanDefinitionReader.java:340)
> at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinition\
> s(XmlBeanDefinitionReader.java:317)
> at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanD\
> efinitions(AbstractBeanDefinitionReader.java:125)
> at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanD\
> efinitions(AbstractBeanDefinitionReader.java:141)
> at
> org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinit\
> ions(XmlWebApplicationContext.java:123)
> at
> org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinit\
> ions(XmlWebApplicationContext.java:91)
> at
> org.springframework.context.support.AbstractRefreshableApplicationContext.refres\
> hBeanFactory(AbstractRefreshableApplicationContext.java:94)
> at
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractA\
> pplicationContext.java:292)
> at
> org.springframework.web.context.support.AbstractRefreshableWebApplicationContext\
> .refresh(AbstractRefreshableWebApplicationContext.java:156)
> at
> org.springframework.web.context.ContextLoader.createWebApplicationContext(Contex\
> tLoader.java:246)
> at
> org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextL\
> oader.java:184)
> at
> org.springframework.web.context.ContextLoaderListener.contextInitialized(Context\
> LoaderListener.java:49)
>
> The only workaround I found is to remove the Spring jar from the ActiveMQ
> rar.
> I didn't find any error similar to this searching on this mailing list, so i
> suppose it could be a problem
> of my configuration, but I can' find what is wrong.
> Any idea?
>
> Thanks
>
> Luciano
> --
> View this message in context: http://www.nabble.com/JCA-adapter-and-Spring-2-application-conflict-in-JBoss-tf3189496s2354.html#a8853863
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>
--
James
-------
http://radio.weblogs.com/0112098/