On 8/22/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > you have to create your own custom feedback filter. this is simply how > wicket feedback works. it is stored per page, and if you want to filter it > you have to do it inside the panel.
Still, using these filters is a bit clumsy imo. I can see Matt's case where you want to couple feedback panels to forms and let that print out the messages for only these forms, and whatever is left after that can be rendered by other feedback panels. In fact that would be a lot better than what we have now; how helpful is it anyway to have multiple feedbackpanels rendering out the same messages?. Only rendering messages for a form is possible using ContainerFeedbackMessageFilter, but the rest of the case... is not really possible in a simple fashion unless I'm overlooking something. Note that this case was actually what I tried to achieve 1.5 years ago or such with feedback boundries (though that had it's own problems, so I'm not arguing to get that back). Improving upon the current situation could work roughly like this: updateFeedback is done post order, and the implementations should mark feedbackmessages as accepted or something (IFeedbackMessageFilter would best be converted to an abstract class then so that we can guarantee marking the messages). When messages are marked, other components may choose to ignore them. If FeedbackPanel would work that way, we'd have Matt's behavior out-of-the-box, which imho is a lot better than the current way that feedbackmessages just print out any messages regarless whether they already were consumed by another feedback panel. WDYT? Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
