Re: Best Approach Question
Re: Best Approach Question
- Subject: Re: Best Approach Question
- From: steve stout <email@hidden>
- Date: Tue, 16 Mar 2004 11:34:38 -0700
What I would suggest is that you create another class that controls
when your EOs are created and saved. Probably implement it as a
singleton and is attached to the user's Session object. So the first
time someone goes to the wizard, the Session is asked for it's
WizardContext (or WizardController). It's worked well for me, and
takes care of having to pass off EOs from one component to another.
And it abstracts it from having to put all your code in the Session.
.steve
On Mar 16, 2004, at 10:44 AM, James Cicenia wrote:
Hello -
I am developing a wizard which has three pages with the usual
next and previous buttons. When I call this wizard from one of
my pages I will obviously instantiate a new object. I was doing this
on the first page constructor but realized that if they went back to
that
page with the previous button it would create a new instance again.
So I figure that I would instantiate the object from the calling page.
There also needs to be created a new object which is related with
a one-one relationship. Since both objects are brand new will the
EO take care of the relationship ? Do I just simply use the
addObjectToBothSidesOfRelationship method?
Thanks
James Cicenia
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.
///---------------------------------------
steve stout
web coordinator
arizona student unions
52o.626.o1o9
http://www.union.arizona.edu
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.