+1
Am 17.09.13 17:18, schrieb Michael Haitz:
Hi,
why do you need a special API using IModel instead of Serializable?
wicket-bootstrap uses also models but with existing API, isn't this enough?
check NotificationPanel, NotificationAlert and NotificationMessage:
https://github.com/l0rdn1kk0n/wicket-bootstrap/tree/master/bootstrap-core/src/main/java/de/agilecoders/wicket/core/markup/html/bootstrap/common
cheers,
Michael
Am 17.09.2013 um 16:49 schrieb Rafael W.
<[email protected]<mailto:[email protected]>>:
Hello everybody,
I would like to put https://issues.apache.org/jira/browse/WICKET-5353 to
dicussion. Attached, you can find an example of a Wicket application that would
benefit from that change. (Simly run wicket-async-task-demo with jetty:run in
Maven.)
Generally, I want feedback messages to be represented by models rather than by
Serializables in order to allow more multithreading in Wicket. The example
contains a simple progress bar component where tasks are run in background
threads in order to keep the Wicket application responsive. (I mostly use
Wicket in Desktop-style applications where the attached component is
tremendously useful for me.)
The problem with the Serializable solution for feedback messages is that the
messages have to be assembled at the time the error occurs, not at the time the
message is to be displayed. In my believe, this is a misconception that can
easily be corrected. I described the topic further in the Jira issue above.
Thank you for your feedback.
Regards, Rafael Winterhalter
<wicket-async-task.zip>
