do you want to avoid serialization or deserialization (you talk about
Session.getPage() and thats deserialization)
But deserialization will not happen because the active page is stored in
memory,
Serialization does happen at the end of a request to store the actual
content of the page, so that late
No, I want to process these requests in context of existing original
page instance, but without page serialization.
Standard processing of ajax requests is implemented in
WebRequestCycleProcessor class, in method resolve(). This method is
called with RequestParameters instance which is only pa
so for that ajax request you do want to create a new page every time the
ajax request hits?
2010/4/19 Martin Schayna
> I have pretty stateful page with plenty of AJAX components. Most of these
> components have behaviors, which renders JavaScript code for calling AJAX
> requests to Java code. B
I have pretty stateful page with plenty of AJAX components. Most of
these components have behaviors, which renders JavaScript code for
calling AJAX requests to Java code. Because page isn't stateless, each
request causes serialization of page. So far so good.
But some of these AJAX requests do
