11:48 a.m.
Hot deploy JSF deserialization
------------------------------
Key: JBSEAM-1645
URL: http://jira.jboss.com/jira/browse/JBSEAM-1645
Project: JBoss Seam
Issue Type: Bug
Components: JSF
Affects Versions: 1.2.1.GA
Environment: Seam 1.2.1.GA
Reporter: Samuel Mendenhall
Using a war deployment (as built by seam-gen), any classes placed in src/action are
hot-deploy enabled, causing them to be loaded off a different classloader, when they are
deserialised by JSF the wrong classloader is used.
--
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
12:43 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Assigned: (JBSEAM-1645) Hot deploy JSF deserialization
[ http://jira.jboss.com/jira/browse/JBSEAM-1645?page=all ]
Norman Richards reassigned JBSEAM-1645:
---------------------------------------
Assignee: Norman Richards
Hot deploy JSF deserialization
------------------------------
Key: JBSEAM-1645
URL: http://jira.jboss.com/jira/browse/JBSEAM-1645
Project: JBoss Seam
Issue Type: Bug
Components: JSF
Affects Versions: 1.2.1.GA
Environment: Seam 1.2.1.GA
Reporter: Samuel Mendenhall
Assigned To: Norman Richards
Using a war deployment (as built by seam-gen), any classes placed in src/action are
hot-deploy enabled, causing them to be loaded off a different classloader, when they are
deserialised by JSF the wrong classloader is used.
--
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:09 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-1645) Hot deploy JSF deserialization
[ http://jira.jboss.com/jira/browse/JBSEAM-1645?page=all ]
Norman Richards closed JBSEAM-1645.
-----------------------------------
Fix Version/s: 2.0.0.CR1
Resolution: Done
This is only a problem when hot deployable classes are stored in the view and client side
state saving is used. The best solution would be to use server state. Where this
isn't acceptable, I've added a SerializationProvider implementation that is aware
of Seam's hot deployable classloaders. It can be enabled with the JSF RI by adding
the following to web.xml:
<context-param>
<param-name>com.sun.faces.serializationProvider</param-name>
<param-value>org.jboss.seam.faces.SeamDebugSerializationProvider</param-value>
</context-param>
Note that this implementation is not compatible with JBoss serialization but could easily
be made compatible where JBoss serialization is desired.
Hot deploy JSF deserialization
------------------------------
Key: JBSEAM-1645
URL: http://jira.jboss.com/jira/browse/JBSEAM-1645
Project: JBoss Seam
Issue Type: Bug
Components: JSF
Affects Versions: 1.2.1.GA
Environment: Seam 1.2.1.GA
Reporter: Samuel Mendenhall
Assigned To: Norman Richards
Fix For: 2.0.0.CR1
Using a war deployment (as built by seam-gen), any classes placed in src/action are
hot-deploy enabled, causing them to be loaded off a different classloader, when they are
deserialised by JSF the wrong classloader is used.
--
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
6840
days inactive
6842
days old
2 comments
2 participants
participants (2)
-
Norman Richards (JIRA) -
Samuel Mendenhall (JIRA)