Re: witness the classloader loading classes
schwarml@gmail.com wrote:
...
In the WebSphere contect, ...
I recalled your thread from the other day, which is why I
guessed this was the same problem. A lot of people will
not remember a post/thread/person from the very same
day though, so it is best to presume that your audience
in each thread knows *nothing* about the problem domain,
and restate it for each thread.
...I need to know which classloader mode is
being used ...
We also discussed this briefly, though nothing much
useful came of it. The thing is, I am still not entirely
clear on why it is important to know from where, or
using which classloader, that classes are obtained.
If these differences change the behaviour of the app.
itself, it should be possible to test from within the app.
code, to see which of two (or more) possibilities exist.
OTOH, if the classloading order does *not* affect the
app., ..why would anybody want to know?
So the hint here, is can you be a lot more specific
about the *end* *goal* of detecting the classloader
info.? Note that 'knowing which classloader is
used' might be a (probably flawed) strategy aimed
at achieving a goal - but it is not any sort of *goal*
in itself.
--
Andrew Thompson
http://www.athompson.info/andrew/
Message posted via JavaKB.com
http://www.javakb.com/Uwe/Forums.aspx/java-setup/200709/1