[
http://issues.apache.org/jira/browse/MYFACES-872?page=comments#action_12358623
]
Dennis Byrne commented on MYFACES-872:
--------------------------------------
Is BoardConverter an implementation of Converter or is that just a coincidence?
Can you tell me a little more about what you mean by "the deserializing failes
with an ClassNotFoundException for the next application class "?
What happens when you try calling the following in you application?
Thread.currentThread().getContextClassLoader().loadClass("class name for
BoardConverter ");
this.getClass().getClassLoader().loadClass("class name for BoardConverter");
The stack traces suggest weblogic is the problem. Have you taken this up w/
them as well? If so, direct them here if you'd like.
> Deserialization of view fails on Weblogic 8.1
> ---------------------------------------------
>
> Key: MYFACES-872
> URL: http://issues.apache.org/jira/browse/MYFACES-872
> Project: MyFaces
> Type: Bug
> Components: Implementation
> Versions: Nightly
> Environment: Linux
> Weblogic 8.1
> Reporter: Roland Huss
> Attachments: client_server_stacktrace.txt, state_server_stacktrace.txt
>
> The current MyFaces SVN snapshot used object serialization for storing the
> view in the session
> (instead of plain objects as it does in 1.1.1)
> This leads to an ClassLoader issue on Weblogic 8.1 during deserialization of
> the view. It seems that
> Weblogic cannot find non-myfaces classes during view-restoring:
> [java] 78230 ERROR .JspStateManagerImpl| Could not deserialize state:
> com.bmw.gss.client.converter.BoardConverter
> [java] java.lang.ClassNotFoundException:
> com.consol.gss.client.converter.BoardConverter
> [java] at
> weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:199)
> [java] at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
> [java] at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
> [java] ....
> [java] at
> org.apache.myfaces.application.jsp.JspStateManagerImpl.deserializeView(JspStateManagerImpl.java:546)
> Strange engough, the client classes and myfaces.jar are loaded by the same
> Classloader (we deployed them as jar within
> an ear which are both referenced from the war's manifest) and except for this
> deserialization issue the can 'see' each
> other.
> I'm not sure, whether this is MyFaces or a Weblogic Issue.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
