Hi,

I have pretty statefull 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 doesn't change page ever, so serialization of page isn't necessary. For example it is forward caching data for (home-brewed) datagrid component. These requests are calling continuously and serialization of page during each request causes delays.

There are some projects for stateless wicket components out there (e.g. wicket-stateless, http://code.google.com/p/jolira-tools/), but it solves another situation -- request of stateless components are processed on new instances of pages. I want to process it on existing page instance but without its serialization.

I have tried to implement semi-stateless behaviors in own RequestCycleProcessor.resolve(), but I hung on searching for page from requestParameters -- Session.getPage() always touches page and it causes serialization after request processing.

Is there any example, idea, whatever for implementing this in Wicket?

Hope it's understandable :)

Thank you, Martin Schayna

Reply via email to