You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Robert Niestroj (JIRA)" <ji...@apache.org> on 2013/02/06 11:11:14 UTC
[jira] [Commented] (WICKET-4163) BufferedResponseMapper doesn't
recognize the the stored response because the session id is not available
[ https://issues.apache.org/jira/browse/WICKET-4163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13572307#comment-13572307 ]
Robert Niestroj commented on WICKET-4163:
-----------------------------------------
Got the same error on Wicket 6.5.0. Dont know where it come from. Maybe i will have to revert on SVN revision by revision to find out what wrong. Clearing browser cache doesnt change anything. Closing browser changes. When i click an ajax link or sth like that the first time the request goes to the server but nothing happens. Second time it then works ok.
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira