[
https://jira.jboss.org/jira/browse/JBSEAM-3119?page=com.atlassian.jira.pl...
]
Susanne Jarl commented on JBSEAM-3119:
--------------------------------------
This is working fine in Seam 2.2.0.GA except for one thing - the seam graphicImageStore.
It is only working in the first loaded war and in the second war I get the following
exception when trying to view an image using the s:graphicImage tag:
javax.servlet.ServletException: java.lang.IllegalArgumentException: value of context
variable is not an instance of the component bound to the context variable:
org.jboss.seam.ui.graphicImage.graphicImageStore. If you are using hot deploy, you may
have attempted to hot deploy a session or application-scoped component definition while
using an old instance in the session.
at
org.jboss.seam.servlet.ContextualHttpServletRequest.run(ContextualHttpServletRequest.java:74)
at
org.jboss.seam.ui.graphicImage.GraphicImageResource.getResource(GraphicImageResource.java:46)
at org.jboss.seam.servlet.SeamResourceServlet.service(SeamResourceServlet.java:80)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
...
If I only deploy the second war, so there is only one war in the ear, I get no exception
and the images shows up. So I guess this must be a bug. This worked fine in Seam 2.1.0.
Multiple WAR in EAR verification, example, and document
-------------------------------------------------------
Key: JBSEAM-3119
URL:
https://jira.jboss.org/jira/browse/JBSEAM-3119
Project: Seam
Issue Type: Feature Request
Components: Documentation Issues, Examples, Platform interoperability
Affects Versions: 2.1.0.A1
Reporter: Jay Balunas
Assignee: Pete Muir
Fix For: 2.2.0.GA
Attachments: admin-dvdstore.diff, multi-war-appname1.diff, multi-war-wip-v2.diff,
multi-war-wip.diff, multiple-wars.diff, seam-multi-war-2009-06-14.diff
Create an example of two seam WAR applications inside of an EAR. There has been quite a
bit of forum traffic on the subject and it would be good to nail down an example and
document. There may also be errors and other issue that need to be worked out.
An admin console type application to the standard booking application may be a good way
to go. It would be a real world/useful example.
--
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