[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [aspectj-users] Load time weaving and classpath!
|
Matthew,
Of course there is no difference at the end - my jar files have to be in the classpath
of the application when it's run in the application server (here OAS).
But the jar files are part of our normal deployed application. And in the
classloader hirarchy normally these classes have to be loaded by the classlaoder of
the application and not at startup.
My idea would be to define joinpoints not in the aspect but only in the xml file.
Would the AspectJ loader still load the aspects to check if there are joinpoints?
Because normally he has to load them because he has to check where they have to be weaved in.
And I'm not sure if the 1.5 agent can do this anyhow different.
And for me this behavior is a problem because I don't want to modify the javawrapper
of the OAS every time I have a change in the aspect.
Thanks,
Michael
--
Michael Dempfle
Master of Computer Science (MC.Sc.)
mgm technology partners GmbH
Frankfurter Ring 105a
80807 München
Tel. +49 89 358680-309
Fax +49 (89) 35 86 80-88
Michael.Dempfle@xxxxxxxxxx
http://www.mgm-tp.com
