Re: [aspectwerkz-dev] tracing to the console

Right now I am printing the classloader.hashCode.
Tomcat classlaoder.toString was returning to much information so I had to
stick to hashCode
I d like to avoid some runtime check on the classloader instance

In my mind, I d like to have a (HTML / Swing ?) based console that can
show the classloader hierarchy, the system hierarchy etc, and could have
some extension point to provide some renderer specific to a target
platform (tomcat, wls etc) for the classloader (f.e. show the name of the
app, instead of the classloader info). I have a proto that is a WLS web
based console right now, but not yet QAed for 1.0b1.

I am wondering if it would be worth the effor to do this console in a
Swing way and use the remote proxy server we already have there.
Please vote / comment on that if this is of interest for you (I am just
bored with html based stuff.. so if we can avoid a silly generic JSP -
although this one can be done in 5 minute and hacked at your convenience).

Alex



----- Original Message -----
> Hi,
>
>    I noticed that AW 1.0 beta1 is dumping some trace information about
> classloaders to the console. It will be great to see URL's handled by
> the classloader instance if this instance extends URLClassLoader (there
> is a method called getURLs()).
>
>    Thank you.
>
>    Eugene
>
>
>