On 21.08.08 02:55, "Simon McLean" <[EMAIL PROTECTED]> wrote:
> If we need to set a property and make absolutely sure that it doesn't > get replaced by another framework, or even the application itself, we > put it in WebObjects.properties. If i remember correctly, the > WebObjects.properties are always the very last properties to be read > in, so using it also prevents you from suffering from framework > ordering. The WebObjects.properties is the biggest piece of shit ever invented as it gets read by every freaking project no matter what and you still have to take care to get your settings into the production app. It's like a rocket launcher for hunting butterflies ... kills everything without even noticing you killed more than you wanted. If you only have one project, that might be okay for you, I currently deal with around 20 applications in various development stages (company work, private work and some old contracting stuff) - I can't work with that file. Normally I define most of my properties in the Application, but some are in frameworks (especially for my D2W setup). And if then a new version of third party framework suddenly also declares that same property and it is read before yours ... your app might end up with not loading any D2W rule files anymore which makes it pretty much unusable. Didn't take long to find, but nevertheless killed my production app for 10 minutes until I found what it was. Fortunately, it wasn't a busy app but something that is only accessed during office hours. Maybe I should add another Mac Mini (production is a Mac Mini) as a staging server for testing ... ;-) cug _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
