ApplicationResource unavailable with multiple contexts in 4.

[bretg80]

HELP! I've tried everything and this just doesn't make any sense.

I have two WAR files in the default deploy of 4.0.1 named as follows:

/Callcenter

/Public

The Callcenter context can find the ApplicationResource bundle just fine in Callcenter/WEB-INF/classes, but the Public context doesn't see it's own version of the ApplicationResource bundle. I think it is looking at Callcenter since Callcenter is loaded first.

Anyone run into this one? Any solutions? Each context should have a separate ApplicationResource bundle? Right?

Any help would be appreciated. I am upgrading from JBOSS 3.0.2 and this works correctly in that environment.


Thanks, Bret

[bretg80]

Ok, I have now verified that it is using the ApplicationResource.properties file from Callcenter in the /Public context (see previous post). Not sure why this is working this way in 4.0.1. Anyone have any ideas on how to fix this?

Is it a JBOSS configuration issue?

Thanks,

Bret

[starksm64]

See the following class loading configuration links.

http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossClassLoadingUseCases
http://wiki.jboss.org/wiki/Wiki.jsp?page=ClassLoadingConfiguration

The jboss-4.0.2 release ships with the standard servlet 2.3 class loading model enabled by default which is what you want.

[bretg80]

After much research, I did discover this issue as well. Thanks for the reply it confirms my research.

I'm glad the parameter was changed in 4.0.2. I believe the unified classloader is a good idea, but for legacy apps it really creates some serious issues. Also, the documentation doesn't really explain the consequences of the unified loader very well and I'm sure it has created a lot of problems for people.

Bret