Hi,
It appears that Wicket already has everything I need:
- A global FeedbackPanel for any messages not necessarily associated
with components (a call error(...) displays the message on it)
- An individual ComponentFeedbackPanel for messages belonging to and
displayed in context of components.
My question is: Should I use both on the same page, and if so, how?
When I use both, then an error filtered by a ComponentFeedbackPanel is
also filtered by FeedbackPanel and the error is displayed twice, in
both panels.
I tried to avoid this by:
IFeedbackMessageFilter filter = new IFeedbackMessageFilter(){
public boolean accept(FeedbackMessage message) {
return ! message.isRendered();
}
};
FeedbackPanel feedbackPanel = new FeedbackPanel("feedback", filter);
ComponentFeedbackPanel componenFeedbackPanel = new
ComponentFeedbackPanel("fedbackText", textField);
But this simple approach fails because FeedbackPanel gets the message
before ComponentFeedbackPanel :(
I would rather not add a not-to-do list to FeedbackPanel, as I would
really like to keep this simple. Especially because
message.isRendered() looks useful.
Any ideas?
Many thanks.
Bernard
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
