4:32 p.m.
Stuart Douglas created CDI-278:
----------------------------------
Summary: Clarify scope of Stateless and Singleton EJB's
Key: CDI-278
URL: https://issues.jboss.org/browse/CDI-278
Project: CDI Specification Issues
Issue Type: Bug
Reporter: Stuart Douglas
At the moment Stateless and Singleton beans are classified as @Dependent scope by default,
which is not really very useful, as a lot of the rules for dependent scoped beans simple
do not apply to them (they violate pretty much every rule for dependent scoped beans in
6.4).
I think we need to define a new scope for these beans, or at least clarify their behaviour
when they are @Dependent scoped.
--
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:36 p.m.
[
https://issues.jboss.org/browse/CDI-278?page=com.atlassian.jira.plugin.sy...
]
Romain Manni-Bucau commented on CDI-278:
----------------------------------------
@ExternalScoped?
Clarify scope of Stateless and Singleton EJB's
----------------------------------------------
Key: CDI-278
URL: https://issues.jboss.org/browse/CDI-278
Project: CDI Specification Issues
Issue Type: Bug
Reporter: Stuart Douglas
At the moment Stateless and Singleton beans are classified as @Dependent scope by
default, which is not really very useful, as a lot of the rules for dependent scoped beans
simple do not apply to them (they violate pretty much every rule for dependent scoped
beans in 6.4).
I think we need to define a new scope for these beans, or at least clarify their
behaviour when they are @Dependent scoped.
--
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:48 p.m.
[
https://issues.jboss.org/browse/CDI-278?page=com.atlassian.jira.plugin.sy...
]
Mark Struberg commented on CDI-278:
-----------------------------------
For the record. This can be found in CDI 1.0 paragraph 3.2
"A stateless session bean must belong to the @Dependent pseudo-scope."
Maybe what he wanted to express was that a stateless session bean must not have any
special CDI scope? (If you don't add anything it gets @Dependent automatically as
defined in another paragraph).
Clarify scope of Stateless and Singleton EJB's
----------------------------------------------
Key: CDI-278
URL: https://issues.jboss.org/browse/CDI-278
Project: CDI Specification Issues
Issue Type: Bug
Reporter: Stuart Douglas
At the moment Stateless and Singleton beans are classified as @Dependent scope by
default, which is not really very useful, as a lot of the rules for dependent scoped beans
simple do not apply to them (they violate pretty much every rule for dependent scoped
beans in 6.4).
I think we need to define a new scope for these beans, or at least clarify their
behaviour when they are @Dependent scoped.
--
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:56 p.m.
[
https://issues.jboss.org/browse/CDI-278?page=com.atlassian.jira.plugin.sy...
]
Stuart Douglas commented on CDI-278:
------------------------------------
But looking at the rules for Dependent scoped beans:
• No injected instance of the bean is ever shared between multiple injection points.
This is false, singletons are shared, and pooled SLSB's are kinda shared.
• Any instance of the bean injected into an object that is being created by the container
is bound to the lifecycle of the newly created object.
Again, not the case
• When a Unified EL expression in a JSF or JSP page that refers to the bean by its EL name
is evaluated, at most one in- stance of the bean is instantiated. This instance exists to
service just a single evaluation of the EL expression. It is re- used if the bean EL name
appears multiple times in the EL expression, but is never reused when the EL expression is
evaluated again, or when another EL expression is evaluated.
Not the case
• Any instance of the bean that receives a producer method, producer field, disposer
method or observer method invoca- tion exists to service that invocation only.
Nope
• Any instance of the bean injected into method parameters of a disposer method or
observer method exists to service the method invocation only (except for observer methods
of container lifecycle events).
Nope
So basically they don't follow any of the rules for @Dependent scoped beans.
Clarify scope of Stateless and Singleton EJB's
----------------------------------------------
Key: CDI-278
URL: https://issues.jboss.org/browse/CDI-278
Project: CDI Specification Issues
Issue Type: Bug
Reporter: Stuart Douglas
At the moment Stateless and Singleton beans are classified as @Dependent scope by
default, which is not really very useful, as a lot of the rules for dependent scoped beans
simple do not apply to them (they violate pretty much every rule for dependent scoped
beans in 6.4).
I think we need to define a new scope for these beans, or at least clarify their
behaviour when they are @Dependent scoped.
--
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:58 p.m.
[
https://issues.jboss.org/browse/CDI-278?page=com.atlassian.jira.plugin.sy...
]
Romain Manni-Bucau commented on CDI-278:
----------------------------------------
all that rules are true for the instance injected == the proxy
think to a cdi extension returning proxies, same issue
Clarify scope of Stateless and Singleton EJB's
----------------------------------------------
Key: CDI-278
URL: https://issues.jboss.org/browse/CDI-278
Project: CDI Specification Issues
Issue Type: Bug
Reporter: Stuart Douglas
At the moment Stateless and Singleton beans are classified as @Dependent scope by
default, which is not really very useful, as a lot of the rules for dependent scoped beans
simple do not apply to them (they violate pretty much every rule for dependent scoped
beans in 6.4).
I think we need to define a new scope for these beans, or at least clarify their
behaviour when they are @Dependent scoped.
--
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 p.m.
[
https://issues.jboss.org/browse/CDI-278?page=com.atlassian.jira.plugin.sy...
]
Mark Struberg commented on CDI-278:
-----------------------------------
Romain, if the CDI and EJB spec mean proxies, then they name it proxies. If they say
'bean' than they mean many things, but very seldom they mean proxies ;)
Clarify scope of Stateless and Singleton EJB's
----------------------------------------------
Key: CDI-278
URL: https://issues.jboss.org/browse/CDI-278
Project: CDI Specification Issues
Issue Type: Bug
Reporter: Stuart Douglas
At the moment Stateless and Singleton beans are classified as @Dependent scope by
default, which is not really very useful, as a lot of the rules for dependent scoped beans
simple do not apply to them (they violate pretty much every rule for dependent scoped
beans in 6.4).
I think we need to define a new scope for these beans, or at least clarify their
behaviour when they are @Dependent scoped.
--
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
2:32 a.m.
[
https://issues.jboss.org/browse/CDI-278?page=com.atlassian.jira.plugin.sy...
]
Romain Manni-Bucau commented on CDI-278:
----------------------------------------
@Mark: yes and no, typically for cdi proxy word was not used but really implicitely
referenced
well regarding the issue i think we don't discuss the fact that singleton (ejb) and
stateless are not directly injected into cdi beans but their proxies, no?
if yes we only need to status how this is handled in the spec
Clarify scope of Stateless and Singleton EJB's
----------------------------------------------
Key: CDI-278
URL: https://issues.jboss.org/browse/CDI-278
Project: CDI Specification Issues
Issue Type: Bug
Reporter: Stuart Douglas
At the moment Stateless and Singleton beans are classified as @Dependent scope by
default, which is not really very useful, as a lot of the rules for dependent scoped beans
simple do not apply to them (they violate pretty much every rule for dependent scoped
beans in 6.4).
I think we need to define a new scope for these beans, or at least clarify their
behaviour when they are @Dependent scoped.
--
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
2:50 a.m.
[
https://issues.jboss.org/browse/CDI-278?page=com.atlassian.jira.plugin.sy...
]
Mark Struberg commented on CDI-278:
-----------------------------------
yes Romain. To sum up:
1.) by injecting an EJB into a CDI bean we will _not_ use CDI proxies but use the EJB
provided ones
2.) the lifecycle of a @Stateless EJB is fundamentally different than a @Dependent CDI
bean. It also doesn't match any other of the lifecycles defined in CDI 1.0.
Clarify scope of Stateless and Singleton EJB's
----------------------------------------------
Key: CDI-278
URL: https://issues.jboss.org/browse/CDI-278
Project: CDI Specification Issues
Issue Type: Bug
Reporter: Stuart Douglas
At the moment Stateless and Singleton beans are classified as @Dependent scope by
default, which is not really very useful, as a lot of the rules for dependent scoped beans
simple do not apply to them (they violate pretty much every rule for dependent scoped
beans in 6.4).
I think we need to define a new scope for these beans, or at least clarify their
behaviour when they are @Dependent scoped.
--
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:12 a.m.
[
https://issues.jboss.org/browse/CDI-278?page=com.atlassian.jira.plugin.sy...
]
Pete Muir updated CDI-278:
--------------------------
Fix Version/s: 1.1 (Proposed)
Clarify scope of Stateless and Singleton EJB's
----------------------------------------------
Key: CDI-278
URL: https://issues.jboss.org/browse/CDI-278
Project: CDI Specification Issues
Issue Type: Bug
Reporter: Stuart Douglas
Fix For: 1.1 (Proposed)
At the moment Stateless and Singleton beans are classified as @Dependent scope by
default, which is not really very useful, as a lot of the rules for dependent scoped beans
simple do not apply to them (they violate pretty much every rule for dependent scoped
beans in 6.4).
I think we need to define a new scope for these beans, or at least clarify their
behaviour when they are @Dependent scoped.
--
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:49 p.m.
[
https://issues.jboss.org/browse/CDI-278?page=com.atlassian.jira.plugin.sy...
]
Pete Muir commented on CDI-278:
-------------------------------
Anyone interested in working on this one? [~bergmark]?
Clarify scope of Stateless and Singleton EJB's
----------------------------------------------
Key: CDI-278
URL: https://issues.jboss.org/browse/CDI-278
Project: CDI Specification Issues
Issue Type: Bug
Reporter: Stuart Douglas
Fix For: 1.1 (Proposed)
At the moment Stateless and Singleton beans are classified as @Dependent scope by
default, which is not really very useful, as a lot of the rules for dependent scoped beans
simple do not apply to them (they violate pretty much every rule for dependent scoped
beans in 6.4).
I think we need to define a new scope for these beans, or at least clarify their
behaviour when they are @Dependent scoped.
--
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
9:41 a.m.
[
https://issues.jboss.org/browse/CDI-278?page=com.atlassian.jira.plugin.sy...
]
Jozef Hartinger commented on CDI-278:
-------------------------------------
With Pete and Stuart we discussed that introducing @StatelessScoped might be the right
approach for SLSB. This scope would act in two roles:
1.) It would be the scope of a SLSB - implicit for every SLSB so that a user does not have
to define both @Stateless and @StatelessScoped on the same class.
2.) For other types of CDI beans @StatelessScoped would guarantee that every method
invocation on the bean is executed on a new instance of a given Bean (Bean.create() is
invoked for every invocation). That would allow the manager pattern (Solder's
@Unwraps) to be used applications.
Clarify scope of Stateless and Singleton EJB's
----------------------------------------------
Key: CDI-278
URL: https://issues.jboss.org/browse/CDI-278
Project: CDI Specification Issues
Issue Type: Bug
Reporter: Stuart Douglas
Fix For: 1.1 (Proposed)
At the moment Stateless and Singleton beans are classified as @Dependent scope by
default, which is not really very useful, as a lot of the rules for dependent scoped beans
simple do not apply to them (they violate pretty much every rule for dependent scoped
beans in 6.4).
I think we need to define a new scope for these beans, or at least clarify their
behaviour when they are @Dependent scoped.
--
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
6:50 p.m.
[
https://issues.jboss.org/browse/CDI-278?page=com.atlassian.jira.plugin.sy...
]
Mark Struberg commented on CDI-278:
-----------------------------------
@StatelessScoped imo is contradicting itself. The most important fact about any
NormalScoped bean is that it has a well defined lifecycle. So it for sure cannot be
NormalScoped. But it would be perfectly possible to treat it as JSR-330 @Scoped. We
don't need to introduce an own annotation for that imo.
Solders @Unwraps is just a workaround for a deficit of CDI Contexts. I think I have
discussed that already with Pete and Stu and we came up with something like adding
destroy(Bean<?>) to a new DisposableContext extends Context interface.
Invoking Bean#create() for every invocation is frankly said crazy. Think about recursive
invocations, etc. a->b->a ... That would end up in an endless loop! It would also be
a performance nightmare.
Clarify scope of Stateless and Singleton EJB's
----------------------------------------------
Key: CDI-278
URL: https://issues.jboss.org/browse/CDI-278
Project: CDI Specification Issues
Issue Type: Bug
Reporter: Stuart Douglas
Fix For: 1.1 (Proposed)
At the moment Stateless and Singleton beans are classified as @Dependent scope by
default, which is not really very useful, as a lot of the rules for dependent scoped beans
simple do not apply to them (they violate pretty much every rule for dependent scoped
beans in 6.4).
I think we need to define a new scope for these beans, or at least clarify their
behaviour when they are @Dependent scoped.
--
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:46 a.m.
[
https://issues.jboss.org/browse/CDI-278?page=com.atlassian.jira.plugin.sy...
]
Pete Muir commented on CDI-278:
-------------------------------
An alternative we discussed is to ask the EJB EG to make @Stateless a scope itself. Mark
will handle this I think.
Clarify scope of Stateless and Singleton EJB's
----------------------------------------------
Key: CDI-278
URL: https://issues.jboss.org/browse/CDI-278
Project: CDI Specification Issues
Issue Type: Bug
Reporter: Stuart Douglas
Fix For: 1.1 (Proposed)
At the moment Stateless and Singleton beans are classified as @Dependent scope by
default, which is not really very useful, as a lot of the rules for dependent scoped beans
simple do not apply to them (they violate pretty much every rule for dependent scoped
beans in 6.4).
I think we need to define a new scope for these beans, or at least clarify their
behaviour when they are @Dependent scoped.
--
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:50 a.m.
[
https://issues.jboss.org/browse/CDI-278?page=com.atlassian.jira.plugin.sy...
]
Mark Struberg commented on CDI-278:
-----------------------------------
Oki, will move this question over to the EJB EG.
Clarify scope of Stateless and Singleton EJB's
----------------------------------------------
Key: CDI-278
URL: https://issues.jboss.org/browse/CDI-278
Project: CDI Specification Issues
Issue Type: Bug
Reporter: Stuart Douglas
Fix For: 1.1 (Proposed)
At the moment Stateless and Singleton beans are classified as @Dependent scope by
default, which is not really very useful, as a lot of the rules for dependent scoped beans
simple do not apply to them (they violate pretty much every rule for dependent scoped
beans in 6.4).
I think we need to define a new scope for these beans, or at least clarify their
behaviour when they are @Dependent scoped.
--
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
4423
days inactive
4452
days old
13 comments
5 participants
participants (5)
-
Jozef Hartinger (JIRA) -
Mark Struberg (JIRA)
-
Pete Muir (JIRA)
-
Romain Manni-Bucau (JIRA)
-
Stuart Douglas (JIRA)