aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Ward (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARIES-669) Proxy or weaving code should mark all its changes synthetic
Date Mon, 06 Jun 2011 21:30:59 GMT

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

Timothy Ward commented on ARIES-669:
------------------------------------

Hi,

There is a slight difference between Richard's suggestion and the current code (based on what
the ASM static init merger does). In the case that a class already has a static init block
both the original static init and the aries proxy code will be added as static methods (not
clinit), with a new static init added that calls both. With the new modifications both the
Aries code and the original code will be marked synthetic, which is probably the wrong thing.to
do

I do agree with the aim of this JIRA though so I think it might be worth reverting the static
init part to add in Richard's proposed fix asap.

> Proxy or weaving code should mark all its changes synthetic
> -----------------------------------------------------------
>
>                 Key: ARIES-669
>                 URL: https://issues.apache.org/jira/browse/ARIES-669
>             Project: Aries
>          Issue Type: Bug
>          Components: Proxy
>    Affects Versions: 0.4
>            Reporter: David Jencks
>
> In order to make it easier for OWB to ignore the additional goo added by the proxy/weaving
stuff, it should all be marked synthetic.  So far I've identified the added SerialVersionUID
field and static_init_* methods as causing problems with the jcdi tck.

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

Mime
View raw message