How do you get those?
Do you also see them when you use the wicket-examples?

On 12/5/05, Gili <[EMAIL PROTECTED] > wrote:

        In WicketServlet.java line 221 we have a "finally" block with
response.close() in it. Consider what happens if the "try" block throws
an exception, the "finally" block is executed and response.close()
throws its own exception: the original exception is lost. (I am guessing
that is what is going on in my case)

        Can you guys rewrite this block so it throws the first exception
encountered and quietly swallows any new ones?

Gili

Gili wrote:
>
>     Old code that used to run fine is now broken after a CVS update of
> Wicket. Here are some stack-traces I see:
>
> 23:45:23,546 ERROR WebResponse:149 - Unable to redirect to:
> /DesktopBeautifierServer/Main?path=2&version=1, HTTP Response has
> already been committed.
> 23:45:23,702 ERROR [Webpage]:260 - Servlet.service() for servlet Webpage
> threw exception
> java.lang.IllegalStateException
>         at
> org.apache.catalina.connector.ResponseFacade.sendRedirect (ResponseFacade.java:423)
>
>         at wicket.protocol.http.WebResponse.redirect(WebResponse.java:157)
>         at
> wicket.protocol.http.BufferedWebResponse.close(BufferedWebResponse.java:66)
>         at wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:221)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java :802)
> [snip]
>
>
> and
>
>
> 23:45:28,906 ERROR WebRequestCycle:170 -
> java.lang.NullPointerException
>         at wicket.Component.getResponse(Component.java:895)
>         at wicket.Page.configureResponse(Page.java:709)
>         at wicket.Page.onRender(Page.java:828)
>         at wicket.Component.render(Component.java:1246)
>         at wicket.Page.doRender(Page.java :271)
>         at
> wicket.protocol.http.WebRequestCycle.redirectTo(WebRequestCycle.java:132)
>         at
> wicket.request.PageRequestTarget.respond(PageRequestTarget.java:59)
>         at
> wicket.request.compound.DefaultResponseProcessor.respond(DefaultResponseProcessor.java:44)
>
>         at
> wicket.request.compound.AbstractCompoundRequestCycleProcessor.respond(AbstractCompoundRequestCycleProcessor.java :66)
>
>         at
> wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:678)
>         at wicket.RequestCycle.step(RequestCycle.java:526)
>         at wicket.RequestCycle.steps(RequestCycle.java :433)
>         at wicket.RequestCycle.request(RequestCycle.java:395)
>         at wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:216)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java :689)
> [snip]
>
>     The second exception (NPE) might be caused by the first. Any ideas
> what's causing this? The only change I am aware of is that I used to use
> NO_REDIRECT in the older release and in the newer release I use the
> default value (which is redirect via buffer or something).
>
> Gili

--
http://www.desktopbeautifier.com/


-------------------------------------------------------
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://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to