On 16/12/2010 2:19 AM, Martin Höller wrote:
Hi Ron!
Am Mittwoch 15 Dezember 2010, 23:04:49 schrieb Ron Wheeler:
Use JNDI to manage the site specific aspects of your configuration. This
will make deploying to test machines and production less painful.
I saw you mentioning this a few times now. However, I don't get it what you
are actually doing here. Would you mind explaining this approach in more
detail.
tia,
- martin
Of course, it is fairly specific to what we need.
1) Database connection specification is clearly a place where JNDI is a
great solution.
2) Site name/customer name - can be used in code to specify namespaces
or build file specifications,
3) Webservice endpoint specifications so that clients use the right
webservices for test and production by customer.
4) URLs for resources or error screens
We have removed anything that relates to operations/deployment from the
code and into the Tomcat configurations (server.xml) on the server instance.
Is this what you are looking for?
Ron
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
