Re: [aspectwerkz-dev] tracing to the console

I think so, but for Java 1.3 and 1.4 it will pby ignore
java.lang.ClassLoader, URLClassLoader etc, so you might miss some part since
a user can use new URLClassLoader() directly.
Else just hotswap it by hand at the beginning of your app. There should be a
way if you need it.

Alex

----- Original Message ----- 
From: "Eugene Kuleshov" <eu-E/[email protected]>
To: <[email protected]>
Sent: Wednesday, July 14, 2004 12:27 PM
Subject: Re: [aspectwerkz-dev] tracing to the console


> Alex wrote:
>
> > Sure, this one should work fine to intercept user hacked ClassLoader
> > subclasses.
>
>    Sorry for bugging this, but can it be done using online mode only
without
> precompilation?
>
>    regards,
>    Eugene
>
>
> > ----- Original Message ----- 
> > From: "Eugene Kuleshov" <eu-E/[email protected]>
> > To: <[email protected]>
> > Sent: Wednesday, July 14, 2004 12:19 PM
> > Subject: Re: [aspectwerkz-dev] tracing to the console
> >
> >
> >
> >>Alex, Jonas,
> >>
> >>   That all is godd to know but it is all AW internals. What I'm looking
> >
> > for
> >
> >>is to bind and advice to the following pointcut
> >>
> >>   execution(* java.lang.ClassLoader+.new(..))
> >>
> >>   It will be ok to do not have advice at the very top class loader.
> >>
> >>   regards,
> >>   Eugene
> >>
> >>>Exact
> >>>There is indeed some ways to alter the java.lang.ClassLoader as well
> > with
> >>>JVMTI, but then it makes things complex to support offline deployments.
> >>>Alex
>
>