myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis Byrne (JIRA)" <>
Subject [jira] Commented: (MYFACES-1163) JBoss classloading fails if myfaces jars installed in tomcat
Date Tue, 14 Mar 2006 07:27:40 GMT
    [ ] 

Dennis Byrne commented on MYFACES-1163:

Can either/both of you please give me a detailed set of instructions on how to reproduce this
( w/out facelets )?  Please post a stacktrace or something.  I believe you guys but I am having
a hard time reproducing what may or may not be the problem.  Some of the errors I'm getting
both w/ and w/out Stan's patch have no explanation.  

> JBoss classloading fails if myfaces jars installed in tomcat
> ------------------------------------------------------------
>          Key: MYFACES-1163
>          URL:
>      Project: MyFaces Core
>         Type: Bug
>     Versions: 1.1.2-SNAPSHOT, 1.1.2, 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