[weld-issues] [JBoss JIRA] (WELD-600) Unable to deserialize Javassist proxy due to wrong classloader being used

Ales Justin (JIRA) jira-events at lists.jboss.org
Mon Feb 27 12:28:39 EST 2012


     [ https://issues.jboss.org/browse/WELD-600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ales Justin resolved WELD-600.
------------------------------

    Resolution: Out of Date

    
> Unable to deserialize Javassist proxy due to wrong classloader being used
> -------------------------------------------------------------------------
>
>                 Key: WELD-600
>                 URL: https://issues.jboss.org/browse/WELD-600
>             Project: Weld
>          Issue Type: Bug
>          Components: Servlet Container Support
>         Environment: Apache Tomcat 6.0.20
>            Reporter: Fabio Wang
>             Fix For: TBC
>
>         Attachments: Action.java, action.xhtml, Bean.java, jersey-gf-bundle.jar, 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, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the weld-issues mailing list