On 26 Aug 2006, at 06:48, Mike Schrag wrote:
Any examples of the dirty way? I'll check the backlog of emails as
well.
Assuming your EO's are in the same project as your Application,
there really isn't anything you need to do except import your
Application class and call the method. There's nothing
particularly special about Application compared to any other Java
class.
Ahem.
Application application = (Application)WOApplication.application();
I take in a lot of settings via both the Properties file, and
settings files that I load (from plists or xml; the latter sucks
harder). But so far I have avoided doing this from the model layer,
as it goes against MVC principles. One technique to use is to create
class (sorry, static) methods in your model class for these
properties, and call them from your application constructor. That
way you don't have to feel guilty.
Paul
_______________________________________________
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 archive@mail-archive.com
