Hi Mark,
Thanks for your comments.
Please see my comments below.
----- Original Message ----
> From: Mark Thomas <ma...@apache.org>
> To: Tomcat Users List <users@tomcat.apache.org>
> Sent: Tue, January 26, 2010 11:19:33 PM
> Subject: Re: Global JNDI resource loaded from a webapp
>
> On 26/01/2010 07:59, Woonsan Ko wrote:
> > Does *global JNDI resource* mean that all implementation jars must be in
> shared lib path together with the sharable interfaces?
>
> Yes.
>
> > If sharable interfaces are in the shared lib path like javax.sql.DataSource
> > or
> javax.jcr.Repository, but the real implementation of those are loaded from a
> web
> application, then isn't it possible to call it a "global JNDI resource" of
> javax.sql.DataSource or javax.jcr.Repository?
>
> This is unlikely to work and if by some fluke it did work you will have
> a memory leak.
IMHO, if Tomcat *optionally* allows a web application context descriptor to
define a global JNDI naming resource, then it would be very useful.
In this case, I think it's doable to manage the lifecycle of the resource to
keep from memory leak.
This feature could give resource reloading feature in a separate classloader.
Kind regards,
Woonsan
>
> Mark
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
