Marko Strukelj commented on WELD-510:
I don't think it has anything to do with classloading. It's simply that portals
depend on cross-context includes, and Weld depends on javax.servlet.ServletRequestListener
events to initialize/destroy request context, and javax.servlet.http.HttpSessionListener
to initialize/destroy session context. During cross-context includes the triggering of
events is different from what Weld relies upon.
Specifically, at the moment the sessionCreated event is triggered, Weld expects that
requestInitialized event had occured beforehand and triggered request context
initialization. For cross-context includes this event happens in another context - the one
initially hit by request, not the one crossed over to the portlet application using Weld -
causing Weld to fail.
For Weld 1.0.1.SP3 (Glasfish 3.0.1) the patch has to first address the stacktrace in the
initial description, and then also the cross-context issue.
For Weld 1.1.2.AS7 (JBoss AS7 Final) only the cross-context issue needs addressing
Support for Portlet 2.0
Issue Type: Feature Request
Affects Versions: 1.0.1.Final
Reporter: Neil Griffin
Assignee: Marko Strukelj
Fix For: 1.1.2.Final
There are some folks trying to use the PortletFaces Bridge for JSF 2.0 + Portlet 2.0 in
Glassfish V3, but Weld is causing an issue.
Here is a simple stacktrace of the problem:
Caused by: java.lang.IllegalStateException: Weld doesn not support using JSF in an
The code for the bridge API is here:
The code for the bridge IMPL is here:
And the code for a sample portlet is here:
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira