Re: [classloader hierarchy] compare loom and phoenix 4.0.3

Hiya,

I have a document describing the current ClassLoader hierarchy. I will send
it along as soon as I get the network connected at my new place - probably
in a day or so.


----- Original Message ----- 
From: <[email protected]>
To: <jcontainer-interest-81qHHgoATdGxIXFVlbCvtR2eb7JE58TQ@public.gmane.org>
Sent: Monday, January 19, 2004 10:40 PM
Subject: [classloader hierarchy] compare loom and phoenix 4.0.3






Hi there.

Can someone show me a graph displaying the classloader hierarchy of
loom-beta, and if you don't mind as well phoenix-4.0.3, since I still have
phoenix in production, loom only in begin of evaluation.

Background:
I have a SAR containing jetty, axis and own components in the container
(when I refer to "the container" I mean both).
FYI: jetty-webserver runs as a component in the container; axis is hosted
as webapp within jetty.
In some special scenarios I run into classloading issues, when I lookup a
component from within an axis webservice, that shares some bean-classes
with my component.

ATM, my workaround is to sacrifice the use of these beans in my components
and use primitives instead.
But eventually, I want to understand classloading in loom/phoenix, jetty
and axis well enough to be able to solve the problem at its root.

Cheers,
Joerg

-----------------------------------------------------------
Jörg Buchberger
Dipl.-Ing. Technische Informatik (FH)
PRÜFTECHNIK Condition Monitoring GmbH
Franz-Bayer-Straße 14, 88213 Ravensburg
http://www.pruftechnik.com
Tel:   +49 (0)751-76956-0
Fax:   +49 (0)751-76956-79
-----------------------------------------------------------

_______________________________________________
jcontainer-interest mailing list
jcontainer-interest-81qHHgoATdGxIXFVlbCvtR2eb7JE58TQ@public.gmane.org
http://lists.codehaus.org/mailman/listinfo/jcontainer-interest