[ http://issues.apache.org/jira/browse/MYFACES-1163?page=comments#action_12371085 ]
Stan Silvert commented on MYFACES-1163: --------------------------------------- Hello Cristi, Please keep each jira task confined to a single issue. Also, have you asked about this on the MyFaces user forum or the Seam forum? Do you have a test case that reproduces the problem? Do you have a proposed fix? Any or all of these things will help you get your problem resolved much faster. I doubt that anyone has time to do the research for you on this, but if all else fails you can open a new jira task for it. Regards, Stan > JBoss classloading fails if myfaces jars installed in tomcat > ------------------------------------------------------------ > > Key: MYFACES-1163 > URL: http://issues.apache.org/jira/browse/MYFACES-1163 > Project: MyFaces Core > Type: Bug > Versions: 1.1.2, 1.1.2-SNAPSHOT, 1.1.3-SNAPSHOT > Environment: JBoss 4.0.4RC1 myfaces-1.1.3-SNAPSHOT > Reporter: Ingo Massen > Assignee: Stan Silvert > > Cannot use Myfaces jars installed in > JBOSS_HOME/server/default/deploy/jbossweb-tomcat55.sar/jsf-libs as they do > not use the correct WebappClassloader but instead an UCL3 classloader. > This is because myfaces use the following line in StateUtils.getAsObject > ObjectInputStream s = new ObjectInputStream(input); > instead of > import org.apache.myfaces.shared.util.MyFacesObjectInputStream; > ObjectInputStream s = new MyFacesObjectInputStream(input); > The same applies to JspStateManagerImpl.deserializeView(). > ObjectInputStream uses Class.forName instead of > Thread.currentThread().getContextClassLoader() as the ClassUtils > implementation that MyFacesObjectInputStream uses does. -- 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
