http://permalink.gmane.org/gmane.comp.java.aop.aspectj.general hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.comp.java.aop.aspectj.general/7282 <pre>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 -&gt; corbetura instrumentation -&gt; 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 &lt;stevemash&lt; at &gt;gmail.com&gt; wrote: </pre> Steve Ash 2012-05-16T15:09:36 http://permalink.gmane.org/gmane.comp.java.aop.aspectj.general/7281 <pre>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.pro</pre> Steve Ash 2012-05-15T16:45:52 http://permalink.gmane.org/gmane.comp.java.aop.aspectj.general/7280 <pre>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 &lt;andrew.clement&lt; at &gt;gmail.com&gt; A : aspectj-users&lt; at &gt;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&lt; at &gt;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:</pre> Jean Andre 2012-05-15T16:00:01 http://permalink.gmane.org/gmane.comp.java.aop.aspectj.general/7279 <pre>From what I can tell from adjusting the build.xml for ANT, I removed the following line and the warnings vanished. &lt;aspectpath refid="compile.classpath"/&gt; Sorry for the confusion. From: aspectj-users-bounces&lt; at &gt;eclipse.org [mailto:aspectj-users-bounces&lt; at &gt;eclipse.org] On Behalf Of CRANFORD, CHRIS Sent: Tuesday, May 15, 2012 10:35 AM To: aspectj-users&lt; at &gt;eclipse.org Subject: [aspectj-users] DeclareAnnotation Warnings In a Spring project, the ANT build script shows the following warnings during the IAJC task: &lt;Unknown&gt; [warning] Found &lt; at &gt;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&lt; at &gt;eclipse.org https://dev.eclipse.org/mailman/listinfo/aspectj-users </pre> CRANFORD, CHRIS 2012-05-15T15:57:26 http://permalink.gmane.org/gmane.comp.java.aop.aspectj.general/7278 <pre>In a Spring project, the ANT build script shows the following warnings during the IAJC task: &lt;Unknown&gt; [warning] Found &lt; at &gt;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&lt; at &gt;eclipse.org https://dev.eclipse.org/mailman/listinfo/aspectj-users </pre> CRANFORD, CHRIS 2012-05-15T15:34:35 http://permalink.gmane.org/gmane.comp.java.aop.aspectj.general/7277 <pre>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 &lt;Jean.Andre&lt; at &gt;intact.net&gt; wrote: </pre> Andy Clement 2012-05-15T03:29:35 http://permalink.gmane.org/gmane.comp.java.aop.aspectj.general/7276 <pre>Hello, We got many, many errors like this : [iajc] when batch building BuildConfig[null] #Files=0 AopXmls=#0 [iajc] [Xlint:cantFindType] [iajc] [error 55]: error at (no source information available) [iajc] F:\cruisecontrol-service-4\artifacts\MyApplication_01_SYSINT\20120509153156\MyApplication-1.0.0.49\CrmWeb_origine.war :0::0 can't determine implemented interfaces of missing type javax.validation.ConstraintValidator [iajc] when weaving type com.intact.crm.web.validator.impl.PostalCodeValidator [iajc] when weaving classes [iajc] when weaving Looking for on Internet, we found that we have a classpath problem. We use ANT with the tag (iajc) - something like this: iajc -inpath CrmWeb_origine.war -outJar CrmWeb.war -showWeaveInfo As you can notice, we use a WAR, not a jar file and a WAR as WEB-INF/lib which contains all the necessary libraries needed by the application. However, the weaver does not find those libraries as we got more that 150 errors for m</pre> Jean Andre 2012-05-14T21:30:39 http://permalink.gmane.org/gmane.comp.java.aop.aspectj.general/7275 <pre>After closer examination it looks that this only happen, if the parent class is annotated with javax.persistence.MappedSuperclass ... If I use a class that is a simple entity things work as expected. Am Donnerstag, den 10.05.2012, 11:15 +0200 schrieb Arne Ploese: </pre> Arne Ploese 2012-05-10T12:44:39 http://permalink.gmane.org/gmane.comp.java.aop.aspectj.general/7274 <pre>Hi, I have annotated fields of an entity to track the change of that property. If I run this plain with loadtime weaving the pointcut fires. [code] &lt; at &gt;Pointcut("set(&lt; at &gt;AuditableProperty * *.*)") public void setter() {}; [/code] Adding JPA (Eclipselink), setting fields in classes that are database entities, the pointcut does not fire anymore. Any hints whats going on? Arne </pre> Arne Ploese 2012-05-10T09:15:38 http://permalink.gmane.org/gmane.comp.java.aop.aspectj.general/7273 <pre>There are 3 paths to think about with AspectJ when binary weaving: Regular CLASSPATH - this is solely used to resolve type references. Aspects are not discovered on it and classes on it are not woven into. ASPECTPATH - this is actively searched for aspects. The classes on aspectpath are not woven into. INPATH - this is actively searched for aspects *and* the classes on it are woven into. If you have just one jar and it contains your aspects, just use inpath. Here is an example: --- A.java --- import org.aspectj.lang.annotation.*; &lt; at &gt;Aspect public class A { &lt; at &gt;Before("staticinitialization(!A)") public void beforeAdvice() {System.out.println("advice");} } --- C.java public class C { public static void main(String []argv) {} } --- javac A.java -d out javac C.java -d out cd out jar -cvMf stuff.jar *.class ajc -inpath stuff.jar -outjar wovenstuff.jar -showWeaveInfo Join point 'staticinitialization(void C.&lt;clinit&gt;())' in Type 'C' (C.java) advised by before advice from 'A' (stuff.jar!A.class(from A.java</pre> Andy Clement 2012-05-09T16:23:57 http://permalink.gmane.org/gmane.comp.java.aop.aspectj.general/7272 <pre>Thank you very much for your answer - A last question, is it necessary to have 2 separated and distincts files for binary weaving, because as you have seen with the Worbench, the aspectJ classes and the source code are into the same project (WAR) and ultimely inside the same EAR. So in our case it would be : ajc -aspectpath workbench.jar -inpath workbench.jar -outjar workbench2.jar Thank you in advance - JA De : Andy Clement &lt;andrew.clement&lt; at &gt;gmail.com&gt; A : aspectj-users&lt; at &gt;eclipse.org Date : 2012-05-08 20:52 Objet : Re: [aspectj-users] Differences and impacts between .aj classes vs Java class with AspectJ annotation Envoyé par : aspectj-users-bounces&lt; at &gt;eclipse.org Hi, The only docs we really have are more on how-to-use-it rather than the trade offs: http://www.eclipse.org/aspectj/doc/released/adk15notebook/ataspectj.html The two styles are called code-style (using the real AspectJ keywords) and annotation-style (using the annotations). compiler ? When you use the annotation style, t</pre> Jean Andre 2012-05-09T16:00:05 http://permalink.gmane.org/gmane.comp.java.aop.aspectj.general/7271 <pre>I can confirm there is no encryption stuff in AspectJ and it doesn't use any other encryption libraries. It only really has 2 dependencies: asm bytecode toolkit and the JDT compiler. Andy On 8 May 2012 23:24, Vandy &lt;vandyv&lt; at &gt;gmail.com&gt; wrote: </pre> Andy Clement 2012-05-09T14:57:17 http://permalink.gmane.org/gmane.comp.java.aop.aspectj.general/7270 <pre>Encryption built into aspectj wouldn't make sense, so no I don't see where it would be included. You can make aspects that do encrypt though, but for transferring software that may be export controlled I think just aspect should be safe, but IANAL. On May 9, 2012 2:25 AM, "Vandy" &lt;vandyv&lt; at &gt;gmail.com&gt; wrote: _______________________________________________ aspectj-users mailing list aspectj-users&lt; at &gt;eclipse.org https://dev.eclipse.org/mailman/listinfo/aspectj-users </pre> James Black 2012-05-09T11:53:57 http://permalink.gmane.org/gmane.comp.java.aop.aspectj.general/7269 <pre>Hello, I have not been able to find answer to my questions by checking the wikis, mailing list archives, etc. Thus, I'm posting my questions here. I'm basically trying to find out if there is any ECCN code defined for AspectJ itself. 1) Does AspectJ use/include any encrpytion? 2) If yes, does it have ECCN code assigned? All possible answers are much appreciated, thanks in advance. -Vandana _______________________________________________ aspectj-users mailing list aspectj-users&lt; at &gt;eclipse.org https://dev.eclipse.org/mailman/listinfo/aspectj-users </pre> Vandy 2012-05-09T06:24:54 http://permalink.gmane.org/gmane.comp.java.aop.aspectj.general/7268 <pre>Hi, The only docs we really have are more on how-to-use-it rather than the trade offs: http://www.eclipse.org/aspectj/doc/released/adk15notebook/ataspectj.html The two styles are called code-style (using the real AspectJ keywords) and annotation-style (using the annotations). When you use the annotation style, the code remains 'pure java' and so you can build it with javac. However, this does not cause the weaver to be invoked, so the aspects are only built they are not applied/woven. The AspectJ weaver is a bytecode based weaver. Regardless of which style you use (code or annotation), they will be compiled to binary form before the weaver applies them. So, basically, I'm saying that choosing annotation style still needs the weaver to be run at some point, and there are two options: - after running javac to build the source, do a binary weave with the AspectJ compiler: ajc -aspectpath compiledAspects.jar -inpath codeToBeWoven.jar -outjar wovenCode.jar - use loadtime weaving, the weaver will run as </pre> Andy Clement 2012-05-09T00:51:56 http://permalink.gmane.org/gmane.comp.java.aop.aspectj.general/7267 <pre>Hello, I would like to clarify the difference and the impact between using native AspectJ language versus the "same" Aspect coded by using Java classes and Annotations from the point of view of building an application and runtime dependencies. When we use &lt; at &gt;annotations, do we need to compile with the AspectJ compiler ? or the Javac compiler call the AspectJ compiler ? When a project is compile with the aspectJ compiler, do we need a runtime ? and by Annotation? It seems that using annotation means Load-time weaving and it requires 2 jars (aspectJ runtime and the weaver). It that true ? Where to find a clear explanation between these 2 ways of coding the aspects ? Regards - JA _______________________________________________ aspectj-users mailing list aspectj-users&lt; at &gt;eclipse.org https://dev.eclipse.org/mailman/listinfo/aspectj-users </pre> Jean Andre 2012-05-08T21:00:36 http://permalink.gmane.org/gmane.comp.java.aop.aspectj.general/7266 <pre>Thanks, the current development snapshot (DEVELOPMENT-20120418141500) solves this issue. Arne Am Freitag, den 04.05.2012, 11:25 -0700 schrieb Andy Clement: </pre> Arne Ploese 2012-05-05T06:52:58 http://permalink.gmane.org/gmane.comp.java.aop.aspectj.general/7265 <pre>Are you using a recent AspectJ dev build? or? You can try running with "-XX:-UseSplitVerifier" on Java7 which will tell us if it is purely a stackmap issue or something more serious. The stackmaps are computed either by the JDT compiler or by asm, depending on whether the file in question was woven or not. Do you know if it was woven? Andy On 4 May 2012 02:39, Arne Ploese &lt;aploese&lt; at &gt;gmx.de&gt; wrote: </pre> Andy Clement 2012-05-04T18:25:00 http://permalink.gmane.org/gmane.comp.java.aop.aspectj.general/7264 <pre>Hi, I got this stacktrace running some junit tests: [code] saveUser(br.org.scadabr.papaya.dao.jpa.UserDaoTest) Time elapsed: 1.291 sec &lt;&lt;&lt; ERROR! java.lang.VerifyError: Stack map does not match the one at exception handler 39 in method br.org.scadabr.papaya.dao.jpa.UserDao.deleteUser(Lbr/org/scadabr/papaya/vo/User;)V at offset 31 at java.lang.Class.getDeclaredConstructors0(Native Method) at java.lang.Class.privateGetDeclaredConstructors(Class.java:2404) at java.lang.Class.getDeclaredConstructors(Class.java:1853) at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.determineCandidateConstructors(AutowiredAnnotationBeanPostProcessor.java:229) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.determineConstructorsFromBeanPostProcessors(AbstractAutowireCapableBeanFactory.java:962) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:935) at org.springframe</pre> Arne Ploese 2012-05-04T09:39:39 http://permalink.gmane.org/gmane.comp.java.aop.aspectj.general/7263 <pre>Done ! Bug 378396 : https://bugs.eclipse.org/bugs/show_bug.cgi?id=378396 Best regards, J. De : Andrew Eisenberg &lt;andrew&lt; at &gt;eisenberg.as&gt; A : Jean Andre &lt;Jean.Andre&lt; at &gt;intact.net&gt; Cc : aspectj-users&lt; at &gt;eclipse.org, Andy Clement &lt;andrew.clement&lt; at &gt;gmail.com&gt; Date : 2012-05-03 12:03 Objet : Re: [aspectj-users] How do we declare multilple class in &lt; at &gt;DeclareParents ? Envoyé par : andrew.eisenberg&lt; at &gt;gmail.com Hi Jean, impact aspect. I tried to reproduce this problem naively, but could not. It would be helpful if you could attach a simple project that reproduces the problem and I will take a look at it. Raising a bug would also be good. Thanks. _______________________________________________ aspectj-users mailing list aspectj-users&lt; at &gt;eclipse.org https://dev.eclipse.org/mailman/listinfo/aspectj-users </pre> Jean Andre 2012-05-03T18:00:14 http://permalink.gmane.org/gmane.comp.java.aop.aspectj.general/7262 <pre>It is what I'm doing presently- I've also reported an another bug : Bug 378361 - https://bugs.eclipse.org/bugs/show_bug.cgi?id=378361 Regards, De : Andrew Eisenberg &lt;andrew&lt; at &gt;eisenberg.as&gt; A : Jean Andre &lt;Jean.Andre&lt; at &gt;intact.net&gt; Cc : aspectj-users&lt; at &gt;eclipse.org, Andy Clement &lt;andrew.clement&lt; at &gt;gmail.com&gt; Date : 2012-05-03 12:03 Objet : Re: [aspectj-users] How do we declare multilple class in &lt; at &gt;DeclareParents ? Envoyé par : andrew.eisenberg&lt; at &gt;gmail.com Hi Jean, impact aspect. I tried to reproduce this problem naively, but could not. It would be helpful if you could attach a simple project that reproduces the problem and I will take a look at it. Raising a bug would also be good. Thanks. _______________________________________________ aspectj-users mailing list aspectj-users&lt; at &gt;eclipse.org https://dev.eclipse.org/mailman/listinfo/aspectj-users </pre> Jean Andre 2012-05-03T16:10:02 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.java.aop.aspectj.general