Hmm, well, there are no other web applications, the server is dedicated to this one. If there *were* other web applications, they would likely be using the same data source anyways -- and in that case it's certainly handy to be able to set the data source for multiple web apps by maintaining just a single entry in one of Tomcat's configuration files. Also, for now, I did name the resource something unique to the web application, I'm not worried about conflicts. As for management, simple instructions "insert this into context.xml on new server setup" seems to be working out well.
I can't think of any way that's more convenient. IMHO, if the choice is writing custom deployment scripts and having to maintain and run those to deploy the web app (and centrally maintaining separate copies of configuration files so they can be distributed with the deployment scripts rather than letting other developers maintain their own), and describe to other developers how those work vs. adding an entry to context.xml once and using Tomcat manager to deploy things, it seems that the former ends up being more confusing and hard to manage. To be honest I can't think of a single compelling reason not to do it this way, or any reason at all other than the fact that I have to explain to developers that when setting up a new system, they must modify Tomcat configuration files, and I don't see that as a big deal. I could be missing something, but everything is working great and is incredibly easy to manage now that I've made this change. That seems positive. Jason On Thu, Nov 6, 2008 at 5:23 PM, Christopher Schultz <[EMAIL PROTECTED]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Jason, > > Jason Cipriani wrote: >> My end solution ended up being to modify >> $CATALINA_ROOT/conf/context.xml and put the JNDI data source >> definition there. > > Yikes! You should /definitely/ not do that. Doing so will make that JNDI > data source available (separately, I might add) to all deployed > applications. You'd be better off putting it in server.xml, since nobody > really ever looks for anything in the server-wide context.xml. I believe > you will be adding confusion at the least and a management nightmare at > the worst. > > - -chris > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (MingW32) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iEYEARECAAYFAkkTbmgACgkQ9CaO5/Lv0PBg4gCgpjHTTBCbQDvesDsgYh7ork8i > 11YAn2d/Hx2erPtBGBdxrkVjLwAY97Wr > =4mqt > -----END PGP SIGNATURE----- > > --------------------------------------------------------------------- > 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]
