gmane.comp.java.aop.aspectj.general

Some Noob Design Questions

El Lunes — 2012-05-24T10:00:44

Hallo

I am pretty new to AspectJ and I want to add interfaces to some classes. I
have to do this with AspectJ, because I need these interfaces for testing
but I am not allowed to change the code.
It was no problem to add the interfaces but I am not sure where to put the
code. Is it better to create only one aspect that adds all the interfaces
or should I use one aspect per interface?

I have the same question regarding added methods. One aspect per class or
on aspect that adds all methods to all classes?

Thanks for your help!
_______________________________________________
aspectj-users mailing list
aspectj-users< at >eclipse.org
https://dev.eclipse.org/mailman/listinfo/aspectj-users

convert unchecked-exception to checked-exception

Straub Oliver — 2012-05-24T09:06:04

Hello,
there has been long discussions on checked vs. unchecked exceptions.
I don't want to start this discussion again.

I know, the opposite behaviour can be achieved by "declare soft ..."

In my case i have to convert any exception to a layer-specific checked
exception.
This behaviour shall be controllable (on/off) with the presence of a
method-annotation.
Here an example:

  < at >DSExceptionTranslator
  private void anyMethod() throws DSException {
      throw new PersistException();
  }

Obvious the above code will normally generate an unhandled-exception-error.
I expected the following advice to solve that.

  after() throwing (Exception ex) throws DSException : mypointcut() {
      throw new DSException(ex);
  }

But the unhandled-exception-error did not disappear!

So i added a "declare soft":

  declare soft : Exception : mypointcut();

The unhandled-exception-error disappears, but this did not solve my problem
because the generated code looks like this:

try {
   try {
       throw new PersistException();
   } catch(Exception exception) {

ThrowDSExceptionAspect.aspectOf().ajc$afterThrowing$com_gid_bip_dataservice_aj_ThrowDSExceptionAspect$1$e66f2abe(exception);
      throw exception;
   }
} catch(Exception exception1) {
    if(exception1 instanceof RuntimeException)
       throw exception1;
    else
       throw new SoftException(exception1);
}

As we can see, my new DSException is softened too and is thrown as a
SoftException.
It seems that the code for "declare soft" will always be weaved as last
step.
I tried "declare precedence" to control the weaving-process, but nothing
changes!

==== Is there any other way to avoid the unhandled-exception-error? ====

I found similar Questions in several lists, but the solutions all did not
work with the current release of AspectJ 1.6.12.M1 (ajdt 2.1.3).

Thank you in advance
_______________________________________________
aspectj-users mailing list
aspectj-users< at >eclipse.org
https://dev.eclipse.org/mailman/listinfo/aspectj-users

Re: Use of aop.xml

Andy Clement — 2012-05-23T15:03:17

Hi,

If your aspects are 'ready to go' (i.e. non-abstract), you can just
define a trivial aop.xml that lists them:

<aspectj>
 <aspects>
  <aspect name="com.foo.MyAspect"/>
 </aspects>
</aspectj>

In face you can create that file automatically if you compile with
-outxml specified, it will create a suitable aop.xml listing all the
aspects you are compiling.

If you want to be more flexible in the wiring, it is possible to
define the pointcuts in aop.xml, and wire them to Java methods that
get treated like advice.  For example:

<aspectj>
  <aspects>
<concrete-aspect name="MyAspect">
  <before pointcut="execution(* Hello.say2(..)) AND args(message)"
   invokeClass="SomeRegularJavaClass"
   invokeMethod="someMethod(JoinPoint tjp, java.lang.String message)"/>
  <after pointcut="execution(* Hello.say2(..)) AND args(message)"
   invokeClass="SomeRegularJavaClass"
   invokeMethod="someOtherMethod(JoinPoint tjp, java.lang.String message)"/>
</concrete-aspect>
  </aspects>
</aspectj>

This kind of usage is discussed in detail in here:
http://www.eclipse.org/aspectj/doc/released/README-1612.html

cheers,
Andy

On 23 May 2012 03:45, Bhavuk soni <bhavuksoni< at >gmail.com> wrote:

Use of aop.xml

Bhavuk soni — 2012-05-23T10:45:50

Hi,

