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

["David Blevins (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OWB-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064717#comment-13064717 ] 

David Blevins commented on OWB-573:
-----------------------------------

Sure, happy to look into it.  Not sure how with the info provided.  Would probably need either some info on the benchmark (which part is slow or maybe performance data that shows where the biggest tim change is) or the benchmark itself.  Or even a test case that can show the slowdown.


> 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