Thx for the response. The sample you have is the same i have in my build.
Problem is by the time in my build process aopc runs....the above classes folder probably has around 3000 or so compiled classes. My aspect definition in the -aop.xml file is against all classes that have a pattern of *BO.class (of course written in the manner expected by aop). We have probably around 200-250 classes that end with *BO. These are our business objects. I cannot change the current build structure since thats pretty much written in stone (or not managed by me). If you run aopc against so many classes (with verbose turned ON) you will see that it tries to match every .class to the patterns defined in the -aop.xml file. And at some point dies outofmemory. I am still surprised with this implementation. Since we use weblogic the build dir even contains all weblogic precompiled classes. - Now the workaround for me is to copy the *BO classes in my aop build first to a temp classes folder...aspect against that classes folder and then move them back to the main folder...will work but not the most desirable approach. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3863219#3863219 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3863219 ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
