]
Stuart Douglas updated JBSEAM-4590:
-----------------------------------
Attachment: graphicImageFix.diff
The attached patch might fix the graphic image issue
Multiple war in ear - resources not isolated between wars
----------------------------------------------------------
Key: JBSEAM-4590
URL:
https://jira.jboss.org/jira/browse/JBSEAM-4590
Project: Seam
Issue Type: Bug
Affects Versions: 2.2.0.GA
Environment: JBoss 5.1.0.GA, Hot deployment. JDK 1.6
Reporter: Susanne Jarl
Assignee: Stuart Douglas
Attachments: graphicImageFix.diff
If you have a.war and b.war in an ear and try to send an email using
org.jboss.seam.faces.Renderer this will only work for b.war and in a.war you will get an
exception saying that the resource in b.war could not be found. So the renderer called
from a.war looks for resources in b.war.
Kind of the same problem with s.graphicImage, only working in b.war, and when used in
a.war the exception says it is looking for resources in b.war.
I use hot deployment.
If I start my application with only one of the war files at the time everything works
perfectly fine. These issues did not exist in version 2.0.X, they appeared in 2.1. and has
been around since then although changed a little between versions.
I have also tried 2.2.1. nightly build #164, since I thought that JBSEAM-4316 might solve
this, but unfortunatally it did not.
I have in each war a jboss-web.xml looking like this example (with of course different
unique names):
<jboss-web>
<class-loading java2ClassLoadingCompliance="false">
<loader-repository>
org.jboss.seam:archive=uniquename
<loader-repository-config>java2ParentDelegation=false</loader-repository-config>
</loader-repository>
</class-loading>
</jboss-web>
jboss-app.xml looks like this:
<jboss-app>
<loader-repository>
org.jboss.seam:archive=myapp
<loader-repository-config>
java2ParentDelegation=false
</loader-repository-config>
</loader-repository>
</jboss-app>
Please solve this bug until next release. Thank you!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: