[
https://issues.apache.org/jira/browse/OWB-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065051#comment-13065051
]
Gerhard Petracek commented on OWB-573:
--------------------------------------
i haven't looked into details (so far) but we have to tweak the check you
introduced or to move it to a different place. the benchmark is the one i'm
publishing on a ~regular basis in my blog and is quite simple - it just calls a
method of injected beans (with different scopes) several times. this rev.
caused the problem (0.2ms -> 2ms in average for 1000 method calls). but only
the request scope got that worse. the performance of passivatable scopes is
unchanged. that also fits to the changes made by this rev. if you have a fix,
i'll re-run the benchmark. if it won't change a lot, we can talk in irc about
it because it's simpler compared to jira comments.
> 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
