Thanks for that unambiguous clarification! I will 
settle for the fat independent webapp contexts.
On your comment below:

    uma> I am trying to determine if its possible to attempt such a 
    uma> layering with Tomcat.
    > 
    Cc> It has nothing to do with Tomcat, but everything to do with application
    CC> independence.

You are referring to the webapp contexts as 'applications', while
I regard the webapp contexts as *components* of a larger application.
IMO, the problem is occurring because Tomcat does not have a notion
of this larger application which is a federation of webapp contexts.

Regards,

/U


 -------------- Original message ----------------------
From: "Caldarale, Charles R" <[EMAIL PROTECTED]>
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
> > Subject: RE: Classloader Problems: loading webapp classes 
> > using commons CL
> > 
> > You won't duplicate a sorting algorithm even if it takes only 
> > a few more bytes would you?
> 
> Duplicating source code, certainly not.  Duplicating within multiple
> wars, absolutely I would.  You're causing yourself a whole lot of
> headaches by trying to mimic your source structure in your packaging.
> Many, many have gone down that path before you, with no benefit but
> increased frustration and complexity for all involved.
> 
> > I am trying to determine if its possible to attempt such a 
> > layering with Tomcat.
> 
> It has nothing to do with Tomcat, but everything to do with application
> independence.
> 
> > - when is the webapp classloader "born"?
> 
> When the webapp is first referenced, which could be a lifecyle listener,
> a load-on-startup setting, or the first client request to the webapp.
> 
> > - is the webapp classloader loaded by the 
> > commons classloader or the system classloader?
> 
> Don't know, because it's not really an interesting question.
> 
> > - which classloader loads the context loader listener?
> 
> The webapp classloader.
> 
>  - Chuck
> 
> 
> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
> MATERIAL and is thus for use only by the intended recipient. If you
> received this in error, please contact the sender and delete the e-mail
> and its attachments from all computers.
> 
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to