• 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: Best Practices - Properties files
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Best Practices - Properties files


  • Subject: Re: Best Practices - Properties files
  • From: Lachlan Deck <email@hidden>
  • Date: Fri, 26 Jun 2009 08:53:34 +1000

On 25/06/2009, at 11:59 AM, Tim Worman wrote:

All:

context: I've been wanting to start some threads on simple best practices and maybe get involved in helping with the wiki. From my own work, this seemed as good a place to start as any.

--------------

I have a project that is pretty recently moved to Wonder. From searching list posting and blogs I have seen mentions of different configurations of Properties files that Wonder will discover and use for database connection stuff, etc. Some of them I hadn't seen mention of elsewhere.

I've recently started using Properties.<username> for doing dev work and keeping passwords in there (and away from my code repository). However, I've also recently seen whisper of a Properties.dev.

Two things I'd like to see:

1. a full concise list of what all the possible Properties files (requiring Wonder or not) and also how the more experienced among us leverage them. If it turns out there are some that don't have great documentation I'll volunteer to update the wiki!!

2. It still seems to me that another Properties file must be inserted at deployment for different db passwords, etc. How do the veterans among handle this? I've seen some deployment scripts around but haven't dug into that stuff yet. I still build very locally and deploy very manually (scp). :-)

<using Wonder>

I define in the application Properties file:
runtime.config.dir=Properties
runtime.config.name=

and:
er.extensions.ERXProperties.OptionalConfigurationFiles=(\
	@@runtime.config.dir@@/log4j@@runtime.config.name@@.properties,\
	@@runtime.config.dir@@/jdbc@@runtime.config.name@@.properties,\
	@@runtime.config.dir@@/runtime@@runtime.config.name@@.properties,\
	@@runtime.config.dir@@/runtime@@runtime.config.name@@.properties,\
	../instance.properties
)

For deployment simply tell JavaMonitor:
"-Druntime.config.dir=../../Properties"

For eclipse launch targets, I can switch between test, nightly backup db environments setting:
-runtime.config.dir "../../Properties"
-runtime.config.name "test" or "dev" or...


with regards,
--

Lachlan Deck


_______________________________________________ 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: 
 >Best Practices - Properties files (From: Tim Worman <email@hidden>)

  • Prev by Date: Re: [Wonder-disc] Best Practices - Properties files
  • Next by Date: Re: [Wonder-disc] Best Practices - Properties files
  • Previous by thread: Re: [Wonder-disc] Best Practices - Properties files
  • Next by thread: WebObjects Jobs in Amsterdam
  • Index(es):
    • Date
    • Thread