• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Model/application development layout request for comment
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Model/application development layout request for comment


  • Subject: Re: Model/application development layout request for comment
  • From: Ted Archibald <email@hidden>
  • Date: Mon, 02 Apr 2012 09:39:35 -0600

Why not just deploy multiple instances with specific property files for each configuration? In your resource folder you could have Properties.config1, Properties.config2 then in the additional args in JavaMonitor you could stick  -Duser.name=config1 then in the next instance you'd have  -Duser.name=config2 .

On Mon, Apr 2, 2012 at 8:16 AM, Dev WO <email@hidden> 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

References: 
 >Model/application development layout request for comment (From: Dev WO <email@hidden>)

  • Prev by Date: Re: Wrong Session class
  • Next by Date: Re: Model/application development layout request for comment
  • Previous by thread: Model/application development layout request for comment
  • Next by thread: Re: Model/application development layout request for comment
  • Index(es):
    • Date
    • Thread