[jboss-jira] [JBoss JIRA] Commented: (JBAS-5146) com.sun.faces.serializeServerState , java.lang.ClassNotFoundException: boolean
Stan Silvert (JIRA)
jira-events at lists.jboss.org
Mon May 4 07:29:47 EDT 2009
[ https://jira.jboss.org/jira/browse/JBAS-5146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12465519#action_12465519 ]
Stan Silvert commented on JBAS-5146:
------------------------------------
So the old stack trace is now gone when you upgraded JSF? I'm talking about the original one that included:
at com.sun.faces.renderkit.ApplicationObjectInputStream.resolveClass(ApplicationObjectInputStream.java:74)
Yes, this looks like a RichFaces/A4J problem because of:
at org.ajax4jsf.application.AjaxStateManager$1.resolveClass(AjaxStateManager.java:337)
In both cases, resolveClass is not able to handle a primitive type. The JDK itself used to have this problem:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4171142
So if the AjaxStateManager is extending ObjectInputStream and resolveClass() doesn't call super() then you could see this problem.
Please open another Jira against RichFaces and link back to this issue. Also, please leave another comment here when that is done. I want to be able to follow the new issue as it is handled by the RichFaces team.
> com.sun.faces.serializeServerState , java.lang.ClassNotFoundException: boolean
> -------------------------------------------------------------------------------
>
> Key: JBAS-5146
> URL: https://jira.jboss.org/jira/browse/JBAS-5146
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JSF
> Affects Versions: JBossAS-4.2.2.GA
> Environment: JBoss 4.2.2.GA, using JSF RI with Tomahawk.
> Reporter: Dave Chen
> Assignee: Stan Silvert
> Priority: Critical
>
> I am using <t:saveState>, and set com.sun.faces.serializeServerState to true in web.xml.
> <context-param>
> <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
> <param-value>server</param-value>
> </context-param>
>
>
> <context-param>
> <param-name>com.sun.faces.serializeServerState</param-name>
> <param-value>true</param-value>
> </context-param>
> I got the following exception.
> java.lang.ClassNotFoundException: boolean
> at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1358)
> at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1204)
> at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:242)
> at com.sun.faces.renderkit.ApplicationObjectInputStream.resolveClass(ApplicationObjectInputStream.java:74)
> at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1544)
> at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1466)
> at java.io.ObjectInputStream.readClass(ObjectInputStream.java:1433)
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1288)
> at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908)
> at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832)
> at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
> at java.util.ArrayList.readObject(ArrayList.java:591)
--
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 jboss-jira
mailing list