[cdi-dev] [JBoss JIRA] (CDI-357) @Stateless and @Singleton session beans are no longer passivation capable dependencies

Joe Bergmark (JIRA) jira-events at lists.jboss.org
Tue Mar 19 15:14:42 EDT 2013

    [ https://issues.jboss.org/browse/CDI-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12761923#comment-12761923 ] 

Joe Bergmark commented on CDI-357:

I think the risk is that this change is not backwards compatible.

In other words could there be an app that deployed successfully following the CDI 1.0 rules, but will now not deploy successfully because EJBs will not always be treated as passivation capable so injecting one into a passivating scope bean could lead to a deployment error?
> @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

More information about the cdi-dev mailing list