This looks like "Best Practice" that most people who are building
production systems need to have.
Can you elaborate a bit more.
Is this documented anywhere?
Ron
On 30/08/2010 7:32 AM, Stephen Connolly wrote:
What I'm saying is that you (ultimately) should refactor your project so
that one war works on all deployment targets. That way you don't need to
create multiple wars each tuned for the specific deployment environment.
Solutions can include (but are not limited to):
1. Using JNDI or an external .properties file to hold the deployment
specific config
2. Adding a deployment specific provider jar to the deployment target lib
folder (e.g. abstract the deployment specific code behind an API and then
deploy the tomcat-impl to tomcat's lib folder, the jetty-impl to jetty's lib
folder the websphere-impl to websphere's lib folder) Your war then picks up
the required impl when deployed to any container
3. Coding to the spec (not always as hard as you might think)
-Stephen
On 30 August 2010 12:22,<[email protected]> wrote:
I think you'll find overlays as a smaller solution than adding in
multiple
profiles to support multiple hosts.
The reality is you should be abstracting out these things so that you
don't
need them any more and one universal war is all that is required.
Stephen,
this comment [1] describes my issue.
[1]
http://www.sonatype.com/people/2010/01/how-to-create-two-jars-from-one-project-and-why-you-shouldnt/#comment-44713627
--
Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief!
Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail
---------------------------------------------------------------------
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]
