[
https://jira.jboss.org/jira/browse/JBSEAM-2579?page=com.atlassian.jira.pl...
]
Stuart Douglas commented on JBSEAM-2579:
----------------------------------------
This is fixed in trunk, I verified that the test case provided no longer demonstrates the
bug.
Messages.properties do not work as expected with multiple WARs inside
multiple Seam EARs
----------------------------------------------------------------------------------------
Key: JBSEAM-2579
URL:
https://jira.jboss.org/jira/browse/JBSEAM-2579
Project: Seam
Issue Type: Bug
Components: JSF Integration
Affects Versions: 2.0.1.GA
Environment: JBoss 4.2.2
Reporter: Reind D
Fix For: The future
Attachments: messages_defect.tar.gz
When 2 Seam apps are deployed, both with multiple WARs each of which as a
WEB-INF/classes/messages.properties file, the messages for one of the web contexts will
not work. Instead, the messages for the other WAR in the same EAR will be displayed.
I've attached a sample application that demonstrates this behavior. It is modified
from the "Registration" example.
Steps:
1) Untar the archive
2) Copy to the app server's deploy directory
3) Go to the following URLs:
http://localhost:8080/a/register.seam
http://localhost:8080/b/register.seam
http://localhost:8080/c/register.seam
http://localhost:8080/d/register.seam
The 'expected' and 'actual' fields should always match, but they
won't in 1 case.
--
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