http://blog.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://comments.gmane.org/gmane.comp.java.aop.aspectj.general/7311 <pre>Hi all, Newbie here. I just need a sanity check here on LTW. Here is what I think ought to happen Given a properly constructed aspect and a properly configured and placed aop.xml, I can run any java program which has been compiled by regular old javac and have LTW apply aspects against it at runtime. To achieve the above I have to do the all and only the following (aside from compiling the aspect with ajc and writing aop.xml): make certain that the classpath for regular old java program includes: jar://&lt;path to aspectJ&gt;aspectj1.6/lib/aspectjrt.jar!/ &lt;path to compiled aspects&gt; &lt;path to aop.xml containing META-INF folder&gt; and for VM options include: -Djava.system.class.loader=org.aspectj.weaver.loadtime.WeavingURLClassLoader That's pretty much it. How am I mistaken? What am I doing wrong? Thank you! </pre> trhouse 2012-05-25T21:43:07 http://comments.gmane.org/gmane.comp.java.aop.aspectj.general/7307 <pre>Hi I have a very simple point cut, but the method return does not seem to be intercepted. Is the syntax wrong ? Thanks ! &lt; at &gt;Pointcut("within(com.mycom.mypack.myclass)")                 public void withinMyPackage() {}   &lt; at &gt;AfterReturning(pointcut = "execution(public static * myMethod ( .. ))  " +        "  &amp;&amp; withinMyPackage() " ,         returning = "myResult"         ) public void provideAdviseAfterReturning(   MyType myResult    , JoinPoint jp ) {          // do something with returned results   }_______________________________________________ aspectj-users mailing list aspectj-users&lt; at &gt;eclipse.org https://dev.eclipse.org/mailman/listinfo/aspectj-users </pre> Srinivas S Tamvada 2012-05-25T15:33:47 http://comments.gmane.org/gmane.comp.java.aop.aspectj.general/7299 <pre>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&lt; at &gt;eclipse.org https://dev.eclipse.org/mailman/listinfo/aspectj-users </pre> El Lunes 2012-05-24T10:00:44 http://comments.gmane.org/gmane.comp.java.aop.aspectj.general/7298 <pre>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: &lt; at &gt;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&lt; at &gt;eclipse.org https://dev.eclipse.org/mailman/listinfo/aspectj-users </pre> Straub Oliver 2012-05-24T09:06:04 http://comments.gmane.org/gmane.comp.java.aop.aspectj.general/7296 <pre>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&lt; at &gt;eclipse.org https://dev.eclipse.org/mailman/listinfo/aspectj-users </pre> Bhavuk soni 2012-05-23T10:45:50 http://comments.gmane.org/gmane.comp.java.aop.aspectj.general/7291 <pre>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&lt; at &gt;eclipse.org https://dev.eclipse.org/mailman/listinfo/aspectj-users </pre> Sina 2012-05-21T16:25:12 http://comments.gmane.org/gmane.comp.java.aop.aspectj.general/7289 <pre>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 &lt; at &gt;aspectJ files. We use the ANT command &lt;iajc&gt; 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 ============================================= &lt;iajc inpath="Web_origine.war" outjar="Web.war" showWeaveInfo="false"&gt; &lt;classpath&gt; &lt;pathelement path = "ext/aspectjrt.jar"/&gt; &lt;pathelement path = "ext/javax.faces.jar"/&gt; &lt;pathelement path = "ext/annotations-4.2.0.Final.jar"/&gt; &lt;pathelement path = "ext/antlr-2.7.6.jar"/&gt; &lt;pathelement path = "ext/cglib-nodep-2.2.2.jar"/&gt; &lt;pathelement path = "ext/cof-service-api-official.jar"/&gt; &lt;pathelement path = "ext/cof-service-web-official.jar"/&gt; &lt;pathelement path = "ext/common-api-core-official.jar"/&gt; &lt;pathelement path = "ext/common-api-dm-official.jar"/&gt; &lt;pathelement path = "ext/common-api-email-official.jar"/&gt; &lt;pathelement path = "ext/common-api-il-services-official.jar"/&gt; &lt;pathelement path = "ext/common-api-java-services-official.jar"/&gt; &lt;pathelement path = "ext/common-api-moneris-official.jar"/&gt; &lt;pathelement path = "ext/common-api-pega-services-official.jar"/&gt; &lt;pathelement path = "ext/common-api-web-official.jar"/&gt; &lt;pathelement path = "ext/common-api-web-struts-official.jar"/&gt; &lt;pathelement path = "ext/common-api-web-tags-official.jar"/&gt; &lt;pathelement path = "ext/common-api-wi-official.jar"/&gt; &lt;pathelement path = "ext/commons-lang-2.4.jar"/&gt; &lt;pathelement path = "ext/commons-logging-1.1.1.jar"/&gt; &lt;pathelement path = "ext/commons-validator-1.4.0.jar"/&gt; &lt;pathelement path = "ext/cssparser-0.9.6.jar"/&gt; &lt;pathelement path = "ext/dom4j-1.6.1.jar"/&gt; &lt;pathelement path = "ext/guava-11.0.1.jar"/&gt; &lt;pathelement path = "ext/hibernate-3.3.2.jar"/&gt; &lt;pathelement path = "ext/hibernate-annotations-3.4.0.jar"/&gt; &lt;pathelement path = "ext/hibernate-commons-annotations-3.4.0.jar"/&gt; &lt;pathelement path = "ext/hibernate-entitymanager-3.4.0.jar"/&gt; &lt;pathelement path = "ext/hibernate-validator-4.2.0.Final.jar"/&gt; &lt;pathelement path = "ext/junit-4.10.jar"/&gt; &lt;pathelement path = "ext/log4j-1.2.16.jar"/&gt; &lt;pathelement path = "ext/ojdbc14-10.2.0.4.jar"/&gt; &lt;pathelement path = "ext/org.springframework.asm-3.0.6.RELEASE.jar"/&gt; &lt;pathelement path = "ext/org.springframework.beans-3.0.6.RELEASE.jar"/&gt; &lt;pathelement path = "ext/org.springframework.context-3.0.6.RELEASE.jar"/&gt; &lt;pathelement path = "ext/org.springframework.core-3.0.6.RELEASE.jar"/&gt; &lt;pathelement path = "ext/org.springframework.expression-3.0.6.RELEASE.jar"/&gt; &lt;pathelement path = "ext/org.springframework.jdbc-3.0.6.RELEASE.jar"/&gt; &lt;pathelement path = "ext/org.springframework.orm-3.0.6.RELEASE.jar"/&gt; &lt;pathelement path = "ext/org.springframework.transaction-3.0.6.RELEASE.jar"/&gt; &lt;pathelement path = "ext/org.springframework.web-3.0.6.RELEASE.jar"/&gt; &lt;pathelement path = "ext/pop-api-official.jar"/&gt; &lt;pathelement path = "ext/pop-services-official.jar"/&gt; &lt;pathelement path = "ext/richfaces-components-api-4.2.0.Final.jar"/&gt; &lt;pathelement path = "ext/richfaces-components-ui-4.2.0.Final.jar"/&gt; &lt;pathelement path = "ext/richfaces-core-api-4.2.0.Final.jar"/&gt; &lt;pathelement path = "ext/richfaces-core-impl-4.2.0.Final.jar"/&gt; &lt;pathelement path = "ext/sac-1.3.jar"/&gt; &lt;pathelement path = "ext/slf4j-api-1.6.4.jar"/&gt; &lt;pathelement path = "ext/slf4j-log4j12-1.6.4.jar"/&gt; &lt;pathelement path = "ext/j2ee.jar"/&gt; &lt;pathelement path = "ext/commons-collections-3.2.1.jar"/&gt; &lt;pathelement path = "ext/org.springframework.aop-3.0.6.RELEASE.jar"/&gt; &lt;/classpath&gt; &lt;/iajc&gt;_______________________________________________ aspectj-users mailing list aspectj-users&lt; at &gt;eclipse.org https://dev.eclipse.org/mailman/listinfo/aspectj-users </pre> Jean Andre 2012-05-18T16:50:08 http://comments.gmane.org/gmane.comp.java.aop.aspectj.general/7285 <pre>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. </pre> jbolger 2012-05-18T10:09:40 http://comments.gmane.org/gmane.comp.java.aop.aspectj.general/7284 <pre>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(&lt; at &gt;Updates * *.*(..)) implements Observable; private List&lt;Observer&gt; observers = new ArrayList&lt;Observer&gt;(); 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(&lt; at &gt;Updates * *.*(..)) &amp;&amp; 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. </pre> hart404 2012-05-17T18:40:00 http://comments.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.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 &lt; at &gt;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&lt; at &gt;eclipse.org https://dev.eclipse.org/mailman/listinfo/aspectj-users </pre> Steve Ash 2012-05-15T16:45:52 http://comments.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://comments.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 missing classes. How do we inform the waver that those file are inside the war itself ? Best 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-14T21:30:39 http://comments.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://comments.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://comments.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://comments.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.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:485) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456) at org.springframework.beans.factory.support.AbstractBeanFactory $1.getObject(AbstractBeanFactory.java:294) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:225) at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:291) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:193) at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:585) at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:913) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:464) at org.springframework.test.context.support.AbstractGenericContextLoader.loadContext(AbstractGenericContextLoader.java:103) at org.springframework.test.context.support.AbstractGenericContextLoader.loadContext(AbstractGenericContextLoader.java:1) at org.springframework.test.context.support.DelegatingSmartContextLoader.loadContext(DelegatingSmartContextLoader.java:228) at org.springframework.test.context.TestContext.loadApplicationContext(TestContext.java:124) at org.springframework.test.context.TestContext.getApplicationContext(TestContext.java:148) at org.springframework.test.context.support.DependencyInjectionTestExecutionListener.injectDependencies(DependencyInjectionTestExecutionListener.java:109) at org.springframework.test.context.support.DependencyInjectionTestExecutionListener.prepareTestInstance(DependencyInjectionTestExecutionListener.java:75) at org.springframework.test.context.TestContextManager.prepareTestInstance(TestContextManager.java:321) at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.createTest(SpringJUnit4ClassRunner.java:211) at org.springframework.test.context.junit4.SpringJUnit4ClassRunner $1.runReflectiveCall(SpringJUnit4ClassRunner.java:288) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.methodBlock(SpringJUnit4ClassRunner.java:290) at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:231) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) at org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61) at org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:71) at org.junit.runners.ParentRunner.run(ParentRunner.java:300) at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:174) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127) at org.apache.maven.surefire.Surefire.run(Surefire.java:177) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:334) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:980) [/code] Any ideas whether this is a bug, misconfiguration, ...? Arne </pre> Arne Ploese 2012-05-04T09:39:39 http://comments.gmane.org/gmane.comp.java.aop.aspectj.general/7253 <pre>How do we declare multilple class in &lt; at &gt;DeclareParents ? This syntaxe does not work : &lt; at &gt;DeclareParents(value="com.c1 || com.c2" ,defaultImpl=Implclass.class) Thank you _______________________________________________ aspectj-users mailing list aspectj-users&lt; at &gt;eclipse.org https://dev.eclipse.org/mailman/listinfo/aspectj-users </pre> Jean Andre 2012-05-02T13:22:36 http://comments.gmane.org/gmane.comp.java.aop.aspectj.general/7252 <pre>How do we declare multilple class in &lt; at &gt;DeclareParents ? This syntaxe does not work : &lt; at &gt;DeclareParents(value="com.c1 || com.c2" ,defaultImpl=Implclass.class) Thank you _______________________________________________ aspectj-users mailing list aspectj-users&lt; at &gt;eclipse.org https://dev.eclipse.org/mailman/listinfo/aspectj-users </pre> Jean Andre 2012-05-02T13:22:36 http://comments.gmane.org/gmane.comp.java.aop.aspectj.general/7246 <pre>Hi all, I am just trying to use AspectJ to get a handle on all the threads that an application runs. To start with, I just want to know how many there in how many ThreadGroups. I am using Loadtime Weaving to advise an admittedly large code base- a popular open source IDE. Yes, it's huge. What I am experiencing is the application "hangs" on start up without terminating and without seeming to progress or so it seems. By "hangs" all I mean is the application's splashscreen appears but the progress bar gets stuck after a while and doesn't move. For half an hour, at which time I quit the program. It DOES work as intended - it does give me the information I am seeking, but there just comes a point when the output from this aspect is intermittent and the progress bar is not moving and I can't prove it's not in long many statement infinite loop. So my question is, is there something special about advising Runnable.run() that is doomed to slow everything to a crawl or get caught in an infinite loop for some reason? The problem may be just the sheer number of things I am trying to advise, because the code base is so large. The only reason I don't think that is using another aspect, I can advise all methods and the application successfully loads (then tells me I am out of memory and becomes uselessly slow). The "everything" aspect is just pointcut captureAllMethods() : execution( * *(..)); and then I print out the signature and source location in the before() statement of the aspect. I am sure you've all seen 1000 times before, but I included this aspect along with the thread aspect at the bottom of this question. Using this "everything" aspect also takes a long time but it does result , after many minutes, in the application being launched. Oddly, when I apply BOTH aspects, the application I do get continuous output from the "everything" aspect. which means it's still running. In a slightly different version of the thread aspect, I make sure to !within the aspect itself, just in case I was entering an infinite loop with the aspect advising itself - something I don't see as even being possible given the particular aspect. I also do some System.out. printlns just to be sure that the thing is still alive, which it is. So I guess my other question is- have you been here before with really big code bases? Is this just something that's bound to be unusable and the fact that my ( 64 bit AMD quadcore 8 gig RAM) computer runs for 45 minutes with no sign of further progress is not a surprise to anyone? Or is something else at work here? Any advise is appreciated. --------------------------------------------------------------------------------------------------- "Everything " aspect: ---------------------------------------------------------------------------------------------------- package recipePackage; public aspect CaptureCallTargetRecipe { pointcut captureAllMethods() : execution( * *(..)) &amp;&amp; !within(CaptureCallTargetRecipe); // Advice declaration before() : captureAllMethods() { System.out.println( "Signature: " + thisJoinPoint.getStaticPart( ).getSignature( )); System.out.println( "Source Line: " + thisJoinPoint.getStaticPart( ).getSourceLocation( )); System.out.println(); } } --------------------------------------------------------------------------------------------------- "Thread" aspect: --------------------------------------------------------------------------------------------------- package recipePackage; import java.util.ArrayList; import java.util.Iterator; import java.util.List; public aspect CaptureAllUniqueThreadsStartingRecipe { static List&lt;Thread&gt; threads = new ArrayList&lt;Thread&gt;(20); static List&lt;ThreadGroup&gt; threadGroups = new ArrayList&lt;ThreadGroup&gt;(20); pointcut captureAllThreads(): execution(public void Runnable.run() ) ; // Advice declaration before(): captureAllThreads() { Thread thisThread = Thread.currentThread(); if (thisThread == lastThread) { return; } lastThread = thisThread; for (Iterator&lt;Thread&gt; threadIterator = threads.iterator(); threadIterator.hasNext(); ) { Thread nextThread = threadIterator.next(); if (thisThread == nextThread) { threadFound = true; return; } } threads.add(thisThread); for (Iterator&lt;ThreadGroup&gt; threadGroupIterator = threadGroups.iterator(); threadGroupIterator.hasNext(); ) { ThreadGroup threadGroup = threadGroupIterator.next(); if (Thread.currentThread().getThreadGroup() == threadGroup) { threadGroupFound = true; break; } } { threadGroups.add(thisThread.getThreadGroup()); } System.out.println("------------------- THREAD DISCOVERED--------------------"); System.out.println("New thread discovered: " + thisThread); System.out.println("Thread List"); System.out.println("number Of Threads Created so far= " + threads.size()); System.out.println("number Of ThreadGroups Created far+ " + threadGroups.size()); System.out.println("Threads so far: "); int i=0; for (Iterator&lt;Thread&gt; iterator = threads.iterator(); iterator.hasNext(); ) { Thread nextThread = iterator.next(); System.out.println(); System.out.println("Thread Name : " + nextThread.getName()); System.out.println("Alive? " + nextThread.isAlive()); System.out.println("Daemon? " + nextThread.isDaemon()); System.out.println("Thread Group? " + nextThread.getThreadGroup().getName()); System.out.println("------------------------------------------------------------"); } } public volatile boolean threadFound; public volatile boolean threadGroupFound; public Thread lastThread; public Thread newThread; } </pre> trhouse 2012-04-27T23:07:42 http://comments.gmane.org/gmane.comp.java.aop.aspectj.general/7245 <pre>Apologies for multiple copies received... Due to numerous requests for a deadline extension we have postponed the deadline by one week. Nevertheless, we ask to submit abstracts by May 1st (see below). *** WODA 2012 *** 10th International Workshop on Dynamic Analysis Sunday, July 15, 2012, Co-located with ISSTA, Minneapolis, MN http://woda2012.ec-spride.de/ ========================= Important dates ========================= * Abstract submission deadline: May 1st, 2012 (23:59 American Samoa Time) * Paper submission deadline: May 4th, 2012 (23:59 American Samoa Time) * Author Notification: May 25th, 2012 * Submission of camera ready papers: June 1st, 2012 ========================= Workshop format ========================= The overall goal of WODA 2012 is to bring together researchers and practitioners working in all areas of dynamic analysis to discuss new issues, share results and ongoing work, and foster collaborations. For more details see http://woda2012.ec-spride.de/ ========================= Submission Format ========================= Submissions to WODA should be four to six page papers in one of the following categories: * A position paper describing an issue in the field, and arguing for a specific  stance or approach to that issue; * An idea paper that puts forth a radical and completely unproven idea that may  generate discussion and ideas for future research; and * An “early bird” research report that is not a “short conference paper” but an  exciting report of initial results from new research effort. ========================= Possible topics ========================= WODA welcomes any submissions that strongly relate to dynamic analysis; typical areas of interest that WODA covers are: * Development of dynamic analysis tools and frameworks * Efficient instrumentation techniques * Novel applications of dynamic analysis * Program security and penetration testing * Fault detection and debugging * Performance analysis and optimization techniques * Remote analysis and measurement of software systems * Runtime monitoring * Software testing * Statistical reasoning techniques * Synergies between static and dynamic analysis techniques * Visualization and classification of program behavior * Analysis of program usage * Relating user feedback to execution dynamics * Dynamic analysis on alternative hardware platforms * The workshop will be a one-full-day workshop, structured to encourage  discussion and develop research collaborations. Accepted WODA papers will be included in the ISSTA proceedings and thus will be accessible to the workshop participants before the workshop to facilitate interaction and discussion. WODA papers will also be published in the ACM Digital Library. ========================= Program Committee ========================= Walter Binder, University of Lugano Eric Bodden, EC SPRIDE / TU Darmstadt Gordon Fraser, Saarland University Alex Groce, Oregon State University Salvatore Guarnieri, IBM Research USA Rajiv Gupta, University of California at Riverside Patrick Lam, University of Waterloo Shan Lu, University of Wisconsin Welf Löwe, Linnaeus University Samuel Midkiff, Purdue University Nick Mitchell, IBM Research USA Madanlal Musuvathi, Microsoft Research Grigore Rosu, University of Illinois at Urbana Champaign Suresh Thummalapenta, IBM Research India ========================= Organizers ========================= Eric Bodden Secure Software Engineering Group European Center for Security and Privacy by Design (EC SPRIDE), TU Darmstadt Madanlal Musuvathi Research in Software Engineering Group Microsoft Research </pre> Eric Bodden 2012-04-27T07:23:03 http://comments.gmane.org/gmane.comp.java.aop.aspectj.general/7242 <pre>Hi, I'm running into an odd problem with m2e and AJDT. With Andy's help on the SpringSource STS forum, I think I have managed to isolate the problem a little better, but not sure if I am encountering a bug, or if there is something I am missing in my Eclipse configuration. My original thread can be found at: http://forum.springsource.org/showthread.php?125470-How-to-enable-AspectJ-nature-in-a-Spring-project-with-annotated-and-aj-aspects In a nutshell, I have a Maven based Spring project. I'm using Eclispe 3.7 with the following m2e plugins m2e: 1.0.100.20110804-1717 maven for AJDT: 0.13.0.2011.07281640 maven for WTP: 0.14.0.20110928-2045 I have some Spring aspects defined with AspectJ annotations. By themselves, they work fine. I then added some .aj aspects and enabled AspectJ Capabilities on the project. Suddenly my Spring aspects are instantiated twice in my junit tests - once by Spring, and once (I believe) by some CTW of the AJ compiler. (Note that these are junits run within Eclipse). If I use the -xmlConfigured flag on AJ project properties and specify my own aop.xml file with only my .aj aspect listed there the junits work fine. I have tried added an &lt;exclude&gt; tag in my aspectj-maven-plugin, excluding the Spring aspects, but they are still run twice. Is this a bug in m2e? Or is there a problem with AJDT? Or am I doing something wrong, or missing some configuration somewhere? My pom has the following aj-related things &lt;dependency&gt; &lt;groupId&gt;org.springframework&lt;/groupId&gt; &lt;artifactId&gt;spring-aop&lt;/artifactId&gt; &lt;version&gt;${org.springframework.version}&lt;/version&gt; &lt;/dependency&gt; &lt;!-- Support for AspectJ Annotations --&gt; &lt;dependency&gt; &lt;groupId&gt;org.aspectj&lt;/groupId&gt; &lt;artifactId&gt;aspectjweaver&lt;/artifactId&gt; &lt;version&gt;${org.aspectj}&lt;/version&gt; &lt;/dependency&gt; &lt;!-- AspectJ weaving --&gt; &lt;dependency&gt; &lt;groupId&gt;org.aspectj&lt;/groupId&gt; &lt;artifactId&gt;aspectjrt&lt;/artifactId&gt; &lt;version&gt;${org.aspectj}&lt;/version&gt; &lt;/dependency&gt; &lt;dependency&gt; &lt;groupId&gt;org.aspectj&lt;/groupId&gt; &lt;artifactId&gt;aspectjtools&lt;/artifactId&gt; &lt;version&gt;${org.aspectj}&lt;/version&gt; &lt;/dependency&gt; ... ... &lt;plugin&gt; &lt;groupId&gt;org.codehaus.mojo&lt;/groupId&gt; &lt;artifactId&gt;aspectj-maven-plugin&lt;/artifactId&gt; &lt;version&gt;1.4&lt;/version&gt; &lt;configuration&gt; &lt;outxml&gt;true&lt;/outxml&gt; &lt;source&gt;1.6&lt;/source&gt; &lt;target&gt;1.6&lt;/target&gt; &lt;weaveDependencies&gt; &lt;weaveDependency&gt; &lt;groupId&gt;commons-pool&lt;/groupId&gt; &lt;artifactId&gt;commons-pool&lt;/artifactId&gt; &lt;/weaveDependency&gt; &lt;/weaveDependencies&gt; &lt;!-- don't weave any of the Spring aspects with AJ --&gt; &lt;excludes&gt; &lt;exclude&gt;**/*Interceptor.java&lt;/exclude&gt; &lt;/excludes&gt; &lt;/configuration&gt; &lt;executions&gt; &lt;execution&gt; &lt;goals&gt; &lt;goal&gt;compile&lt;/goal&gt; &lt;goal&gt;test-compile&lt;/goal&gt; &lt;/goals&gt; &lt;/execution&gt; &lt;/executions&gt; &lt;/plugin&gt; Thanks, Eric _______________________________________________ aspectj-users mailing list aspectj-users&lt; at &gt;eclipse.org https://dev.eclipse.org/mailman/listinfo/aspectj-users </pre> Eric B 2012-04-18T15:55:20 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.java.aop.aspectj.general