[MYFACES-1163] JBoss classloading fails if myfaces jars installed in tomcat

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.1.2-SNAPSHOT, 1.1.3-SNAPSHOT
• Environment: JBoss 4.0.4RC1 myfaces-1.1.3-SNAPSHOT
• Assignee: Stan D. Silvert
• Reporter: Ingo Massen
• Created: 07/Mar/06 19:40
• Updated: 17/Apr/06 20:54
• Resolved: 28/Mar/06 07:07

Description

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.

Issue Links

• is related to: MYFACES-1149 StateUtils has a static inializer that calls FacesContext.getCurrentInstance()