[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2797) There should be one ResourceLoader per module inside an EAR
Stuart Douglas (JIRA)
jira-events at lists.jboss.org
Tue Jun 23 00:37:56 EDT 2009
[ https://jira.jboss.org/jira/browse/JBSEAM-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12473345#action_12473345 ]
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
More information about the seam-issues
mailing list