[
https://issues.apache.org/jira/browse/WICKET-4163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418187#comment-13418187
]
Matthias Keller commented on WICKET-4163:
-----------------------------------------
I still (or again?) get this in Wicket 1.5.7 when using setRedirect on a
mounted page at least. There the new page is created and stored and the user is
redirected to mypage?2 for example. Upon handling this URL, this WARN is issued
every time!
> BufferedResponseMapper doesn't recognize the the stored response because the
> session id is not available
> --------------------------------------------------------------------------------------------------------
>
> Key: WICKET-4163
> URL: https://issues.apache.org/jira/browse/WICKET-4163
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5.2
> Reporter: Martin Grigorov
> Assignee: Martin Grigorov
> Fix For: 1.5.3
>
>
> WebPageRenderer logs a warning that there is a stored response but it wasn't
> picked by BufferedResponseRequestHandler:
> WARN - WebPageRenderer - The Buffered response should be handled
> by BufferedResponseRequestHandler
> The problem is in
> org.apache.wicket.request.mapper.BufferedResponseMapper.getSessionId() which
> was wrongly optimized to not create a new Session with
> http://svn.apache.org/viewvc?view=revision&revision=1186125
> Workaround until 1.5.3 is released:
> MyApplication#init() {
> mount(new BufferedResponseMapper() {
> protected String getSessionId()
> {
> return Session.get().getId();
> }
> });
> }
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
