Here's my comment (copied from my comment on the PR). Note that I whipped up the gist quickly, so it may not compile, but it shows the intent.
I don't think we need this PR. It could easily be accomplished by overriding newMessageDisplayComponent or by the following change: https://gist.github.com/jthomerson/6595716 On Tue, Sep 17, 2013 at 10:49 AM, Rafael W. <rafael....@web.de> wrote: > 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 > > -- Jeremy Thomerson http://wickettraining.com
