[infinispan-dev] Fwd: [Infinispan] - Re: Infinispan 5.0.0 on JBoss AS 6.0.0

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

[infinispan-dev] Fwd: [Infinispan] - Re: Infinispan 5.0.0 on JBoss AS 6.0.0

Galder Zamarreno

Any idea about this? It would appear as if even if Infinispan 5.0 is deployed in isolated mode, the JAXB layer might have issues with previously loaded XSD?


Begin forwarded message:

From: Bertrand Renuart <[hidden email]>
Date: February 18, 2011 5:31:17 PM GMT+01:00
To: Galder ZamarreƱo <[hidden email]>
Subject: [Infinispan] - Re: Infinispan 5.0.0 on JBoss AS 6.0.0

JBoss Community

Re: Infinispan 5.0.0 on JBoss AS 6.0.0

created by Bertrand Renuart in Infinispan - View the full discussion

Adding META-INF/jboss-classloading.xml as you propose does the trick - jars contained in my ear are loaded intstead of those provided by JBoss AS.


BUT... Infinispan still fails to initialize with the following error:

javax.xml.bind.UnmarshalException: unexpected element (uri:urn:infinispan:config:5.0, local:infinispan). Expected elements are <{urn:infinispan:config:4.2}infinispan>

For your information, this happens only when starting JBoss with the "all" configuration - it does work correctly with the "default" configuration.

My understanding is as follows:

  1. The "all" configuration contains Clustering support which makes use of Infinispan (version 4.2.0). The Clustering features are initialized before any application is deployed;
  2. Infinispan relies on JAXB to read/parse its configuration - the InfinispanConfiguration class is unmarshalled using JAXB.
  3. Then comes the initialization of Infinispan within my application - version 5.x and not 4.2.0. For whatever reason, this time JAXB fails to unmarshal it correctly.

The second time JAXB complains with an expected urn of the form :config:4.2 - this looks like a left over from the first unmarshalling (done when JBoss initialized its clustering support). This would also explains why everything works perfectly when deploying under the "default" profile which doesn't contain clustering support...


Do you have any idea on how to solve this issue ?

Is there a way to tell JAXB to "flush" anything it may have collected about the previous unmarshalling ?

Reply to this message by going to Community
Start a new discussion in Infinispan at Community

Galder ZamarreƱo
Sr. Software Engineer
Infinispan, JBoss Cache

infinispan-dev mailing list
[hidden email]