Ok. Thanks for the explanation.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Wicket-8-and-servlet-3-1-async-nio-tp4677098p4677128.html
Sent from the Users forum mailing list archive at Nabble.com.
On Thu, Feb 16, 2017 at 9:50 AM, guillaume.mary
wrote:
> Ok. Thanks for the explanation.
>
Welcome!
Now I think there might be a way to implement my use case!
In onClick() the application code can suspend the current thread, start the
slow operation and setup onComplete listeners.
Custom listen
That would be a wonderfull news ! I'm not so comfortable with Wicket
internal architecture so I don't really see how your idea can be
implemented... but seems great.
I can be your beta-tester or even more implement your idea if you explain
me more.
Could it be applyable to scenarii of long-loading
Hi,
The problem is exactly what Jeremy said:
ArrayList list = manageCategory.findUsers(category.getCategoryname());
ArrayList finalList = new ArrayList();
final DataView dataView = new DataView("userTable", new
ListDataProvider(
li
I have the following situation:
- ajax button clicked
- request cycle begins
- the button's onSubmit method is called
- onSubmit method calls setResponsePage
- request cycle continues, *components are initialized*, etc
- request cycle ends with a response that contains an ajax-response redirect
-
Hi,
your situation looks pretty normal.
What do you mean by "are initialized (again)" - #onInitialize() is
called again?
What argument do you pass to #setResponsePage() ?
Have fun
Sven
On 17.02.2017 02:47, gmparker2000 wrote:
I have the following situation:
- ajax button clicked
- reques
