myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stan Silvert (JIRA)" <>
Subject [jira] Commented: (MYFACES-1163) JBoss classloading fails if myfaces jars installed in tomcat
Date Mon, 20 Mar 2006 14:35:59 GMT
    [ ] 

Stan Silvert commented on MYFACES-1163:

Back to the issue at hand, Ingo has reported to me that all Seam examples are working with
the latest fix.  Also, he says that his own application is now working.  

Dennis, are you still seeing a problem?  Maybe you and Ingo can get together to see what is
different about your environments?


> JBoss classloading fails if myfaces jars installed in tomcat
> ------------------------------------------------------------
>          Key: MYFACES-1163
>          URL:
>      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:
For more information on JIRA, see:

View raw message