You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openwebbeans.apache.org by "David Blevins (JIRA)" <ji...@apache.org> on 2011/06/19 11:58:47 UTC

[jira] [Updated] (OWB-573) Invalid checking of Interceptor serialization capabilities for non-Passivation capable EJBs

     [ https://issues.apache.org/jira/browse/OWB-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Blevins updated OWB-573:
------------------------------

    Summary: Invalid checking of Interceptor serialization capabilities for non-Passivation capable EJBs  (was: Invalid checking of Interceptor serialization capabilities)

Per current spec only @Stateful session beans should be serializable.

> Invalid checking of Interceptor serialization capabilities for non-Passivation capable EJBs
> -------------------------------------------------------------------------------------------
>
>                 Key: OWB-573
>                 URL: https://issues.apache.org/jira/browse/OWB-573
>             Project: OpenWebBeans
>          Issue Type: Bug
>          Components: Interceptor and Decorators
>            Reporter: David Blevins
>            Assignee: David Blevins
>             Fix For: 1.2.0
>
>
> DefinitionUtil invalidly checks the fields of Interceptor classes to see if they are serializable.  This isn't a requirement of the Interceptor specification.  As well in pure Java serialization terms, there is no requirement that the class types of fields implement Serializable, so a field of say java.lang.Object is OK.  The requirement is that at serialization time that field must point to a serializable instance or be null.  This obviously can only be checked by inspecting instances of a class and cannot be checked statically against the class itself.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira