Our webapp is given to many discrete clients with their own networks. Often these users do not have tomcat at all. Our application requires it. Therefore the IT guy has to install tomcat when they get our web app. And they are not familiar with the ins and outs of tomcat at all.
My ideal sequence of events is this. 1) User installs tomcat 2) User places our clean database file in the "recommended location on the server machine. i.e c"\databse\ourfile.gdb" 3) User drops our war file into the webapps directory. It expands, copies the context.xml file we pre-configure with the db file location from step 2. 4 ) user can then fire up our app. And it connects ok to the db. I would prefer not to instruct the user to create a global JNDI, or a context level JNDI using the tomcat/admin app. Not because they can't but to reduce the number of steps and or sources of user input error. These are our number one source of installation/deployment hiccups. If we can include a preconfigured contxt.xml, and have it used when the app is deployed, it would then not require the user to setup the context JNDI, or a global one. Frankly I don't care if its global or context level. I just want it to work. -----Original Message----- From: Caldarale, Charles R [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 18, 2006 5:49 PM To: Tomcat Users List Subject: RE: placing context.xml in META-INF works? > From: Christopher Schultz [mailto:[EMAIL PROTECTED] > Subject: Re: placing context.xml in META-INF works? > > I get that, but it sounds like that's exactly what this guy wants: > configuration that is available to all of his webapps, and never > changes. If it smells like a global resource...? I didn't read it that way. My interpretation was that he wanted something accesible to all his _customers_ (each with their own server), not multiple webapps. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- 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]