Marko Strukelj commented on WELD-510:
I think we can move forward. While the idea was to set up testing infrastructure first,
the real challenge was reproducing the issue in the first place, so it got stuck on hold a
But I managed to reproduce it. The exception in the description is only the first issue -
it looks like Weld-1.1.2.AS7 does not suffer from it any more.
The real issue is that Weld at the moment can't handle cross-context includes, and the
reason is that cross-context includes don't trigger request initialization events -
meaning RequestContexts don't get activated. One solution for that would be to install
an optional filter that gets triggered on INCLUDE only, and also check that current
request context is not yet activated (to avoid double init on in-context includes).
Ideally the solution would not require additional web.xml configuration ...
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