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.
-igor On 8/22/07, Watter <[EMAIL PROTECTED]> wrote: > > > I've searched for and read a number of threads on using multiple feedback > panels on one page. I'm struggling with the same thing, but I haven't seen > a > response that is directly on point to my problem. We want to have a > feedback > component on our main page that most of the other pages in the application > extend. This would be present to display any truly unexpected errors and > the > occasional feedback message related to things that happen in our menus or > in > our global search box (an "invalid search query" message for example). We > also need to have a specific feedback panel for the forms that we use in > our > app. It's very easy to restrict what gets shown in that second feedback > panel. We either add a ComponentFeedbackMessageFilter or use the > convenience > class, ComponentFeedbackPanel. The problem is that the page level feedback > panel is catching the messages for the form level component as well. > > I'm not sure how to go about solving this. I'm reluctant to put some > arbitrary filters on the page level feedback as it's intended to be a > catch-all for things we don't expect (there's some AOP advice around our > service tier calls that wrap exceptions and deliver them to this > component). > > Any ideas? > > Matt > -- > View this message in context: > http://www.nabble.com/Page-and-compoenent-level-feedback-are-mixing-together-tf4314782.html#a12285394 > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
