You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2014/04/23 08:18:23 UTC

[jira] [Resolved] (WICKET-5566) "Catch-All" FencedFeedbackPanel has lost message in case of message-level filter in nested FencedFeedbackPanel

     [ https://issues.apache.org/jira/browse/WICKET-5566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Grigorov resolved WICKET-5566.
-------------------------------------

    Resolution: Won't Fix

> "Catch-All" FencedFeedbackPanel has lost message in case of message-level filter in nested FencedFeedbackPanel
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: WICKET-5566
>                 URL: https://issues.apache.org/jira/browse/WICKET-5566
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 6.14.0
>         Environment: Windows 2008 Server, Java 7u45 x64, Glassfish 3
>            Reporter: Alexander Morozov
>            Assignee: Igor Vaynberg
>         Attachments: myproject.zip
>
>
> We have almost successfully use FencedFeedbackPanel feedback, until we enable ErrorLevelFeedbackMessageFilter in nested FencedFeedbackPanels. Here is page structure:
> FencedFeedbackPanel ("catch-all", fence=null)
>   Panel1 (with form)
>     FencedFeedbackPanel (fence=Panel1) + ErrorLevelFeedbackMessageFilter(accept ERROR level or higher) 
>   Panel2 (with form)
>     FencedFeedbackPanel (fence=Panel2) + ErrorLevelFeedbackMessageFilter(accept ERROR level or higher) 
> The issue: catch-all FencedFeedbackPanel doesn't show "success" messages, added by submit links in Panel1 or Panel2, hence messages had lost. Are there any solutions for the issue?
> See also http://apache-wicket.1842946.n4.nabble.com/quot-Catch-all-quot-FencedFeedbackPanel-and-message-level-filter-in-nested-FencedFeedbackPanel-td4665515.html



--
This message was sent by Atlassian JIRA
(v6.2#6252)