Hi Sven,
it is true that you should be careful with manipulating the view from
background threads as with any UI model. However, if you look at
FeedbackMessages.add(FeedbackMessage) you will see that this method is as a
matter of fact synchronized in its implementation. The asynchronous appoach
works therefore fine in practice. We run the implementation in a production
environment and never experienced problems. This is of course, because we
abort all asynchronous threads once an error occurs and the feedback
messages might be read.
However, I agree, that a scheduling model as in Swing would be nicer but as
far as I know, there is no such thing in Wicket.
Best, Rafael
