The usual approach is to configure resources such as databases as part of the servlet container, and then reference these via JNDI. It requires a small change to the applicationContext-resources.xml file to point to the correct JNDI name, and then some servlet container specific configuration to set up the database connection. This allows you to create a single binary package and deploy it to several different environments (e.g. dev, test, qa, etc).
Mike On 12/8/06, acate <[EMAIL PROTECTED]> wrote:
Please re-read my question. The server names will not be the same. Fadi Samara wrote: > > well it depends where your database is located. It is on the same machine > you are deploying to, you should be fine with *localost* > > On 12/8/06, acate <[EMAIL PROTECTED]> wrote: >> >> >> I am new to AppFuse and Spring, but need to build an app that has a mysql >> connection. I can build the app locally and use "localhost" as part of >> the >> mysql connection parameters. However, when I deliver the app to the >> designated server the host name "localhost" will be different. What is >> the >> appropriate strategy to take so that I can build and deploy and >> automatically account for the mysql host name? Thanks for any help. >> -- >> View this message in context: >> http://www.nabble.com/AppFuse---Spring-Question-tf2781685s2369.html#a7760891 >> Sent from the AppFuse - User mailing list archive at Nabble.com. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > -- View this message in context: http://www.nabble.com/AppFuse---Spring-Question-tf2781685s2369.html#a7761021 Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
