Benson wrote: > I'm reading this thread as the following meta-discussion. I may be > confused.
It's been a fairly long thread. You've got the jist though, except: I don't use global resources and I'm not for or against either them or per-webapp resources. I joined the thread to help someone else who was having trouble configuring a global resource. My interest is learning about and following standards where I can, although I'm not religious about that either if it gets too difficult ;) I don't think the problem are over whether to put jars under webapps or common (at least, not the problems mentioned on this thread). It's been more about which config file to put the resource config in. I don't think the TC docs are poor, I think they are 99% spot on. It is a confusing area for DBCP/JNDI newbies, because there are several docs, and a few choices to make about which approach to take (plus, in my case, I didn't find the docs at first because I didn't know they were there, and other things came higher on google). I have spotted a few possible small enhancements to the existing docs, which I intend to contribute just as soon as I've worked out how to diff the files on my windows box. My eureka moment was Yoav pointing out that often (but not always) it's not necessary to use container-managed resources, and in fact if you avoid them, you will have a more portable webapp. If only I'd realised that earlier, I wouldn't have got into the whole container-managed resource thing at all. Doh. > However, us poor suckers who use JNI > are forced into global resources for other reasons. Now I see where you're coming from on JNI, and I agree, it's a good reason to use them. But as I said above, I'm not against global resources anyway, nor is anyone else on this thread as far as I can tell. Except maybe Yoav ;) > Whoops, I missed a point: > > 'counter-example' to the general idea that anything you can do as a > global resource you can do just as well as a per-web-app resource. Aha! Thanks for explaining that. I agree - that general idea is probably not true (and likewise vice-versa). I also think there are probably many more counter-examples, including many in the situation where container adminstrators want to configure resources rather than letting a load of webapp programmers loose on DIYing it. In summary then, I think that both global and per-webapp resources have their place; each to his own according to personal taste :) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
