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?
See the following class loading configuration links.
The jboss-4.0.2 release ships with the standard servlet 2.3 class loading model enabled by default which is what you want.
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.