[jboss-jira] [JBoss JIRA] Updated: (JBAOP-731) problem with javac->aopc->javac sequence

Thu May 21 19:37:56 EDT 2009

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

Konstantin Sobolev updated JBAOP-731:
-------------------------------------

    Attachment: POJO.j


decompiled POJO.class

> problem with javac->aopc->javac sequence
> ----------------------------------------
>
>                 Key: JBAOP-731
>                 URL: https://jira.jboss.org/jira/browse/JBAOP-731
>             Project: JBoss AOP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.1.1.GA
>         Environment: JDK 1.6.0_13/32bit
>            Reporter: Konstantin Sobolev
>         Attachments: bug.tar.gz, POJO.j
>
>
> I'm trying to switch from JBossAOP 1.5.6 to 2.1.1 and can't build my project, looks like there are some problems with aop-compiled classes. Here's what happens: first we build our interface classes, let's say there's *abstract* POJO1 among them. Then we run AopC on them, and it modifies POJO1.class
> Then we compile some more classes, and there's non-abstract POJO2 there, which extends POJO1. At this time javac fails with this message:
> POJO2 is not abstract and does not override abstract method _getAdvisor() in org.jboss.aop.Advised
> javap shows that POJO1 now implements Advisable and indeed contains _getAdvisor() method, but this method is not abstract! I'm confused.
> Running AopC after compiling all of the classes works fine. Making POJO1 non-abstract also makes javac happy.
> I'm attaching a testcase. Unpack it into jboss-aop-2.1.1.GA/docs/aspect-framework/examples/bug and run ant there to reproduce the problem.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira