Re: Updating Nested To-Many Relationship *NOT SOLVED*
Re: Updating Nested To-Many Relationship *NOT SOLVED*
- Subject: Re: Updating Nested To-Many Relationship *NOT SOLVED*
- From: Ken Anderson <email@hidden>
- Date: Wed, 11 Apr 2007 15:01:16 -0400
This is one of Jerry's reponses:
http://lists.apple.com/archives/webobjects-dev/2005/Jul/msg00509.html
You can go to lists.apple.com and pretty much search your heart out.
What Chuck is suggesting happening is that you have something on your
page (like a WOConditional) that's state is bound to something that
is changing. When the form post comes back, WO tries to match up the
structure of the page to get all the values out, and it effectively
'gets lost'. What I usually do is have hyperlink or submit actions
modify temporary variables that are not referenced during page
creation. Then, I override appendToResponse() in the component and
update the real data from the temporary variables. This way, you
guarantee that your page structure is the same.
Ken
On Apr 11, 2007, at 2:47 PM, David Avendasora wrote:
Okay, I'm having a hard time finding the info by googling for it.
Any chance of a link?
Thanks,
Dave
On Apr 11, 2007, at 11:16 AM, Ken Anderson wrote:
You can look for my prior postings too... I've even written up a
decent solution a couple of times... :)
On Apr 11, 2007, at 12:07 PM, Chuck Hill wrote:
Paging Mr. Walker, Mr. Jerry Walker. Mr. Jerry Walker, please
come to the WO List. :-)
This is one of Jerry's most favored rants. I am pretty sure that
what is happening is that you are modifying the structure of the
page while it is processing the takeValues phase. Search for
some of Jerry's past postings on this for the cause and solution.
Chuck
_______________________________________________
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