I'm very sorry I wasn't clear enough. I assumed the mechanism you just
explained in detail now, thanks for clarifying it. The thing is that the
response from my the server was empty, it had nothing at all. Not even an
empty JSON structure.
I'm only wondering, where did the response indicate the link to redirect to
if there is no JSON response ? Or does chrome's developer-tools fail to
catch the JSON response for this case ?
I adjusted chrome to "Preserve Log Upon Navigation" as not to lose
request\response logs between page navigation.
On Tue, Nov 20, 2012 at 1:59 PM, Ivan Khalopik <ikhalo...@gmail.com> wrote:
> Select component with enabled ajax posts ajax request to the server-side.
> Then server-side dispatches it to correspondent event handler and it
> returns some value. Then this value goes to correspondent
> ComponentEventResultProcessor and generates response markup. Then this
> markup goes to client-side where ZoneManager refreshes zone.
>
> In other words if you will return page class from your select
> onValueChanged event handler, AjaxPageClassComponentEventResultProcessor
> will produce json response like this:
> {
> ...
> redirectURL: some/application/refresh/page/link,
> ...
> }
>
> Then ZoneManager on client-side gets this redirectURL property and:
>
> if (redirectURL) {
> window.location.href = redirectURL;
> return;
> }
>
>
> On Tue, Nov 20, 2012 at 2:06 PM, Muhammad Gelbana <m.gelb...@gmail.com
> >wrote:
>
> > I'm trying to understand how an ajax-enabled Select component can reload
> a
> > whole page. Using chrome, I logged the Select component's post and there
> > are my logs:
> >
> >
> > 1. Request URL:
> > http://localhost/ixload/configuretest.testtypefield:change
> > 2. Request Method:
> > POST
> > 3. Status Code:
> > 200 OK
> > 4. Request Headersview parsed
> > 1. POST /ixload/configuretest.testtypefield:change HTTP/1.1 Host:
> > localhost Connection: keep-alive Content-Length: 38 Origin:
> > http://localhost X-Prototype-Version: 1.7 X-Requested-With:
> > XMLHttpRequest User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64)
> > AppleWebKit/537.11 (KHTML, like Gecko) Chrome/23.0.1271.64
> > Safari/537.11
> > Content-type: application/x-www-form-urlencoded; charset=UTF-8
> > Accept:
> > text/javascript, text/html, application/xml, text/xml, */*
> > Referer: http://localhost/ixload/configuretest
> > Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8
> > Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie:
> > JSESSIONID=ogvmp393aemps4uvserib6q2
> > 5. Form Dataview URL encoded
> > 1. t:zoneid:
> > dummyZone
> > 2. t:selectvalue:
> > 0
> > 6. Response Headersview parsed
> > 1. HTTP/1.1 200 OK Content-Type: application/json;charset=UTF-8
> > Transfer-Encoding: chunked Server: Jetty(6.1.26)
> >
> >
> > I can't see here how did that force the browser to reload the whole page.
> > Would someone please just point out why does this work ? Thank you.
> >
>
>
>
> --
> BR
> Ivan
>
