[
https://issues.apache.org/jira/browse/WICKET-5814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14384751#comment-14384751
]
Martin Grigorov commented on WICKET-5814:
-----------------------------------------
The problem is that the page is rendered and stored for rendering after
redirect (REDIRECT_TO_BUFFER strategy).
But after the redirect BufferedResponseMapper is not used but the page is
re-rendered again, the feedback message is already marked as rendered in the
first request and thus doesn't appear in the second page render.
> CryptoMapper clears feedback messages
> -------------------------------------
>
> Key: WICKET-5814
> URL: https://issues.apache.org/jira/browse/WICKET-5814
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 6.18.0
> Reporter: Guy Wuyts
> Assignee: Jesse Long
> Attachments: cryptomapper_quickstart.tar.gz
>
>
> Wicket 6.18 breaks the behaviour when using a CryptoMapper:
> the feedback messages are cleared for pages that don't use the
> CryptoMapper.
> This was added to WicketApplication.init():
> mountPage("page1", Page1.class);
> setRootRequestMapper(new CryptoMapper(getRootRequestMapper(), this));
> mountPage("page2",Page2.class);
> Page1 and Page2 contain both a form and a FeedbackPanel.
> With Wicket 6.17 there are no problems. When using Wicket 6.18, no
> feedback messages are displayed on Page2.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