I am working on a similar solution like yours, where i have to weave an
aspect during execution of a method.
I am working on a solution where mock dependencies for junits are done with
AspectJ(without spring)
and during execution of a test method those dependencies should be weaved so
that the real calls to the classes/ DB can be replaced by mock classes.

I am done with my aspect code, but i am unable to weave this aspect to the
code, point is that i have to do this using aop.xml.

The project structure is like that

1.Aspects- Here all the aspects are written, they are not ABSTRACT, as the
requirement is like that

2.Tests - Here all the tests are written

The test project .classpath has refrences to aspects and the code base
project.

If you can help with a small snippet , it would be great.

Thanks,
Bhavuk
_______________________________________________
aspectj-users mailing list
aspectj-users< at >eclipse.org
https://dev.eclipse.org/mailman/listinfo/aspectj-users

Re: Issue with WAR file

Jean Andre — 2012-05-22T17:00:11

Thank you Andy for your answer. Well, when we work under IDE, everything 
is smooth enough to avoid developpers to take care about many details. The 
WAR or even an EAR projet can be converted to an AspectJ project and 
something handles correctly the problem of compiling and weaving the 
aspects. WAR and EAR files are not more than specialized JAR file with 
well-known conventions and rules. It is why we have expected similar 
behavior with IAJC task but we have to recognize we have surrestimated the 
capabilities of this specialized task. We have to returned back to the 
starting point by following your recommended approach.

Best regards,

JA.





De :    Andy Clement <andrew.clement< at >gmail.com>
A :     aspectj-users< at >eclipse.org
Date :  2012-05-22 11:56
Objet : Re: [aspectj-users] Issue with WAR file
Envoyé par :    aspectj-users-bounces< at >eclipse.org



Hi,

This is related to the other war discussion we had - AspectJ has no
knowledge beyond understanding a jar.  Similar to how javac has no
understanding either.

Of course, this doesn't mean we can't add it.  But the recommended
approach at the moment is to use the other tools available to do
pre-processing (unpacking) and post-processing (repacking) - tools
like the ant jar task.  How about producing output to some other jar
and then using another ant task that runs after the compile to merge
the contents back into the right place in your war file?

I'm a bit surprised things behaved at all given that the input was a
war file - I'd have expected the leading directories on the front of
the package names to have given the weaver problems.

cheers,
Andy

On 18 May 2012 09:50, Jean Andre <Jean.Andre< at >intact.net> wrote:
solved
files.
-
both
as
folder
put
"ext/cglib-nodep-2.2.2.jar"/>
"ext/commons-lang-2.4.jar"/>
"ext/cssparser-0.9.6.jar"/>
"ext/hibernate-3.3.2.jar"/>
"ext/ojdbc14-10.2.0.4.jar"/>
"ext/pop-api-official.jar"/>
"ext/slf4j-api-1.6.4.jar"/>
_______________________________________________
aspectj-users mailing list
aspectj-users< at >eclipse.org
https://dev.eclipse.org/mailman/listinfo/aspectj-users

_______________________________________________
aspectj-users mailing list
aspectj-users< at >eclipse.org
https://dev.eclipse.org/mailman/listinfo/aspectj-users

Re: Fwd: trigger all calls/sets from an annotated parameter within a method

Andy Clement — 2012-05-22T16:29:34

Hi,

I'm afraid you can't do that (easily) - we don't know/preserve enough
about local variables.  The slightly messy way to do it would be:

At the execution joinpoint for the method, remember which parameter
objects are annotated, some kind of sequence of these (for different
arg positions):
before(B b): execution(* *(< at >MyAnno (*),..)) && args(b) // arg in first
position
before(B b): execution(* *(*,< at >MyAnno (*),..)) && args(b) // arg in
second position
remember 'b'

Then, when call/set is made within that code, look at the object upon
which the method is being called (target) and check if it was an
annotated one.
before(B b):  (call(* *(..)) || set(* *)) && target(b) {
  if (b is in my list) {
    System.out.println("triggered");
  }
}

Using some kind of stack to push (on entry)/pop (on exit) the
contextual information you are keeping about the method.

cheers,
Andy

On 21 May 2012 08:50, Frederick Egli <frederick.egli< at >gmail.com> wrote:

