[weld-issues] [JBoss JIRA] Updated: (WELD-600) Unable to deserialize Javassist proxy due to wrong classloader being used
[
https://jira.jboss.org/browse/WELD-600?page=com.atlassian.jira.plugin.sys...
]
Pete Muir updated WELD-600:
---------------------------
Fix Version/s: (was: 1.1.0.BETA2)
As this is working with a manual test, and I can't write a test with embedded TC
(which is all Arquillian supports right now), I'm descheduling.
To be clear this issue has been fixed, the issue is simply open to remind us to add a test
when we can.
Unable to deserialize Javassist proxy due to wrong classloader being
used
-------------------------------------------------------------------------
Key: WELD-600
URL: https://jira.jboss.org/browse/WELD-600
Project: Weld
Issue Type: Bug
Components: Servlet Container Support
Environment: Apache Tomcat 6.0.20
Reporter: Fabio Wang
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 contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira