[
https://issues.jboss.org/browse/CDI-357?page=com.atlassian.jira.plugin.sy...
]
Jozef Hartinger reopened CDI-357:
---------------------------------
Actually, one more minor issue with this.
It would be cleaner better not to repeat the part about passivationCapable flag in
multiple places and rather say that:
{quote}all stateful session beans which are passivation capable beans are passivation
capable dependencies{quote}
Furthermore, the definition of passivation capable beans needs minor wording cleanup. It
currently says:
{quote}
As defined by the EJB specification, all stateful session beans are passivation capable
if:
interceptors and decorators of the bean are passivation capable, and,
the stateful session bean does not have the passivationCapable flag set to false.
{quote}
and should rather say:
{quote}
As defined by the EJB specification, *a* stateful session bean *is* passivation capable
if:
interceptors and decorators of the bean are passivation capable, and,
the stateful session bean does not have the passivationCapable flag set to false.
{quote}
@Stateless and @Singleton session beans are no longer passivation
capable dependencies
--------------------------------------------------------------------------------------
Key: CDI-357
URL:
https://issues.jboss.org/browse/CDI-357
Project: CDI Specification Issues
Issue Type: Bug
Components: Beans
Affects Versions: 1.1.PFD
Reporter: Jozef Hartinger
Assignee: Pete Muir
Priority: Blocker
Fix For: 1.1.FD
This is a regression since 1.0
CDI 1.0:
{quote}all session beans are passivation capable dependencies{quote}
CDI 1.1:
{quote}all passivation capable beans with scope @Dependent are passivation capable
dependencies{quote}
and
{quote}As defined by the EJB specification, stateless and singleton session beans are not
passivation capable{quote}
--
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