Re: Accessing protected methods of parent class from within an aspect in another package

Andy Clement — 2012-05-22T16:18:08

Hi Sina,

That should work, the use of 'privileged' should cause generation of
an accessor method that can then be used by the aspect.

here is my sample:

==== 8< ==== Parent.java
package com.somewhereelse;

public class Parent {

protected void foo() {
System.out.println("foo!");
}
}
===== 8< ====
===== 8< ==== Child.java
package com;

import com.somewhereelse.Parent;

public class Child extends Parent {

public static void main(String[] args) {
new Child().m();
}

public void m() {

}
}
===== 8< ==== Overthere.aj
package xxx;
import com.Child;

privileged aspect Overthere {

before(Child c): execution(* Child.m(..)) && this(c) {
c.foo();
}
}
===== 8< ====


Join point 'method-execution(void com.Child.m())' in Type 'com.Child'
(Child.java:11) advised by before advice from 'xxx.Overthere'
(Overthere.aj:6)

foo!

Here is the accessor in the Parent class:

Compiled from "Parent.java"
public class com.somewhereelse.Parent extends java.lang.Object{
    public com.somewhereelse.Parent();
    protected void foo();
    public void ajc$privMethod$xxx_Overthere$com_somewhereelse_Parent$foo();
}

So what is different about your configuration from mine?

cheers,
Andy

On 21 May 2012 09:25, Sina <my.linked.account< at >googlemail.com> wrote:

Re: Issue with WAR file

Andy Clement — 2012-05-22T15:55:58

Hi,

This is related to the other war discussion we had - AspectJ has no
knowledge beyond understanding a jar.  Similar to how javac has no
understanding either.

Of course, this doesn't mean we can't add it.  But the recommended
approach at the moment is to use the other tools available to do
pre-processing (unpacking) and post-processing (repacking) - tools
like the ant jar task.  How about producing output to some other jar
and then using another ant task that runs after the compile to merge
the contents back into the right place in your war file?

I'm a bit surprised things behaved at all given that the input was a
war file - I'd have expected the leading directories on the front of
the package names to have given the weaver problems.

cheers,
Andy

On 18 May 2012 09:50, Jean Andre <Jean.Andre< at >intact.net> wrote:

Accessing protected methods of parent class fromwithin an aspect in another package

Sina — 2012-05-21T16:25:12

Hi there.

I have Parent class and a child one. The parent class has some protected  methods.
My pointcut works on methods of the child class. The problem is that I want to access protected methods of the parent in my Aspect, but they are not 
visible from within my Aspect.

All these 3 classes (Parent, Child, Aspect) are in different packages. 

I read here http://dev.eclipse.org/mhonarc/lists/aspectj-users/msg03270.html
that using privileged  modifier will solve the problem but it does not work for me.
Any idea??

Sina_______________________________________________
aspectj-users mailing list
aspectj-users< at >eclipse.org
https://dev.eclipse.org/mailman/listinfo/aspectj-users

Fwd: trigger all calls/sets from an annotatedparameter within a method

Frederick Egli — 2012-05-21T15:50:21

Hi all,

I'm trying to trigger all calls/sets from an annotated parameter within a
method. Consider the following example:

public class A {

    public void foo(< at >MyAnno B b1, B b2){
        b1.bar();         //this should trigger
        b1.field = 42;  //this should trigger

        b2.bar();         //should not trigger
        b2.field = 42;  //should not trigger
    }
}

public class B {
    public int field;
    public void bar() {    }
}

< at >Retention(RetentionPolicy.RUNTIME)
< at >Target(ElementType.PARAMETER)
public < at >interface MyAnno {
}


So far I have the following aspect. But of course this triggers all calls
and sets from all method parameters.

< at >Aspect
public class MyAspect {
    < at >Before("cflowbelow(execution(* *.*(..,< at >MyAnno (*),..))) && (call(*
*(..)) || set(* *)) && !within(MyAspect)")
    public void belowAdvice() {
        System.out.println("triggered");
    }
}

Is there any way to only trigger the calls and sets from the annotated (in
my case b1) parameter within a method (foo())?


Thanks in advance!

