[ https://issues.jboss.org/browse/CDI-195?page=com.atlassian.jira.plugin.sy... ] Jozef Hartinger updated CDI-195: -------------------------------- Description: 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. was: 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: public class Bar implements Serializable { @Inject private InjectionPoint ip; } 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

[ https://issues.jboss.org/browse/CDI-195?page=com.atlassian.jira.plugin.sy... ] Arne Limburg commented on CDI-195: ---------------------------------- Does the spec state explicitely that instances can hold DIRECT references to the metadata. The container could inject serializable proxies of the metadata and restore the underlying metadata on deserialization. -- 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

[ https://issues.jboss.org/browse/CDI-195?page=com.atlassian.jira.plugin.sy... ] 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. -- 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

[ https://issues.jboss.org/browse/CDI-195?page=com.atlassian.jira.plugin.sy... ] Jozef Hartinger commented on CDI-195: ------------------------------------- Yes, I was probably missing something at the time I raised the issue since I cannot see the problem anymore. -- 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