Hi Eric, Could you try the standard Java launcher instead and explicitly specify the agent as a launching parameter? Also, I do think that the aop.xml is required for LTW launching. This can be auto generated from the compiler through Project Properties -> AspectJ Compiler -> Other -> outxml.
On Thu, May 5, 2011 at 2:36 AM, Eric Bodden <eric.bod...@mail.mcgill.ca> wrote: > Hi all. > > I am using load-time weaving through an appropriate Eclipse launch > configuration but without any aop.xml file. The application that I am > weaving into loads the bulk of its classes through a custom class > loader. Now it appears that the load-time weaver is currently only > weaving into the classes loaded by the default class loader, and hence > most of the actual classes that make up the application are missed. > > Why is this the case? Is Eclipse not using the agent-based approach by > default? I had expected that all loaded classes would be woven, no > matter which class loader is used. > > Is there a way to get around this problem? > > Cheers, > Eric > -- > Dr. Eric Bodden, http://bodden.de/ > Principal Investigator in Secure Services at CASED > Coordinator of the CASED Advisory Board of Study Affairs > PostDoc at Software Technology Group, Technische Universität Darmstadt > Tel: +49 6151 16-5478 Fax: +49 6151 16-5410 > Mailing Address: S2|02 A209, Hochschulstraße 10, 64289 Darmstadt > _______________________________________________ > aspectj-users mailing list > aspectj-users@eclipse.org > https://dev.eclipse.org/mailman/listinfo/aspectj-users > _______________________________________________ aspectj-users mailing list aspectj-users@eclipse.org https://dev.eclipse.org/mailman/listinfo/aspectj-users