Fred
_______________________________________________
aspectj-users mailing list
aspectj-users< at >eclipse.org
https://dev.eclipse.org/mailman/listinfo/aspectj-users

Issue with WAR file

Jean Andre — 2012-05-18T16:50:08

Hello,

We have a problem and we tried to figure out if this problem can be solved 
by iajc. We have WAR file which contains the source and the < at >aspectJ 
files.
We use the ANT command  <iajc> inpath="my_original_War" -outJar="MyWar" - 
classpath="The full list of jar"

The weaven did not report any error, everything seems fine. BUT, when we 
tried to run the WAR file inside the EAR, it fails. We compared the both 
WAR and the  WAR produced by the Weaver did not have the same structure as 
the original WAR.

The WAR has an additional folder starting from the root : 
com\companyName\projectName\.... In fact, the weaver have put the src 
folder at the root of the WAR file instead of keeping the classes inside 
WEB-INF\classes. It it like having duplicated classes, with and without 
veaven.

For sure, it is not normal ?
Iis there a way to specify with IAJC  the destination folder where to put 
the weaven classes inside the WAR (I think, there are weaven classes ?)

What are our alternatives ?

Best regards and thank you for your quick feedback.

JA.

=============================================
The exact command for the weaver
=============================================

           <iajc inpath="Web_origine.war"
                 outjar="Web.war"
                 showWeaveInfo="false"> 
                <classpath>
                        <pathelement path = "ext/aspectjrt.jar"/>
                        <pathelement path = "ext/javax.faces.jar"/>
                        <pathelement path = 
"ext/annotations-4.2.0.Final.jar"/>
                        <pathelement path = "ext/antlr-2.7.6.jar"/>
                        <pathelement path = "ext/cglib-nodep-2.2.2.jar"/>
                        <pathelement path = 
"ext/cof-service-api-official.jar"/>
                        <pathelement path = 
"ext/cof-service-web-official.jar"/>
                        <pathelement path = 
"ext/common-api-core-official.jar"/>
                        <pathelement path = 
"ext/common-api-dm-official.jar"/>
                        <pathelement path = 
"ext/common-api-email-official.jar"/>
                        <pathelement path = 
"ext/common-api-il-services-official.jar"/>
                        <pathelement path = 
"ext/common-api-java-services-official.jar"/>
                        <pathelement path = 
"ext/common-api-moneris-official.jar"/>
                        <pathelement path = 
"ext/common-api-pega-services-official.jar"/>
                        <pathelement path = 
"ext/common-api-web-official.jar"/>
                        <pathelement path = 
"ext/common-api-web-struts-official.jar"/>
                        <pathelement path = 
"ext/common-api-web-tags-official.jar"/>
                        <pathelement path = 
"ext/common-api-wi-official.jar"/>
                        <pathelement path = "ext/commons-lang-2.4.jar"/>
                        <pathelement path = 
"ext/commons-logging-1.1.1.jar"/>
                        <pathelement path = 
"ext/commons-validator-1.4.0.jar"/>
                        <pathelement path = "ext/cssparser-0.9.6.jar"/>
                        <pathelement path = "ext/dom4j-1.6.1.jar"/>
                        <pathelement path = "ext/guava-11.0.1.jar"/>
                        <pathelement path = "ext/hibernate-3.3.2.jar"/>
                        <pathelement path = 
"ext/hibernate-annotations-3.4.0.jar"/>
                        <pathelement path = 
"ext/hibernate-commons-annotations-3.4.0.jar"/>
                        <pathelement path = 
"ext/hibernate-entitymanager-3.4.0.jar"/>
                        <pathelement path = 
"ext/hibernate-validator-4.2.0.Final.jar"/> 
                        <pathelement path = "ext/junit-4.10.jar"/>
                        <pathelement path = "ext/log4j-1.2.16.jar"/>
                        <pathelement path = "ext/ojdbc14-10.2.0.4.jar"/>
                        <pathelement path = 
"ext/org.springframework.asm-3.0.6.RELEASE.jar"/>
                        <pathelement path = 
"ext/org.springframework.beans-3.0.6.RELEASE.jar"/>
                        <pathelement path = 
