[
http://jira.jboss.com/jira/browse/JBSEAM-2797?page=comments#action_12414995 ]
Oran Kelly commented on JBSEAM-2797:
------------------------------------
So my specific problem is that Seam is deployed at the top level of my ear.
ResourceBundle.getLoader looks at the caller stack to obtain the "caller's
caller" class and gets its loader. More often than not, the top of the call stack is
FacesMessages -> SeamResourceBundle -> ResourceBundle so the classloader returned is
that of FacesMessages, which is the application-wide classloader (because the Seam jar is
at ear level).
This is why it is caching using the same class loader despite being called from different
webapps.
There should be one ResourceLoader per module inside an EAR
-----------------------------------------------------------
Key: JBSEAM-2797
URL:
http://jira.jboss.com/jira/browse/JBSEAM-2797
Project: Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.0.1.GA
Environment: Windows XP, Seam 2.0.1.GA with JBoss 4.2.1.GA
Reporter: Gregory Tanneau
According to the following scenario :
One MAIN.EAR with two web modules
- APP1.WAR (with messages_one_xx.properties)
- APP2.WAR (with messages_two_xx.properties)
When starting JBoss, the first webapp accessed makes the Resource Loader search for
bundles (ie. I access APP1, messages_one_xx.properties are found).
When the second webapp is accessed, the Resource Loader assumes bundles are already
loaded (messages_two are NOT loaded).
I think there should be (in this case) TWO ResourceLoaders, one per web module.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira