[jboss-jira] [JBoss JIRA] Updated: (JBAOP-801) incorrect fieldinfo rebuilding due to unmatching order between the instance advisor and class advisor

[Rick Dong (JIRA)]

     [ https://jira.jboss.org/browse/JBAOP-801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rick Dong updated JBAOP-801:
----------------------------

    Fix Version/s: 2.2.1.GA


> incorrect fieldinfo rebuilding due to unmatching order between the instance advisor and class advisor 
> ------------------------------------------------------------------------------------------------------
>
>                 Key: JBAOP-801
>                 URL: https://jira.jboss.org/browse/JBAOP-801
>             Project: JBoss AOP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.1.Alpha3
>            Reporter: Rick Dong
>            Priority: Critical
>             Fix For: 2.2.1.GA
>
>
> Using an instrument class with pre-defined field point cut in an remoting application, all the information about the fieldinfo (read/write) is lost after invoking a method remotely.  This seems to be a bug in the field info rebuilding process in that the 
> GeneratedClassAdvisor.easyFinalizeFieldChainForInstance(Map<Joinpoint, Interceptor[]> oldFieldInfos, FieldInfo[] classFieldInfos, FieldInfo[] newFieldInfos, OldInfoMaps oldInfoMapInstance) simply copying fieldinfos by iterating through
> on the newFieldInfos, but the order of the items in the two arrays newFieldInfos and classFieldInfos are not consistent in which classFieldInfos would have all the field listed based on the index in ascending order and newFieldInfos would have random order.

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