Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [aspectj-users] AJDT stability?

Hi

That could be it.
The errors that we see are usually transactions not getting started or beans not injected being into our domain model (using Spring AspectJ for transactions and bean injection).

/Jeppe

Ron Bodkin wrote:
I still see cases where incremental compilation creates spurious errors like
inter-type declarations that conflict where a full rebuild fixes them. This
happens a lot less often. Much more annoyingly, I'm getting cases where the
compile fails but no output occurs, which of course won't execute correctly.
Perhaps that is what Jeppe is seeing?

I can't remember cases where the compiled result was wrong otherwise...

-----Original Message-----
From: aspectj-users-bounces@xxxxxxxxxxx
[mailto:aspectj-users-bounces@xxxxxxxxxxx] On Behalf Of Andy Clement
Sent: Tuesday, April 25, 2006 6:00 AM
To: aspectj-users@xxxxxxxxxxx
Subject: Re: [aspectj-users] AJDT stability?

I have spent some time this afternoon investigating this problem of
the 'advice disappearing'.  I have found out how it occurs, but it
should only mean that the gutter markers are missing, the 'end result'
should execute just fine (fully advised) - apart from Jeppe, is anyone
else seeing that the result of an incremental compile fails to execute
correctly?

Andy.

On 25/04/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


_______________________________________________
aspectj-users mailing list
aspectj-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/aspectj-users

  

Back to the top