[
http://jira.jboss.com/jira/browse/JBSEAM-2797?page=comments#action_12414807 ]
Oran Kelly commented on JBSEAM-2797:
------------------------------------
I've hit this problem too. I think the main problem is in
SeamResourceBundle.getBundle. It delegates to java.util.ResourceBundle.getBundle using its
class name as the bundle name. java.util.ResourceBundle caches bundles in a private static
member variable, using the bundle name, the locale and a class loader.
It would appear that once you've loaded the first webapp, its resource bundle is
cached. Then when you hit the second webapp, it is seeing the first webapp's cached
resource bundle.
I guess the only way this could happen is if java.util.ResourceBundle.getLoader returned
the same classloader for both webapps. I am having trouble seeing which class loader is
returned by this method at the moment, if I find anything further I'll post.
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