Re: IPageRendererProvider - HTTP 500 issue

2014-11-26 Thread Wayne W
Hi Sven, Well that might explain a lot then! We hired someone to do the migration from wicket 1.4 to 6 for us as we didn't have time or the expertise with the latest version. Previously we used : getRequestCycle().setRequestTarget(new RedirectRequestTarget()) and the consultant replaced that

Re: IPageRendererProvider - HTTP 500 issue

2014-11-19 Thread Sven Meier
Hi, I'm not exactly sure what you're trying to do, but the following is just wrong: getRequestCycle().scheduleRequestHandlerAfterCurrent(new RedirectRequestHandler(http://localhost:8080/wicket/bookmarkable/com.mycompany.Foo2?ff=gg;)); This will result in two responses written to the

Re: IPageRendererProvider - HTTP 500 issue

2014-11-18 Thread Wayne W
Hi Sven, Kind of - however its seems to happen only in 6.17. In 6.18 it seems to work ok with the quick start, but with our code base it still happens even with 6.18. I see this fix https://issues.apache.org/jira/browse/WICKET-5689 which seems somewhat related (nested redirects). Its still very

Re: IPageRendererProvider - HTTP 500 issue

2014-11-17 Thread Sven Meier
Can you reproduce the problem in a quickstart? Sven On 11/17/2014 06:46 PM, Wayne W wrote: Hi, We had the requirement that we needed to use RedirectPolicy.NEVER_REDIRECT for a single page in our app . We used this code: setPageRendererProvider(new IPageRendererProvider() { @Override