You can enlarge your update container to the entire form and use it for many update trigger. I usually use them like this.
When an AjaxUpdateContainer refresh it's content, the appendToResponse of the component containing the AjaxUpdateContainer is not called but all the refreshed sub component behave normally including the call to appendToResponse.
Keep in mind the update container create a div by default (it need a container element), this is probably why it did not worked the first time you tried. You can create another element type by specifying the elementName binding to create a TR for example.
Samuel
Le 2015-03-09 à 15:55, Calven Eggert <
email@hidden> a écrit :
that worked! Thanks!
However, how can I deal with this when I have a field that is only shown based on a woconditional? Like so...(BTW, this gives the same original problem with the phantom field at the top of the page)
<WEBOBJECT NAME=UpdateComponent>
<WEBOBJECT NAME=ShowConditional><WEBOBJECT NAME=SiteOfDiseasePopUpButton></WEBOBJECT></WEBOBJECT>
If I put the UpdateComponent in the ShowConditional then obviously if the ShowConditional is false then the UpdateComponent does not exist on the page.
<WEBOBJECT NAME=ShowConditional>
<WEBOBJECT NAME=UpdateComponent><WEBOBJECT NAME=SiteOfDiseasePopUpButton></WEBOBJECT></WEBOBJECT>
Calven
On 2015-03-09, at 12:54 PM, Theodore Petrosky wrote:
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