You'll need something like that:
In Tomcat's:
value="jdbc:mysql://127.0.0.1:3306/shproduction" type="java.lang.String"
override="false"/>
In Spring config:
Greetings, Lilianne E. Blaze
Bas Schulte wrote:
Hi,
I'd like to deploy my Spring-based webapp twice in the same Tomcat
ins
Bas Schulte wrote:
Hi,
I tend to agree with both you and Chuck. However... ;)
We're on a budget so separate servers is a no-op. Running multiple
instances of Tomcat, with it's own start/stop script and it's own
location for config files/libs etc. won't allow me to continue using
debian's pac
Hi,
I tend to agree with both you and Chuck. However... ;)
We're on a budget so separate servers is a no-op. Running multiple
instances of Tomcat, with it's own start/stop script and it's own
location for config files/libs etc. won't allow me to continue using
debian's package management (
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bas,
Bas Schulte wrote:
| I'd like to deploy my Spring-based webapp twice in the same Tomcat
| instance, one for production and one for development.
I agree with Chuck: you are asking for trouble with a production
configuration that includes develop
> From: Bas Schulte [mailto:[EMAIL PROTECTED]
> Subject: Configuring one webapp in 2 instances, system properties
>
> I'd like to deploy my Spring-based webapp twice in the same Tomcat
> instance, one for production and one for development.
I strongly recommend that you don&
Hi,
I'd like to deploy my Spring-based webapp twice in the same Tomcat
instance, one for production and one for development.
To configure my webapp, these distinct environments connect to
different database schema using different username/password combo's.
My spring configuration gets thi
