[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2797) There should be one ResourceLoader per module inside an EAR
1:26 p.m.
There should be one ResourceLoader per module inside an EAR
-----------------------------------------------------------
Key: JBSEAM-2797
URL: http://jira.jboss.com/jira/browse/JBSEAM-2797
Project: JBoss 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 tow 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 cas) 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
1:31 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2797) There should be one ResourceLoader per module inside an EAR
[ http://jira.jboss.com/jira/browse/JBSEAM-2797?page=all ]
Gregory Tanneau updated JBSEAM-2797:
------------------------------------
Description:
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.
was:
According to the following scenario :
One MAIN.EAR with tow 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 cas) TWO ResourceLoaders, one per web module.
There should be one ResourceLoader per module inside an EAR
-----------------------------------------------------------
Key: JBSEAM-2797
URL: http://jira.jboss.com/jira/browse/JBSEAM-2797
Project: JBoss 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
1:38 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2797) There should be one ResourceLoader per module inside an EAR
[ http://jira.jboss.com/jira/browse/JBSEAM-2797?page=comments#action_12405807 ]
Pete Muir commented on JBSEAM-2797:
-----------------------------------
In general, what is the behaviour of Seam when there are two WARs in an EAR?
There should be one ResourceLoader per module inside an EAR
-----------------------------------------------------------
Key: JBSEAM-2797
URL: http://jira.jboss.com/jira/browse/JBSEAM-2797
Project: JBoss 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
4:54 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2797) There should be one ResourceLoader per module inside an EAR
[ http://jira.jboss.com/jira/browse/JBSEAM-2797?page=comments#action_12405927 ]
Gregory Tanneau commented on JBSEAM-2797:
-----------------------------------------
I'm currently testing this configuration. The only issue I found (at the moment) is
related to Seam's Resource Loader.
There should be one ResourceLoader per module inside an EAR
-----------------------------------------------------------
Key: JBSEAM-2797
URL: http://jira.jboss.com/jira/browse/JBSEAM-2797
Project: JBoss 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
5:30 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2797) There should be one ResourceLoader per module inside an EAR
[ 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
3 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2797) There should be one ResourceLoader per module inside an EAR
[ 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
3 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2797) There should be one ResourceLoader per module inside an EAR
[ http://jira.jboss.com/jira/browse/JBSEAM-2797?page=comments#action_12414996 ]
Oran Kelly commented on JBSEAM-2797:
------------------------------------
FYI, I am seeing this problem with Seam 2.0.2.GA and JBoss 4.2.2.GA.
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
6:13 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2797) There should be one ResourceLoader per module inside an EAR
[
https://jira.jboss.org/jira/browse/JBSEAM-2797?page=com.atlassian.jira.pl...
]
Pete Muir updated JBSEAM-2797:
------------------------------
Fix Version/s: 2.1.1.CR1
Assignee: Marek Novotny
There should be one ResourceLoader per module inside an EAR
-----------------------------------------------------------
Key: JBSEAM-2797
URL: https://jira.jboss.org/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
Assignee: Marek Novotny
Fix For: 2.1.1.CR1
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:31 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2797) There should be one ResourceLoader per module inside an EAR
[
https://jira.jboss.org/jira/browse/JBSEAM-2797?page=com.atlassian.jira.pl...
]
Terry commented on JBSEAM-2797:
-------------------------------
Not sure if there is a separate JIRA for this.
There is also an issue with PDF/RTF generation with multiple WARS in as EAR. RTF/PDF only
work in the last WAR loaded. In the other WARs, browser displays alert:
Internet Explorer cannot download ...er-letter.pdf?docId=1&cid=790 from
admin.stage....
Internet Explorer was not able to open this Internet site. The requested site is either
unavailable or cannot be found. Please try again later.
Similar issue in fire fox.
There should be one ResourceLoader per module inside an EAR
-----------------------------------------------------------
Key: JBSEAM-2797
URL: https://jira.jboss.org/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
Assignee: Marek Novotny
Fix For: 2.1.1.CR1
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:33 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2797) There should be one ResourceLoader per module inside an EAR
[
https://jira.jboss.org/jira/browse/JBSEAM-2797?page=com.atlassian.jira.pl...
]
Shane Bryzak updated JBSEAM-2797:
---------------------------------
Fix Version/s: 2.1.1.CR2
(was: 2.1.1.CR1)
There should be one ResourceLoader per module inside an EAR
-----------------------------------------------------------
Key: JBSEAM-2797
URL: https://jira.jboss.org/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
Assignee: Marek Novotny
Fix For: 2.1.1.CR2
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:47 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2797) There should be one ResourceLoader per module inside an EAR
[
https://jira.jboss.org/jira/browse/JBSEAM-2797?page=com.atlassian.jira.pl...
]
Marek Novotny updated JBSEAM-2797:
----------------------------------
Fix Version/s: 2.1.2.CR1
(was: 2.1.1.CR2)
There should be one ResourceLoader per module inside an EAR
-----------------------------------------------------------
Key: JBSEAM-2797
URL: https://jira.jboss.org/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
Assignee: Marek Novotny
Fix For: 2.1.2.CR1
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:37 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2797) There should be one ResourceLoader per module inside an EAR
[
https://jira.jboss.org/jira/browse/JBSEAM-2797?page=com.atlassian.jira.pl...
]
Stuart Douglas commented on JBSEAM-2797:
----------------------------------------
This should be fixed in trunk. ResourceLoader now uses the appropriate servlet context and
SeamResourceBundle caching is is per war.
There should be one ResourceLoader per module inside an EAR
-----------------------------------------------------------
Key: JBSEAM-2797
URL: https://jira.jboss.org/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
Assignee: Marek Novotny
Fix For: 2.2.1.CR1
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:26 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-2797) There should be one ResourceLoader per module inside an EAR
[
https://jira.jboss.org/jira/browse/JBSEAM-2797?page=com.atlassian.jira.pl...
]
Pete Muir closed JBSEAM-2797.
-----------------------------
Fix Version/s: 2.2.0.GA
(was: 2.2.1.CR1)
Resolution: Done
Assignee: Pete Muir (was: Marek Novotny)
Marking as fixed per Stuart's advice. Please report any subsequent problems as new
issues.
There should be one ResourceLoader per module inside an EAR
-----------------------------------------------------------
Key: JBSEAM-2797
URL: https://jira.jboss.org/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
Assignee: Pete Muir
Fix For: 2.2.0.GA
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5487
days inactive
5936
days old
12 comments
7 participants
participants (7)
-
Gregory Tanneau (JIRA) -
Marek Novotny (JIRA)
-
Oran Kelly (JIRA)
-
Pete Muir (JIRA)
-
Shane Bryzak (JIRA)
-
Stuart Douglas (JIRA)
-
Terry (JIRA)