[cdi-dev] [JBoss JIRA] (CDI-195) Clarify serializability requirements for extension-provided metadata

Arne Limburg (Commented) (JIRA) jira-events at lists.jboss.org
Tue Nov 22 04:46:42 EST 2011

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

Arne Limburg commented on CDI-195:

Clarifying that this stuff must be Serializable would take much burden on extension developers imho. If I, as an extension developer, add a new Bean to the container I would expect that there never are more instances of that Bean-object hanging around in the container, even after some serialization and deserialization of instances that have injected the Bean. But to achieve that, I could not just make my Bean class Serializable, but I would have to take care of this myself in the Bean implementation (i.e. I would have to implement readObject(...) or such). This kind of stuff should be left to the container imho, that already has similar facilities with the contextual reference stuff.
> Clarify serializability requirements for extension-provided metadata
> --------------------------------------------------------------------
>                 Key: CDI-195
>                 URL: https://issues.jboss.org/browse/CDI-195
>             Project: CDI Specification Issues
>          Issue Type: Feature Request
>          Components: Portable Extensions
>    Affects Versions: 1.0
>            Reporter: Jozef Hartinger
>             Fix For: 1.1 (Proposed)
> The spec never requires an extension-provided implementation of the Bean, Interceptor, Decorator or InjectionPoint to be serializable. The implementation indicates, whether the underlying bean is passivation capable by implementing PassivationCapable, but the implementation itself does not have to be serializable.
> For both the InjectionPoint bean and Bean metadata bean the spec says: "The built-in implementation must be a passivation capable dependency". However, this is hard to guarantee if an extension provides a non-serializable implementation of a Bean/InjectionPoint interface, e.g. the following code would cause problems at passivation:
> {code:JAVA}
> public class Bar implements Serializable {
>    @Inject
>    private InjectionPoint ip;
> }
> {code}
> If the metadata of the Bar bean (Bean<Bar>) is not serializable, Bar cannot be passivated.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the cdi-dev mailing list