Hi Guido -
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.
Simon
On 21 Aug 2008, at 06:35, Guido Neitzer wrote:
Something I just stumbled into and want to let you know, so you might
remember reading about what the problem could be:
If you override a property in a framework (e.g. your own framework),
which
is also _set_ in another framework (e.g. Wonder, ...) and it works
on your
local Eclipse but doesn't work in deployment, you might have the re-
ordered
the classpath in Eclipse and still end up with a different classpath
in the
deployed application.
Rule of thumb for me now:
Override properties, that are set in ANY (non-system) framework in the
application itself if you have to override it at all because that
way you
know it will definitely override the property from any framework
regardless
of any ordering of the frameworks.
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/simon_mclean%40mac.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
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]
