[
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