Thanks Martin. That's very helpful and inspiring.
That said, I now think, from web clustering's point of view, it might not be
a bad idea to just cluster the page store (which is now in clustered cache)
and disable the application scoped cache. (See
Hi,
You can create your own IPageManagerProvider that extends from
DefaultPageManagerProvider and overrides its #getPageStore() method [1]
Then set it in YourApp#init(), like at [2]
1.
Hi, I'm trying to cluster Wicket web application. I'm using Wicket 6.x.
In terms of the page store, in our system, all servers now share the http
sessions, while the persistent store is still set to be disk files. (We
prefer not to put persistent store into the session, otherwise the session
size
Hi,
I'm assuming you're using Ajax, so you should update the whole row after
your behavior/component has changed the field.
Each row item has to output a markup id, e.g. you can use a custom Item
subclass that calls #setOutputMarkupId(true):
protected Item newRowItem(final String id,
Hello,
I'm using wicket 7.5.
I have a DataTable, where one of the columns is an input textfield with a
clickable icon near it. When providing data for the input field, and
clicking the icon, some validations are done, and the fields for other
columns should be updated accordingly.
However they
Thanks for sharing. I just added a couple of comments/
On Wed, Nov 9, 2016 at 4:23 AM, Maxim Solodovnik
wrote:
> Hello Martin,
>
> sorry for the delay
>
> here is the repo: https://github.com/solomax/wicket-ajax-download
> here is the commit with the