"ext/org.springframework.context-3.0.6.RELEASE.jar"/>
                        <pathelement path = 
"ext/org.springframework.core-3.0.6.RELEASE.jar"/>
                        <pathelement path = 
"ext/org.springframework.expression-3.0.6.RELEASE.jar"/>
                        <pathelement path = 
"ext/org.springframework.jdbc-3.0.6.RELEASE.jar"/>
                        <pathelement path = 
"ext/org.springframework.orm-3.0.6.RELEASE.jar"/>
                        <pathelement path = 
"ext/org.springframework.transaction-3.0.6.RELEASE.jar"/>
                        <pathelement path = 
"ext/org.springframework.web-3.0.6.RELEASE.jar"/>
                        <pathelement path = "ext/pop-api-official.jar"/>
                        <pathelement path = 
"ext/pop-services-official.jar"/>
                        <pathelement path = 
"ext/richfaces-components-api-4.2.0.Final.jar"/>
                        <pathelement path = 
"ext/richfaces-components-ui-4.2.0.Final.jar"/>
                        <pathelement path = 
"ext/richfaces-core-api-4.2.0.Final.jar"/>
                        <pathelement path = 
"ext/richfaces-core-impl-4.2.0.Final.jar"/>
                        <pathelement path = "ext/sac-1.3.jar"/>
                        <pathelement path = "ext/slf4j-api-1.6.4.jar"/>
                        <pathelement path = 
"ext/slf4j-log4j12-1.6.4.jar"/>
                        <pathelement path = "ext/j2ee.jar"/>
                        <pathelement path = 
"ext/commons-collections-3.2.1.jar"/>
                        <pathelement path = 
"ext/org.springframework.aop-3.0.6.RELEASE.jar"/> 
                </classpath>

           </iajc>_______________________________________________
aspectj-users mailing list
aspectj-users< at >eclipse.org
https://dev.eclipse.org/mailman/listinfo/aspectj-users

Re: Aspect in an EAR file

Andy Clement — 2012-05-18T16:06:27

Yes, James is right, load time weaving can do the kinds of thing you
want to do but it will incur you a startup hit.

Using a javaagent each classloader in the system gets a weaver and
will use any aop.xml files it can 'reach' through its classpath to
configure itself.  So if one jar on that classpath defines an aop.xml
file containing an aspect, then that weaver associated with the
classloader will apply the aspect to everything loaded through that
same classloader.

Weaving will be about the same speed regardless of when you choose to
do it (compile time, post compile time, load time) but:
- load time weaving will weave things as they are loaded.  This may
sound obvious, but this does mean if something isn't loaded on a
particular run of the application then you won't weave it or incur the
cost of weaving it.  Whereas compile time weaving will weave
everything.
- beyond speed there is a memory overhead for a weaver that you will
incur.  But having said that we are including some basic caching in
the next version that will mean you can weave on first startup,
automatically store those woven entities, and then use the stored
cached versions on the subsequent starts. (reducing the memory and
performance impact).

Andy

On 18 May 2012 04:30, James Black <planiturthian< at >gmail.com> wrote:

Re: Advice did not match

Andy Clement — 2012-05-18T15:55:37

I might need to see where you are applying it?

I created this tiny thing and your aspect worked just fine:

class Foo {
< at >Updates void foo(String s) {}
}

The advice did not match indicates that during the build of the code
containing the aspect it didn't find anything to apply it to.  If that
is because you are building it into an aspect library to use later,
you can just ignore the warning.  If you expected it to match
something though - I'd need to see what it isn't matching.  If it
isn't matching you can break it into smaller pieces to determine which
piece is causing the problem.

cheers
Andy

On 17 May 2012 11:40, hart404 <hart404< at >gmail.com> wrote:

Re: Aspect in an EAR file

James Black — 2012-05-18T11:30:44

I don't see why you can't do this, but you will take a performance hit as
it weaves at run time.

It is best if you can apply the aspects during compilation, but if that
isn't an option then run time is your other option.
On May 18, 2012 6:10 AM, "jbolger" <john.bolger< at >gmail.com> wrote:

_______________________________________________
aspectj-users mailing list
aspectj-users< at >eclipse.org
https://dev.eclipse.org/mailman/listinfo/aspectj-users

