In terms of changing your ip/port for each deployment you may be better off if you configure the JDBC connection as a JNDI data source rather than build the database connection details into the binary war file. In our environment we are not allowed to change the binary between deployment environments, i.e. the binary we deploy in test must be exactly the same binary we deploy in production.
To use JNDI data sources, just uncomment the relevant line in applicationContext-resources.xml and comment out the existing datasource bean. Mike. On 10/25/07, John Kwon <[EMAIL PROTECTED]> wrote: > > Just found it. Thanks! > > On 10/25/07, Alex Coles <[EMAIL PROTECTED]> wrote: > > > > You only need to rebuild the WAR file if you want to make the IP/port > > default from now on. > > > > If you look in the classes directory of the WAR file after its been > > deployed and unzipped, you should find jdbc.properties. > > > > You should be able to modify jdbc.properties, and then restart the > > application within Tomcat or whatever container you're using. > > > > On 10/25/07, John Kwon < [EMAIL PROTECTED]> wrote: > > > Do I have to rebuild every time I want to change the port and ip of my > > sql > > > server instance? > > > > > > I can't find a properties file that gets set by the pom.xml > > > > > > I hate to have to rebuild for every single server this app goes to. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > >
