Re: Ajax Framework Bug?
Re: Ajax Framework Bug?
- Subject: Re: Ajax Framework Bug?
- From: Pascal Robert <email@hidden>
- Date: Mon, 26 Nov 2012 14:50:38 -0500
Le 2012-11-26 à 14:43, Johnny Miller <email@hidden> a écrit :
> Hi Pascal,
>
> I spent some time trying to figure it out but it's pretty complicated. If you have an AjaxUpdateLink updating an AjaxUpdateContainer it works as you would expect. But if your AjaxUpdateContainer is inside of a form the ERXAjaxApplication.takeValuesFromRequest calls super.takeValuesFromRequest and it takesValuesFromRequest for the whole component not just the bits the AjaxUpdateContainer cares about. On an AjaxUpdateLink it does not call super.takeValuesFromRequest in ERXAjaxApplication.takeValuesFromRequest so that's why it doesn't process the component again.
>
> As far as I can see this is how it worked in previous version of Wonder so I'm beginning to suspect that I changed something and this is just the way it always worked?
I guess it's how it always worked, because I went back to a version of Wonder from last year and I still get the same behaviour for my problem.
> But to answer your question. Yes, the Ajax request just returns the contents that I would expect.
>
> Aloha,
> Mr. Johnny Miller
> Web Development Manager
> Kahalawai Media Company
> Lahaina, HI 96761
> tel: (808) 661-7962 | mobile: (808) 283-0791
> website | e-mail
>
> On Nov 23, 2012, at 1:52 PM, Pascal Robert <email@hidden> wrote:
>
>> That sounds a lot like the problem I have where I tell it to update only a cell but the whole table is reloaded. This is happening when if the Ajax request only send back the row that is updated, but after the response is generated, the whole table is reloaded.
>>
>> Can you confirm that the Ajax is only sending back the area you want to be updated?
>>
>>> Hi,
>>>
>>> I recently updated my Wonder Frameworks and I have a question about something I am seeing.
>>>
>>> One of my components broke and I'm thinking that either I misunderstand something or something in Ajax Framework has now changed.
>>>
>>> Given the following example:
>>>
>>> <wo:form>
>>> <wo:popUpButton list = "$arrayOfStrings" selection = "$selectedString" id = "StringSelector"></wo:popUpButton>
>>> <wo:AjaxUpdateContainer observeFieldID = "StringSelector">
>>> <wo:WOKeyValueConditional key = "selectedString" value = "String Two">
>>> String Two Is Selected
>>> </wo:WOKeyValueConditional>
>>> </wo:AjaxUpdateContainer>
>>> </wo:form>
>>> <wo:repetition list = "$someOtherArrayOfStrings" item = "$aString"><br/>
>>> <wo:str value = "$aString" />
>>> </wo:repetition>
>>>
>>>
>>> I would assume that when the value of the pop up button changes only the contents of the AjaxUpdateContainer would get touched. However, if I put a logging statement on someOtherArrayOfStrings I can see that it gets called. It's like it is processing the whole component all over again.
>>>
>>> Is that the way it is supposed to work or has a bug been introduced?
>>>
>>> Aloha,
>>> Mr. Johnny Miller
>>> Web Development Manager
>>> Kahalawai Media Company
>>> Lahaina, HI 96761
>>> tel: (808) 661-7962 | mobile: (808) 283-0791
>>> website | e-mail
>>>
>>> _______________________________________________
>>> 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
>>
>
_______________________________________________
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