ansaurus

Question

Answer 1

A:

My guess is that Spring is being loaded by two different classloaders. If this is the case, then the webapp's classloader cannot cast the parent context to BeanFactory.

Your WAR is packaged inside your EAR, is that correct? If so, do you have a single copy of Spring inside the EAR, or do you have additional Spring JARs inside the WAR?

skaffman 2009-07-01 15:25:30

i've one copy of spring 2.5.6 in the 'lib' folder of EAR, and my war contains no jars. The jboss server folder has an older version of spring, but i'm sure my config is using the version in the EAR lib folder.In my ear-deployer.xml i'm currently using this isolation level<attribute name="Isolated">true</attribute> but the exception disappears when i set this field 'false'.

emeraldjava 2009-07-01 16:36:21

Ah, the joys of JBoss classloaders. By disabling Isolation, you're telling JBoss to flatten everything out and classloading issues can disappear. It's not recommended, though, since your applications will start fighting each other, rather than fighting the container.

skaffman 2009-07-01 16:43:19

What happens if you remove the old version of Spring from the server lib dir, and leave isolation on?

skaffman 2009-07-01 16:44:01

Answer 2

A:

I would classify this as a problem with the spring configuration, not with JBoss' class loading. Could you describe what your intention is with this set of configurations?

Do you only need to load multiple application contexts, or is there a need to have the application contexts loaded this way?

You can try to just load a single application context and import all other application contexts in that configuration, or configure all contexts via web.xml and have them loaded by the spring context loader listener.

single application context: the context ${servlet-name}-servlet.xml is automatically loaded. You can insert <import/> directives into this configuration file as described in Composing XML-based configuration metadata
configuration via web.xml: configure the contextConfigLocation context parameter of the web application as described in Common configuration.

If you have any special requirements why you chose to configure your application this way, please give more details. The recommended approach is to either configure all contexts externally (in this case via web.xml context parameter), or have the contexts import other contexts via <import/>.

I hope this could help,
Kariem

Kariem 2009-07-06 07:19:13

ansaurus

tags:

views:

answers:

Parent Contexts in spring based web-app

related questions