Issue opened here: https://issues.apache.org/jira/browse/WICKET-5933
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Is-it-possible-to-avoid-serialization-of-page-after-ajax-request-tp4671295p4671331.html
Sent from the Users forum mailing list archive at Nabble.com.
the page is indeed not deserialized, but received from http session, but it
looks like we cannot avoid the serialization.
Our application doesn't touch the page, but the AbstractPageManager does:
*
IManageablePage page = getRequestAdapter().getPage(id);
if (page != null)
{
Here is a quickstart
http://apache-wicket.1842946.n4.nabble.com/file/n4671326/wicket-touch.zip
that demonstrates the performance impact. There is a
ExperimentalPageManagerProvider configured in the WicketApplication that
makes ajax polling requests about two times faster.
Something similiar has
We run into a disc and cpu bottleneck on a wicket page with 1+ users,
that uses ajax updates via polling (AjaxSelfUpdatingTimerBehavior).
The result of our investigation is that page store needs about 10ms for
serialization, while the framework serializes and deserializes the same data
again
Looking for a smart way to integrate wicket with extjs
(http://www.extjs.com) i wrote a small piece of code, that can be used
to generate javascript function-calls.
The idea is to rewrite the public api of the javascript library in
java. Everytime you call one of these java-functions a equivalent
Marieke Vandamme schrieb:
Hello,
Is it possible to use TabbedPanel from wicket extensions together with the
wicket auth-roles?
Because TabbedPanel contains AbstractTab (which do not extend Component), I
didn't find a way to set the specific roles for each tab.
Thanks !
Hello,
AbstractTab
