[JBoss JIRA] (CDI-294) Clarify that a Java EE component definition never results in a managed bean being created
6:36 a.m.
Jozef Hartinger created CDI-294:
-----------------------------------
Summary: Clarify that a Java EE component definition never results in a
managed bean being created
Key: CDI-294
URL: https://issues.jboss.org/browse/CDI-294
Project: CDI Specification Issues
Issue Type: Clarification
Components: Beans, Java EE integration
Affects Versions: 1.0
Reporter: Jozef Hartinger
Assignee: Pete Muir
Fix For: 1.1 (Proposed)
Having e.g. a Servlet that matches managed bean requirements, there is nothing in the spec
saying that the container should not take the servlet class and make a managed bean out of
it. This results in ProcessInjectionTarget being fired twice. Furthermore, it does not
actually make any sense to have Java EE component definitions (e.g. Servlets) to act as
managed beans.
--
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
10:48 a.m.
[
https://issues.jboss.org/browse/CDI-294?page=com.atlassian.jira.plugin.sy...
]
Pete Muir commented on CDI-294:
-------------------------------
Need to collect community feedback here.
Clarify that a Java EE component definition never results in a
managed bean being created
-----------------------------------------------------------------------------------------
Key: CDI-294
URL: https://issues.jboss.org/browse/CDI-294
Project: CDI Specification Issues
Issue Type: Clarification
Components: Beans, Java EE integration
Affects Versions: 1.0
Reporter: Jozef Hartinger
Assignee: Pete Muir
Fix For: 1.1 (Proposed)
Having e.g. a Servlet that matches managed bean requirements, there is nothing in the
spec saying that the container should not take the servlet class and make a managed bean
out of it. This results in ProcessInjectionTarget being fired twice. Furthermore, it does
not actually make any sense to have Java EE component definitions (e.g. Servlets) to act
as managed beans.
--
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
11:07 a.m.
[
https://issues.jboss.org/browse/CDI-294?page=com.atlassian.jira.plugin.sy...
]
Pete Muir commented on CDI-294:
-------------------------------
What do people think should happen instead if a Servlet class is injected? Options I can
see:
(a) UnsatisfiedResolutionException
(b) return the instance the Servlet container is currently using
I prefer (a).
Also note that the Java EE EG is discussing this problem.
Clarify that a Java EE component definition never results in a
managed bean being created
-----------------------------------------------------------------------------------------
Key: CDI-294
URL: https://issues.jboss.org/browse/CDI-294
Project: CDI Specification Issues
Issue Type: Clarification
Components: Beans, Java EE integration
Affects Versions: 1.0
Reporter: Jozef Hartinger
Assignee: Pete Muir
Fix For: 1.1 (Proposed)
Having e.g. a Servlet that matches managed bean requirements, there is nothing in the
spec saying that the container should not take the servlet class and make a managed bean
out of it. This results in ProcessInjectionTarget being fired twice. Furthermore, it does
not actually make any sense to have Java EE component definitions (e.g. Servlets) to act
as managed beans.
--
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
4:22 p.m.
[
https://issues.jboss.org/browse/CDI-294?page=com.atlassian.jira.plugin.sy...
]
Romain Manni-Bucau commented on CDI-294:
----------------------------------------
In tomcat websockets are servlets (at least currently) and it can make sense to inject the
servlet in a bean to push some data to the client
Clarify that a Java EE component definition never results in a
managed bean being created
-----------------------------------------------------------------------------------------
Key: CDI-294
URL: https://issues.jboss.org/browse/CDI-294
Project: CDI Specification Issues
Issue Type: Clarification
Components: Beans, Java EE integration
Affects Versions: 1.0
Reporter: Jozef Hartinger
Assignee: Pete Muir
Fix For: 1.1 (Proposed)
Having e.g. a Servlet that matches managed bean requirements, there is nothing in the
spec saying that the container should not take the servlet class and make a managed bean
out of it. This results in ProcessInjectionTarget being fired twice. Furthermore, it does
not actually make any sense to have Java EE component definitions (e.g. Servlets) to act
as managed beans.
--
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
11:31 a.m.
[
https://issues.jboss.org/browse/CDI-294?page=com.atlassian.jira.plugin.sy...
]
Pete Muir commented on CDI-294:
-------------------------------
Bill Shannon recommends that we approach we take is not to forbid managed beans being
created (as this requires CDI to know about all types it shouldn't create) but instead
advise that these classes should not have observer methods or producer methods defined on
them, nor should they be injected anywhere, stating the reason that you get a new instance
(which may be unexpected). We might even go so far to recommend they are annotated
@Vetoed?
Clarify that a Java EE component definition never results in a
managed bean being created
-----------------------------------------------------------------------------------------
Key: CDI-294
URL: https://issues.jboss.org/browse/CDI-294
Project: CDI Specification Issues
Issue Type: Clarification
Components: Beans, Java EE integration
Affects Versions: 1.0
Reporter: Jozef Hartinger
Assignee: Pete Muir
Fix For: 1.1 (Proposed)
Having e.g. a Servlet that matches managed bean requirements, there is nothing in the
spec saying that the container should not take the servlet class and make a managed bean
out of it. This results in ProcessInjectionTarget being fired twice. Furthermore, it does
not actually make any sense to have Java EE component definitions (e.g. Servlets) to act
as managed beans.
--
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
4408
days inactive
4435
days old
4 comments
3 participants
participants (3)
-
Jozef Hartinger (JIRA) -
Pete Muir (JIRA)
-
Romain Manni-Bucau (JIRA)