RE: [ajdt-dev] Workaround for bug: java.lang.NoSuchMethodError:makeAdvic

["Ron Bodkin" <rbodkin@xxxxxxxxxxxxxx>]

I forgot to mention the new bug I’m trying to narrow down.I get errors like this when I have a chain of non-static inner classes (worker objects) inside aspects where there’s a cflow on the execution of methods on these classes. Does this look at all familiar, or should I dig in and start narrowing it down?

 

java.lang.NoSuchFieldError: ajc$cflowStack$1

        at glassbox.inspector.monitor.AbstractRequestMonitor$RequestContext.exec

ute(AbstractRequestMonitor.aj:47)

        at glassbox.inspector.monitor.operation.AbstractOperationMonitor.ajc$aro

und$glassbox_inspector_monitor_operation_AbstractOperationMonitor$2$b156e73f_aro

undBody4(AbstractOperationMonitor.aj:88)

        at glassbox.inspector.monitor.operation.AbstractOperationMonitor.ajc$aro

und$glassbox_inspector_monitor_operation_AbstractOperationMonitor$2$b156e73f(Abs

tractOperationMonitor.aj:1)

 

Any idea what might be causing this?

 

 

---

From: ajdt-dev-bounces@xxxxxxxxxxx [mailto:ajdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Ron Bodkin
Sent: Sunday, September 11, 2005 12:48 AM
To: 'AspectJ Development Tools developer discussions'
Subject: [ajdt-dev] Workaround for bug: java.lang.NoSuchMethodError:makeAdviceSig & new bug

 

Hi All,

 

I have two questions about recent AspectJ 5 development builds.

 

I have a program that runs with the latest good developer build, but using M3a gives this stack trace:

java.lang.NoSuchMethodError: makeAdviceSig

        glassbox.inspector.monitor.AbstractRequestMonitor.<clinit>(AbstractRequestMonitor.aj:1)

 

Any idea what bug was causing this (hopefully it’s easy to know from the recent fixes?!) I’d like to explain why an alpha release of the code in my AOP@Work article doesn’t work with AspectJ 1.5.0 M3a…

 

 

Ron Bodkin

Chief Technology Officer

New Aspects of Software

w: (415) 824-4690