|
midrange.com
Same here. Our properties needs to be different on our test box and live
box - and our testing standards dictate that the WAR/EAR file we deploy
onto the test box must be identical to the WAR/EAR file that we deploy onto
the live box. If you are doing things like putting your application onto a
test server, then modifying the WAR file (by modifying the properties file
within it) and then that deploying onto a live server... then you haven't
really tested the same WAR file as you're deploying live.
Regards,
Nigel Gay,
Computer Patent Annuities.
"Clapham, Paul"
<pclapham@core-ma
rk.com> To
Sent by: "Java Programming on and around the
java400-l-bounces iSeries / AS400"
@midrange.com <java400-l@xxxxxxxxxxxx>
cc
01/11/2005 13:54 Subject
RE: Properties Files vs. War/Ear
files
Please respond to
Java Programming
on and around the
iSeries / AS400
<java400-l@midran
ge.com>
I don't know if this is considered kosher, but I put those properties in a
predetermined location outside the web application.
PC2
-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx
[mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of Walden H. Leverich
Sent: November 1, 2005 09:01
To: Java Programming on and around the iSeries / AS400
Subject: Properties Files vs. War/Ear files
All,
If I understand the concept correctly, one should put their "softcoded"
things into a properties file. This could be connection strings (if you're
not using WebSphere data sources), Web Services addresses, URLs you access
that are different between test and production, etc.
Now, the properties file is "wrapped" into the WAR file that's deployed to
websphere. So, once deployed you go into the properties file and make your
changes? Am I good so far? If so, what's the process for deploying updates?
If I re-deploy the WAR file then I'll overwrite the properties file, so I
have to make my changes again?
Is there a way to exclude the properties file from the WAR and have WS
leave it on the server?
--
This is the Java Programming on and around the iSeries / AS400 (JAVA400-L)
mailing list
To post a message email: JAVA400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/java400-l.
********************************************************************************
The information in this message is confidential and may be legally
privileged. It is intended solely for the addressee; access to this
email by anyone else is unauthorised.
If you are not the intended recipient: (1) you are kindly requested
to return a copy of this message to the sender indicating that you
have received it in error, and to destroy the received copy; and (2)
any disclosure or distribution of this message, as well as any action
taken or omitted to be taken in reliance on its content, is prohibited
and may be unlawful.
********************************************************************************
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
