that still doesn't really fix the header problems when we redirect to a page.
The only real fix is to upgrade to 1.2..

johan


On 2/5/06, Juergen Donnerstag <[EMAIL PROTECTED]> wrote:
1.1 should already have getOriginalResponse() to solve the problem

Juergen

On 2/5/06, Dan Gould <[EMAIL PROTECTED]> wrote:
> I'm getting an exception in Wicket 1.1.  I'd file a bug, but since so much
> of this has already been refactored, I'll just pass it along in case:
>
> During Page.configureResponse, I try to call RequestCycle.getWebResponse()
> and Wicket throws a ClassCastException.  Apparently, it replaces the
> WebResponse with its own class internally (WebRequestCycle$1), at least
> when it's using RENDER_TO_BUFFER.
>
> I want it so I can call setHeader.
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> _______________________________________________
> Wicket-user mailing list
> Wicket-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wicket-user
>


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmdlnk&kid3432&bid#0486&dat1642
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to