[
http://issues.apache.org/jira/browse/MYFACES-872?page=comments#action_12358615
]
Roland Huss commented on MYFACES-872:
-------------------------------------
Setting the state saving method to client also doesn't work and throws the same
exception. Please find attachted the
stacktraces for both cases.
Some additional hints:
* If one removes the BoardConverter from the configuration, the deserializing
failes with an
ClassNotFoundException for the next application class
* Our application is packaged within an EAR, where we put in all jar toplevel
in the archive
with no jar within the war's WEB-INF/lib. Instead the WAR references its
dependent jars
from within its MANIFEST's classpath attribute:
ear/
myfaces-all.jar
gss-client.jar
gss-client.war
WEB-INF/lib (empty)
META-INF/MANIFEST.MF (classpath: ... myfaces-all.jar gss-client
.jar ...)
This is necessary since we use e.g. spring both in server and client layer
and Spring needs to load
application classes from the server jar as well as from the client jar
> 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
>
> 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
