Hi,
You can use
ListStringValue values = PageParameters.getValues(operations);
Then use this List as a Model for a ListView where each ListItem will add a
TextField for the operation.
Don't forget to call listView.setReuseItems(true)
Martin Grigorov
Wicket Training and Consulting
On Tue, May
That's nice and this is exactly what I do.
But I start my job from init method of my Application class and there is no
RequestCycle there at initialization time. I suppose that because there is
no request has been sent to Application yet. (Nobody uses the application
because it just started).
I
The answer is: create the request cycle yourself
On May 21, 2014 11:01 AM, Sandor Feher sfe...@bluesystem.hu wrote:
That's nice and this is exactly what I do.
But I start my job from init method of my Application class and there is
no
RequestCycle there at initialization time. I suppose that
Hello,
I am using dataview form sorting and pagination
and observed that data in dataview is not refreshed properly
previously i used Listview with set reuseitem=false and it was working
properly
and now after use of dataview its not behaving properly
I looked into sourcecode of ListView
do
Hi,
please take a look at #setItemReuseStrategy(IItemReuseStrategy)
Sven
On 05/21/2014 03:11 PM, pradeepmohite07 wrote:
Hello,
I am using dataview form sorting and pagination
and observed that data in dataview is not refreshed properly
previously i used Listview with set reuseitem=false and
Hi,
I have a form with several question that a user must answer. If the answers
are correct, an email is sent to the user and the user is returned to the
login page. That's a bit abrupt for the user and I would like to provide a
simple modal dialog that confirms that the email is sent before
Hello, I've got a problem that I've just noticed today: When an instance
of a WebPage is created with some url parameters, the PageParameters
object is never updated, that is, if I refresh the same webpage with
different url parameters this won't be taken into account, instead the
first params
Hi,
This is fixed in Wicket 7.x. We didn't apply the fix to 6.x because it is a
behavior change.
You can read the current parameters in #onConfigure() with
getRequestCycle().getRequest().getRequestParameters() and override with
them the page's parameters (page.getPageParameters())
Martin
