[cdi-dev] [JBoss JIRA] (CDI-317) review PassivationCapable interface

Jozef Hartinger (JIRA) jira-events at lists.jboss.org
Mon Jan 14 02:38:21 EST 2013

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

Jozef Hartinger commented on CDI-317:

{quote}For e.g. a ProducerMethodBean it depends on the scope of the produced instance.{quote}

It does not. It works the other way around. If a bean has a passivating scope it has to be passivation capable. However, a bean may be passivation capable yet not have a passivating scope.
> review PassivationCapable interface
> -----------------------------------
>                 Key: CDI-317
>                 URL: https://issues.jboss.org/browse/CDI-317
>             Project: CDI Specification Issues
>          Issue Type: Bug
>          Components: Beans
>            Reporter: Mark Struberg
> Currently the spec says that only _passivation capable Beans_ must implement the PassivationCapable interface.
> But a Bean class could result in both passivation-capable and not-passivation-capable beans. For e.g. a ProducerMethodBean it depends on the scope of the produced instance. For implementing this properly you would need to always need 2 classes for each bean-type. And even worse - often you know only after the all the Bean-building that this very bean is passivation-capable or not.
> Thus I suggest to extend the meaning of PassivationCapable#getId() to allow returning *null* if the very bean doesn't support passivation.

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