Aspect in an EAR file

jbolger — 2012-05-18T10:09:40

Hi,

Can you tell me if I can configure an aspect within an EAR to apply advice
against all code (including jars and wars) within the EAR and it's lib
(without having to define the aspect in each of the wars)?

Also in this case, which weaving style is most appropriate? Is it even
possible to perform compile/post-compile time weaving for an EAR when the
jars / wars it includes have already been built?

And finally, is any weaving style more performant than the other?

Thanks in advance,
John

--
View this message in context: http://aspectj.2085585.n4.nabble.com/Aspect-in-an-EAR-file-tp4644307.html
Sent from the AspectJ - users mailing list archive at Nabble.com.

Advice did not match

hart404 — 2012-05-17T18:40:00

Can anyone tell me why I'm getting "Advice did not match" on the after advice
in the following code, please?

package edu.uat.cs2011.observerpattern;

import java.util.ArrayList;
import java.util.List;

public aspect ObservableAspect {

declare parents: hasmethod(< at >Updates * *.*(..)) implements Observable;

private List<Observer> observers = new ArrayList<Observer>();

public void addObserver(Observer observer) {
observers.add(observer);
}

public void removeObserver(Observer observer) {
observers.remove(observer);
}

public void notifyObservers() {
for (Observer observer : observers) {
observer.update();
}
}

public pointcut mutations(Observable observable) : execution(< at >Updates *
*.*(..)) && this(observable);

after(Observable observable) : mutations(observable) {
for (Observer observer : observers) {
observer.update();
}
}

}

--
View this message in context: http://aspectj.2085585.n4.nabble.com/Advice-did-not-match-tp4643399.html
Sent from the AspectJ - users mailing list archive at Nabble.com.

Re: Corbetura + LTW

Andy Clement — 2012-05-17T17:45:13

Sorry I didn't reply sooner - at a conference right now.

Yes, we can work with cobertura but you have to be careful on ordering
when running it and AJ together.  There is at least one open bug in
this area:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=325362

cheers,
Andy

On 16 May 2012 08:09, Steve Ash <stevemash< at >gmail.com> wrote:

Re: Corbetura + LTW

Steve Ash — 2012-05-16T15:09:36

Just for anyone that runs across this in the googles-- this was just
me being stupid.  I had not cleaned the workspace and the class files
that corbetura was instrumenting were already woven at compile time.
So compile time ajc -> corbetura instrumentation -> LTW caused this
blow up.  You can see the ajc stuff already in the class file that I
attached to my previous message.

Once I cleaned and re-ran letting javac build the original class files
then having corbetura instrument those and do LTW on the corbetura
classes  --- everything worked fine.

So to answer my original question -- it appears that with corbetura
2.5.1 and AspectJ Weaver 1.7.0.M1 -- LTW can weave into corbetura
instrumented classes.

Steve

On Tue, May 15, 2012 at 11:45 AM, Steve Ash <stevemash< at >gmail.com> wrote:

Corbetura + LTW

Steve Ash — 2012-05-15T16:45:52

I have run across a number of things on google so I know that this has
come up in the past, but I couldn't get a clear answer.  So sorry for
the re-post.

I am trying to use corbetura + aspectJ LTW and the weaver is blowing
up on the corbetura instrumented classes.  I am trying to dig in to
the class file to see if I can spot the exact problem, but wanted to
post and see if the expectation was that this would work or not.  I am
using the 1.7.0.M1 weaver and this is the stack trace:

SEVERE: com/argodata/empi/database/util/InsertIfMissingEntityLoader
org.aspectj.apache.bcel.classfile.ClassFormatException: File:
'com.argodata.empi.database.util.InsertIfMissingEntityLoader': Invalid
byte tag in constant pool: 0
        at org.aspectj.apache.bcel.classfile.ClassParser.readConstantPool(ClassParser.java:192)
        at org.aspectj.apache.bcel.classfile.ClassParser.parse(ClassParser.java:131)
        at org.aspectj.weaver.bcel.Utility.makeJavaClass(Utility.java:467)
        at org.aspectj.weaver.bcel.BcelWeaver.processReweavableStateIfPresent(BcelWeaver.java:1387)
        at org.aspectj.weaver.bcel.BcelWeaver.weave(BcelWeaver.java:1097)
        at org.aspectj.weaver.tools.WeavingAdaptor.getWovenBytes(WeavingAdaptor.java:472)
        at org.aspectj.weaver.tools.WeavingAdaptor.weaveClass(WeavingAdaptor.java:323)
        at org.aspectj.weaver.loadtime.Aj.preProcess(Aj.java:99)
        at org.aspectj.weaver.loadtime.ClassPreProcessorAgentAdapter.transform(ClassPreProcessorAgentAdapter.java:54)

