Re: [aspectj-users] AJDT stability?

["Howard Lewis Ship" <hlship@xxxxxxxxx>]

Things are mostly better since upgrading to 3.1.2, though the AspectJ
visualizer doesn't seem to work anymore.

I've been using mostly before() advice on execution()s. I use
annotations to identify methods to be advised (or sometimes,
annotations to identify methods not to be advised). Generally, there's
a type annotation that triggers everything. I posted pretty detailed
examples earlier.

I'm using abstract aspects as well.  Generally, my concrete aspects
are tiny, just identifying a set of classes to affect. That set of
classes is narrowed down by the presence of a type annotation.

On 4/25/06, Andy Clement <andrew.clement@xxxxxxxxx> wrote:
> I think this problem:
>
> > Often (especially after editting an aspect), advised methods are not
> > decorated until I do a clean build.
>
> is possibly dependent on what language features you are using because
> not everyone is affected.  To get to the bottom of it, can you tell me
> what features you are using? before/after/around advice? itds? per
> clauses? generics? what pointcuts - cflow? abstract aspects?
>
> Andy.
>
> On 24/04/06, Jeppe Cramon <jeppe@xxxxxxxxx> wrote:
> > Btw. This happens on both 3.1.2 and 3.2M6.
> >
> > /Jeppe
> >
> > Jeppe Cramon wrote:
> > > Hi
> > >
> > > We experience from time to time that our code doesn't get advised. We
> > > have to clean the project(s) to get the properly weaved.
> > > We usually notice it at runtime when things bomb or NP's occur. Not so
> > > pleasant.
> > >
> > > /Jeppe
> > >
> > > Howard Lewis Ship wrote:
> > >> How are others finding the stability of the AJDT?  I'm running latest
> > >> and greatest and see a lof of problems:
> > >>
> > >> Often (especially after editting an aspect), advised methods are not
> > >> decorated until I do a clean build.
> > >>
> > >> I get a goodly number of exceptions (with that panel that advises me
> > >> to "add a bug").
> > >>
> > >> Often, my aspects will not appear in the Type view.  Sometimes, even a
> > >> restart of Eclipse does not fix this (though a close and re-open of
> > >> the project will!).
> > >>
> > >> --
> > >> Howard M. Lewis Ship
> > >> Independent J2EE / Open-Source Java Consultant
> > >> Creator, Jakarta Tapestry
> > >> Creator, Jakarta HiveMind
> > >>
> > >> Professional Tapestry training, mentoring, support
> > >> and project work.  http://howardlewisship.com
> > >> _______________________________________________
> > >> aspectj-users mailing list
> > >> aspectj-users@xxxxxxxxxxx
> > >> https://dev.eclipse.org/mailman/listinfo/aspectj-users
> > >>
> > >>
> > > _______________________________________________
> > > aspectj-users mailing list
> > > aspectj-users@xxxxxxxxxxx
> > > https://dev.eclipse.org/mailman/listinfo/aspectj-users
> > >
> > _______________________________________________
> > aspectj-users mailing list
> > aspectj-users@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/aspectj-users
> >
> _______________________________________________
> aspectj-users mailing list
> aspectj-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/aspectj-users
>


--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind

Professional Tapestry training, mentoring, support
and project work.  http://howardlewisship.com