On Mon, Aug 31, 2009 at 1:50 PM, Martin Gainty<mgai...@hotmail.com> wrote: > > https://issues.apache.org/bugzilla/show_bug.cgi?id=47769
That's a very good start. Thanks! There is however still one vital piece of information missing in the proposed documentation update. It now clearly states that resource-ref in the web.xml deployment descriptor is optional, but it still doesn't explain what exactly it is that using resource-ref buys me. Okay, it's optional, so I don't HAVE to use, but if I DO use it, what possible advantage does it have? Don't get me wrong, I'm not trying to be clever, just honestly wondering about this. But consider the following analogy. Putting a file called 'nobody-reads-this.txt' in your root directory is obviously optional too. I mean, you -can- put this file there, but if you do that nothing happens. It's a filename I just made up and of course Tomcat doesn't know about it. To me, using resource-ref feels exactly like this. You -can- put this in your web.xml, but as far as I can see nothing changes. Now, maybe, just maybe, it has something to do with compatibility with other servlet containers? I have tried war archives with Jboss, and at least on Jboss resource-ref isn't needed either. DataSources appear in the java: JNDI space, just as in Tomcat. Only the exact location is different, but resource-ref does not seem capable of doing any name aliasing and thus can't be used for that purpose either. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
