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

Jozef Hartinger (JIRA) jira-events at lists.jboss.org
Wed Mar 27 11:45:42 EDT 2013

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

Jozef Hartinger commented on CDI-357:

Not all session beans are passivation capable *beans* but since access to them is proxied I cannot see a reason why stateless session beans and singletons could not be passivation capable *dependencies*. It's the same as with normal-scoped beans which are always *passivation capable dependencies* no matter if the bean is *passivation capable bean*
> @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