[jira] Reopened: (WICKET-3239) for stateless pages wicket complains with "The Buffered response should be handled by BufferedResponseRequestHandler"

["Martin Grigorov (JIRA)" <ji...@apache.org>]

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

Martin Grigorov reopened WICKET-3239:
-------------------------------------


Reopening the ticket because the current solution has a problem - concurrent usage of the application will break because the key used for stored responses is not unique per session and if two or more users work on the same stateless page then the first one that reads it from the storedResponses will also remove it and then the request will be re-processed.

The first possible solution that comes to my mind is to pass a special parameter with unique value in the URL when redirecting and use that value as part of the key.

> for stateless pages wicket complains with "The Buffered response should be handled by BufferedResponseRequestHandler"
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: WICKET-3239
>                 URL: https://issues.apache.org/jira/browse/WICKET-3239
>             Project: Wicket
>          Issue Type: Bug
>    Affects Versions: 1.5-M3
>            Reporter: Peter Ertl
>            Assignee: Martin Grigorov
>             Fix For: 1.5-M4
>
>         Attachments: WICKET-3239.patch, WICKET-3239.patch
>
>
> when initially rendering a __stateless__ page I get
>   "The Buffered response should be handled by BufferedResponseRequestHandler"
> it's logged by WebPageRenderer#respond(cycle) in line 185 in trunk.
> I don't know if this really is worth a warning, maybe we can just remove it.
> There's also method
>   WebPageRenderer#enableRedirectForStatelessPage()
> which seems to be somehow involved (and still contains a TODO which probably should be resolved before 1.5.0)
> I would like to fix it for myself but don't know much about the background of that warning.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.