[weld-issues] [JBoss JIRA] Updated: (WELDX-38) Unable to deserialize Javassist proxy due to wrong classloader being used
Pete Muir (JIRA)
jira-events at lists.jboss.org
Mon Oct 19 08:59:06 EDT 2009
[ https://jira.jboss.org/jira/browse/WELDX-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pete Muir updated WELDX-38:
---------------------------
Summary: Unable to deserialize Javassist proxy due to wrong classloader being used (was: ConversationScoped not working on Tomcat)
> Unable to deserialize Javassist proxy due to wrong classloader being used
> -------------------------------------------------------------------------
>
> Key: WELDX-38
> URL: https://jira.jboss.org/jira/browse/WELDX-38
> Project: Weld Extensions
> Issue Type: Bug
> Components: Servlet Containers
> Affects Versions: Servlet Containers 1.0.0.CR1
> Environment: Apache Tomcat 6.0.20
> Reporter: Fabio Wang
> Attachments: Action.java, action.xhtml, Bean.java, template.xhtml
>
>
> Trying to mark a conversation as long-running causes an exception (java.lang.NoClassDefFoundError: javassist/util/proxy/ProxyObject) when the ServletConversationManager tries to get a proxy for the httpSession.
> The ProxyFactory.classLoaderProvider ends up resolving the classloader to an instance of org.apache.catalina.loader.StandardClassLoader (which doesn't know the javassist lib, since it's only in the app classloader).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the weld-issues
mailing list