I agree that you might expect GlobalNamingResources to be accessible globally. But I think what the name is intended to mean is that the resources under GlobalNamingResources are _potentially_ available to any webapp -subject to you configuring the ResourceLink. Contrast this with placing the Resource under a webapp Context, in which case is not not even potentially available to other webapps.
I'm basing my comment on my own experiences in failing to get DBCP to work when using <Resource> under <GlobalNamingResources>, plus what it says here: http://jakarta.apache.org/tomcat/tomcat-5.0-doc/config/context.html#Resource %20Links > -----Original Message----- > From: sven morales [mailto:[EMAIL PROTECTED] > Sent: Tuesday 26 October 2004 14:54 > To: [EMAIL PROTECTED] > Subject: RE: JNDI DataSource GlobalResources problem > > > Stever Kirk: Did I read that right, "<Resource> > nested inside <GlobaNamingResource> is not visible to > the webapp?" I thought that was the whole purpose "to > make it visible globally" naming resources under > <GlobalNamingResource> noh? If Im wrong I stand > corrected. > > > > > __________________________________ > Do you Yahoo!? > Yahoo! Mail Address AutoComplete - You start. We finish. > http://promotions.yahoo.com/new_mail > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
