6:39 p.m.
Add an optional Portlet specification support
---------------------------------------------
Key: CDI-120
URL: https://issues.jboss.org/browse/CDI-120
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Contexts
Reporter: Mark Struberg
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
@javax.faces.bean.ManagedBean capabilities.
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
portlet definition.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:45 p.m.
New subject: [JBoss JIRA] Updated: (CDI-120) Add optional Portlet specification support
[
https://issues.jboss.org/browse/CDI-120?page=com.atlassian.jira.plugin.sy...
]
Mark Struberg updated CDI-120:
------------------------------
Summary: Add optional Portlet specification support (was: Add an optional Portlet
specification support)
Add optional Portlet specification support
------------------------------------------
Key: CDI-120
URL: https://issues.jboss.org/browse/CDI-120
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Contexts
Reporter: Mark Struberg
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
@javax.faces.bean.ManagedBean capabilities.
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
portlet definition.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:37 p.m.
New subject: [JBoss JIRA] Updated: (CDI-120) Add optional Portlet specification support
[
https://issues.jboss.org/browse/CDI-120?page=com.atlassian.jira.plugin.sy...
]
Pete Muir updated CDI-120:
--------------------------
Fix Version/s: 1.1 (Proposed)
Affects Version/s: 1.0
Add optional Portlet specification support
------------------------------------------
Key: CDI-120
URL: https://issues.jboss.org/browse/CDI-120
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Contexts
Affects Versions: 1.0
Reporter: Mark Struberg
Fix For: 1.1 (Proposed)
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
@javax.faces.bean.ManagedBean capabilities.
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
portlet definition.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:22 p.m.
New subject: [JBoss JIRA] Commented: (CDI-120) Add optional Portlet specification support
[
https://issues.jboss.org/browse/CDI-120?page=com.atlassian.jira.plugin.sy...
]
Pete Muir commented on CDI-120:
-------------------------------
Mark, would you be able to take a stab at this issue?
Add optional Portlet specification support
------------------------------------------
Key: CDI-120
URL: https://issues.jboss.org/browse/CDI-120
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Contexts
Affects Versions: 1.0
Reporter: Mark Struberg
Fix For: 1.1 (Proposed)
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
@javax.faces.bean.ManagedBean capabilities.
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
portlet definition.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:34 p.m.
New subject: [JBoss JIRA] (CDI-120) Add optional Portlet specification support
[
https://issues.jboss.org/browse/CDI-120?page=com.atlassian.jira.plugin.sy...
]
Jason Porter commented on CDI-120:
----------------------------------
Do we have an update for this? I'm sure Ken would also be interested in this.
Add optional Portlet specification support
------------------------------------------
Key: CDI-120
URL: https://issues.jboss.org/browse/CDI-120
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Contexts
Affects Versions: 1.0
Reporter: Mark Struberg
Fix For: 1.1 (Proposed)
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
@javax.faces.bean.ManagedBean capabilities.
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
portlet definition.
--
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
3:56 p.m.
New subject: [JBoss JIRA] (CDI-120) Add optional Portlet specification support
[
https://issues.jboss.org/browse/CDI-120?page=com.atlassian.jira.plugin.sy...
]
Pete Muir updated CDI-120:
--------------------------
Assignee: Pete Muir
Fix Version/s: 1.1.PRD
(was: 1.1 (Proposed))
First draft at https://github.com/jboss/cdi/pull/107
Add optional Portlet specification support
------------------------------------------
Key: CDI-120
URL: https://issues.jboss.org/browse/CDI-120
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Contexts
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
@javax.faces.bean.ManagedBean capabilities.
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
portlet definition.
--
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
12:56 p.m.
New subject: [JBoss JIRA] (CDI-120) Add optional Portlet specification support
[
https://issues.jboss.org/browse/CDI-120?page=com.atlassian.jira.plugin.sy...
]
Pete Muir updated CDI-120:
--------------------------
Fix Version/s: 1.1 (Proposed)
(was: 1.1.PRD)
Add optional Portlet specification support
------------------------------------------
Key: CDI-120
URL: https://issues.jboss.org/browse/CDI-120
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Contexts
Affects Versions: 1.0
Reporter: Mark Struberg
Assignee: Pete Muir
Fix For: 1.1 (Proposed)
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
@javax.faces.bean.ManagedBean capabilities.
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
portlet definition.
--
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
5:35 p.m.
New subject: [JBoss JIRA] (CDI-120) Add optional Portlet specification support
[
https://issues.jboss.org/browse/CDI-120?page=com.atlassian.jira.plugin.sy...
]
Pete Muir commented on CDI-120:
-------------------------------
We're going to put this on the CDI wiki, and not in the spec.
Add optional Portlet specification support
------------------------------------------
Key: CDI-120
URL: https://issues.jboss.org/browse/CDI-120
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Contexts
Affects Versions: 1.0
Reporter: Mark Struberg
Assignee: Pete Muir
Fix For: 1.1 (Proposed)
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
@javax.faces.bean.ManagedBean capabilities.
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
portlet definition.
--
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
7 p.m.
New subject: [JBoss JIRA] (CDI-120) Add optional Portlet specification support
[
https://issues.jboss.org/browse/CDI-120?page=com.atlassian.jira.plugin.sy...
]
Pete Muir resolved CDI-120.
---------------------------
Fix Version/s: 1.1.PRD
(was: 1.1 (Proposed))
Resolution: Done
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
specifications.
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
standalone doc.
Next step is to add JSF specific support to that doc.
Add optional Portlet specification support
------------------------------------------
Key: CDI-120
URL: https://issues.jboss.org/browse/CDI-120
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Contexts
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
@javax.faces.bean.ManagedBean capabilities.
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
portlet definition.
--
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
4213
days inactive
4752
days old
8 comments
3 participants
participants (3)
-
Jason Porter (JIRA) -
Mark Struberg (JIRA)
-
Pete Muir (JIRA)