Re: Model/application development layout request for comment
Re: Model/application development layout request for comment
- Subject: Re: Model/application development layout request for comment
- From: Kieran Kelleher <email@hidden>
- Date: Mon, 02 Apr 2012 11:43:05 -0400
You could have 10 Properties files ...
Properties.config01
Properties.config02
Properties.config03
etc.
And then in WOMonitor (or even development launch arguments, just specify the property extension as the java "user name", in which case ERXProperties will ensure that the properties in that file override all other Properties files. For for a deployed app that you want to run with Properties.config01, just add this in WOMonitor:
-Duser.name=config01
On Apr 2, 2012, at 10:16 AM, Dev WO wrote:
> Hi WOmates,
>
> I'm actually rewritting a project to make it more "multiple configuration" aware.
>
> I need to define a little more the "multiple configuration" setup:
> -the same code-base will have about 10s different configurations (like language setup and custom UI layout)
> -each configuration would serve in the range of 100s (maybe 1000s) users
>
> My original idea was to create a single project in Eclipse and have a build.xml file for each configuration (providing the language(s), the database connection details, etc), that way I could have a specific database for each configuration and be able to update based on the configuration (like if configuration are used on different timezone, I can have a more optimized downtime window), in addition to isolate the data for each configuration.
>
> I haven't completely look into the build.xml to see if I could use it to achieve "per built" Properties and includes for example.
>
> But do you think it's the way to do it or is there a better way to manage this, mostly on the maintenance and future development perspective (having a single project seams pretty interesting to me)?
>
> It shouldn't really matter for now, but it would also be my first move into D2W;)
>
> Thanks for your comments,
>
> Xavier
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden