Pete Muir resolved CDI-120.
Fix Version/s: 1.1.PRD
(was: 1.1 (Proposed))
I talked to Neil Griffin (Liferay) and Mike Freedman (Oracle) at JavaOne, and subsequently
Ken Finnigan (Red Hat), as well as Bill Shannon (Oracle, Java EE spec lead) about how to
move this issue forward.
We came to the conclusion that the CDI spec is not the right place to describe portlet
support, and that this would be much better done in the Portlet and Portlet Bridge
As we don't have revisions of those planned, we agreed that for now we would write up
the support as a wiki page that vendors can optionally agree to support.
I've added https://github.com/jboss/cdi/wiki/CDI-Portlet-integration
to the CDI wiki,
which basically takes all of the changes I proposed for the spec, and makes them into a
Next step is to add JSF specific support to that doc.
Add optional Portlet specification support
Project: CDI Specification Issues
Issue Type: Feature Request
Affects Versions: 1.0
Reporter: Mark Struberg
Assignee: Pete Muir
Fix For: 1.1.PRD
We should mention the portlet specification and how CDI-1.1 should be utilised/supported
in a portlet environment.
This is an important prerequisite for the JSR-344 EG to deprecate the JSF
Imo there is currently no argument which prevents to run a CDI container from running in
a portlet environment anyway. No CDI interface imports any javax.servlet.* class.
It could affect the wording in 6.5.2. which defines the built in scopes as being 'as
defined in the Servlet specification'. We could easily extend this to also cover the
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira