[
https://issues.apache.org/jira/browse/OWB-579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13042957#comment-13042957
]
Joe Bergmark commented on OWB-579:
----------------------------------
This appears to contradict section 5.5.1 of the specification. It explicitly
says that classes with final methods can not be proxied and that this should be
treated as a deployment error.
My gut feel is we should leave the spec behavior as the default, and then
provide some way to opt-out when it makes sense.
> check for non-proxyiable methods should exclude synthetic methods
> -----------------------------------------------------------------
>
> Key: OWB-579
> URL: https://issues.apache.org/jira/browse/OWB-579
> Project: OpenWebBeans
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.1.1
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 1.1.1
>
>
> Aries trunk has some weaving code that adds some final synthetic methods to
> just about every class. AFAICT javassist can still proxy these classes but
> OWB check for proxiablility fails.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
