On Tue, Jan 31, 2012 at 2:16 PM, kamiseq <[email protected]> wrote: > I dont know if the conversation you pointed to can explain anything > for this question;]
OK, then it is not clear. Ajax behavior needs to be stateful to be able to find the page that it has to update. By being stateful the behavior makes the whole page stateful and thus this page is stored in the page store at the end of the request cycle. To be able to store it Wicket needs the session id. Later when an Ajax call fires the same session id is used to find this page instance in the store, then find the component with the Ajax behavior in that page and execute the callback method (onEvent, onClick, etc.) Jolira's Ajax behaviors by being stateless do not store the page and thus they recreate a new page instance for each Ajax call. But instead of rendering the whole page only the components added to the AjaxRequestTarget are rendered and delivered back. Is it more clear now ? > > I can only guess that if you make ajax call and you already have page > created then it is faster, from what I know solution like jolira > creates new page and whole component tree over and over again on each > ajax call. > > pozdrawiam > Paweł Kamiński > > [email protected] > [email protected] > ______________________ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
