Mind you, this does not keep you from just setting -
DdbConfigNameGLOBAL=whatever in Monitor, you can still do that. But
the input field in there totally sucks for a more complex config.
That's why it's better to put the stuff in Properties.sometype files
(which are btw a Wonder-only feature).
Cheers, Anjo
Am 11.04.2008 um 06:02 schrieb Chris Meyer:
Right... OK, I'm going to setup the properties as suggested by Anjo.
Thanks for the info (from both of you). Very helpful!
On Thu, Apr 10, 2008 at 8:45 PM, Mike Schrag
<[EMAIL PROTECTED]> wrote:
It just loads from a property, so like any property you can set it
in monitor or Properties. Any property appearing in Properties can
be passed in as a -D setting as well from Monitor. Anjo's
suggestion is really a good one, though. I have totally switched to
what he's showing. What Anjo is showing is that you can setup a
Properties file for each deployment configuration
(Properties.staging, Properties.production), and then all you have
to do is specify which deployment config to use in monitor and you
can ore easily track of your multiple configurations with version
control, etc. You really don't want to have a lot of settings in
Monitor, because it's obnoxious to keep track of them, and Monitor
(or wotaskd -- I'm not sure which of them actually writes the file)
has a great habit of destroying the SiteConfig.xml when you least
expect it.
ms
On Apr 10, 2008, at 11:37 PM, Chris Meyer wrote:
Is there any technical reason why the active config couldn't be
selected in JavaMonitor? Seems like that would be a nice place for
it...
On Thu, Apr 10, 2008 at 1:07 AM, Anjo Krank <[EMAIL PROTECTED]>
wrote:
I normally (ab)use the property-per user feature as a launching
flag in monitor, i.e. start my app with -Duser.name=deployment, -
Duser.name=staging etc and have Properties files named accordingly
Properties.deployment, Properties.staging etc. where all the values
that are different from Properties are set. The value you want is
dbConfigNameGLOBAL or MyModel.DBConfigName.
Cheers, Anjo
Am 10.04.2008 um 08:37 schrieb Chris Meyer:
I'm sure this is a simple question but I can't find the answer
after searching the internet.
How does one specify the active configuration for a model during
deployment of a webobjects application?
During development, I can just use WOLips to edit the model and
change the active configuration. But is there a way to
automatically specify what configuration should be used when I
build the deployment build (instead of doing it by hand)?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list ([email protected]
)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/krank%40logicunited.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list ([email protected]
)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/mschrag%40mdimension.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list (Webobjects-
[EMAIL PROTECTED])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/cmeyer1969%40gmail.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list (Webobjects-
[EMAIL PROTECTED])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/krank%40logicunited.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
