On 16/12/2010 4:23 AM, Brett Porter wrote:
On 16/12/2010, at 6:19 PM, 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.
It's not strictly related to automated deployment (though it might help)... the basic
idea is to ensure that a single WAR can be used in any environment without being rebuilt.
So anything specific to a target environment is "externalised" - typically
database connections or a set of properties. These can all be specified through JNDI, or
other similar techniques.
Exactly.
More information can be found at slide 31:
http://brettporter.files.wordpress.com/2007/11/ac-us-07-maven-best-practices.pdf. Or for
those that have it, chapter 7 of "Apache Maven 2: Effective Implementation".
Great presentation. I would agree with everything here.
It is a presentation rather than a manual but the ideas are pretty clear.
Cheers,
Brett
--
Brett Porter
[email protected]
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