I have a few spring-aspects < at >Transactional annotations in there
weaving the before, after, and throwing advice for
TransactionalAspect.

I have attached the cobetura instrumented class file to this message
if that helps at all.

But I guess the main question is: should this work?  Or is this a
known limitation?

Thanks,

Steve
_______________________________________________
aspectj-users mailing list
aspectj-users< at >eclipse.org
https://dev.eclipse.org/mailman/listinfo/aspectj-users

Re: How to specify classpath inside a WAR for theweaver ?

Jean Andre — 2012-05-15T16:00:01

It is what I did : https://bugs.eclipse.org/bugs/show_bug.cgi?id=379530

Understood - Surfing on the net about having a such thing, there is a real
need and many users are facing to this problem.
It will increase the interoperability between the java community and the
tools will be more friendly for us.

In our case, the persons who are developping and using AspectJ are not the
same as the persons who are building the project to deploy the ear. The
competency is not the same. Building/Weaving a project should be "smooth"
enough for this king of persons.

Best regards,

JA.

De : Andy Clement <andrew.clement< at >gmail.com>
A : aspectj-users< at >eclipse.org
Date : 2012-05-14 23:29
Objet : Re: [aspectj-users] How to specify classpath inside a WAR for the
weaver ?
Envoyé par : aspectj-users-bounces< at >eclipse.org

Hi,

I'm afraid that right now you can't tell AspectJ to look at jars
within jars. It is probably not toooo difficult to implement though.
Might be worth raising an enhancement request:

https://bugs.eclipse.org/bugs/enter_bug.cgi?product=AspectJ

In the meantime you'll have to extract those into somewhere, but
unfortunately you will need to specify them all on a classpath. You
can turn off that error (or dial it down to a warning) because it is
an Xlint, but it may mean it is not be weaving what you would like it
to (as it couldn't complete its analysis).

cheers,
Andy

On 14 May 2012 14:30, Jean Andre <Jean.Andre< at >intact.net> wrote:
F:\cruisecontrol-service-4\artifacts\MyApplication_01_SYSINT\20120509153156\MyApplication-1.0.0.49\CrmWeb_origine.war:0::0
150
_______________________________________________
aspectj-users mailing list
aspectj-users< at >eclipse.org
https://dev.eclipse.org/mailman/listinfo/aspectj-users

_______________________________________________
aspectj-users mailing list
aspectj-users< at >eclipse.org
https://dev.eclipse.org/mailman/listinfo/aspectj-users

Re: DeclareAnnotation Warnings

CRANFORD, CHRIS — 2012-05-15T15:57:26

From what I can tell from adjusting the build.xml for ANT, I removed the
following line and the warnings vanished.

<aspectpath refid="compile.classpath"/>

 

Sorry for the confusion.

 

From: aspectj-users-bounces< at >eclipse.org
[mailto:aspectj-users-bounces< at >eclipse.org] On Behalf Of CRANFORD, CHRIS
Sent: Tuesday, May 15, 2012 10:35 AM
To: aspectj-users< at >eclipse.org
Subject: [aspectj-users] DeclareAnnotation Warnings

 

In a Spring project, the ANT build script shows the following warnings
during the IAJC task:

<Unknown> [warning] Found < at >DeclareAnnotation while current release does
not support it (see 'org.aspectj.weaver.bcel.AtAjAttributes')

 

I am using the AspectJ 1.6.12 runtime libraries.  

 

How can I avoid/prevent these warnings?
_______________________________________________
aspectj-users mailing list
aspectj-users< at >eclipse.org
https://dev.eclipse.org/mailman/listinfo/aspectj-users