[jira] [Comment Edited] (WICKET-5435) Ajaxified version of WebSession#getClientInfo should be added

["Ufuk Altin (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WICKET-5435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923653#comment-13923653 ] 

Ufuk Altin edited comment on WICKET-5435 at 3/12/14 10:16 AM:
--------------------------------------------------------------

Sorry to dig this out, but after updateing to 6.13.0 we have some errors. 

We are calling getSession.getClientInfo in onInitialize in our TemplatePage. -The first time, after the server restarts-, we get an "Status 500 - Cannot call sendRedirect() after response has been committed" (see below).

*edit:* Not only the first time. Every time a new browsser (maybe session) connects to  it.

Even when we comment this out we get the exception when we use the DateConverter (as this is somwhere calling getClientInfo as well).
Unfortunatly I could not yet reproduce this on a startup wicket project.

HTTP Status 500 - Cannot call sendRedirect() after the response has been committed
    java.lang.IllegalStateException: Cannot call sendRedirect() after the response has been committed
        org.apache.catalina.connector.ResponseFacade.sendRedirect(ResponseFacade.java:483)
	javax.servlet.http.HttpServletResponseWrapper.sendRedirect(HttpServletResponseWrapper.java:138)
	org.springframework.security.web.firewall.FirewalledResponse.sendRedirect(FirewalledResponse.java:25)
	javax.servlet.http.HttpServletResponseWrapper.sendRedirect(HttpServletResponseWrapper.java:138)
	org.springframework.security.web.context.SaveContextOnUpdateOrErrorResponseWrapper.sendRedirect(SaveContextOnUpdateOrErrorResponseWrapper.java:107)
	org.apache.wicket.protocol.http.servlet.ServletWebResponse.sendRedirect(ServletWebResponse.java:268)



was (Author: ualtin):
Sorry to dig this out, but after updateing to 6.13.0 we have some errors. 

We are calling getSession.getClientInfo in onInitialize in our TemplatePage. The first time, after the server restarts, we get an "Status 500 - Cannot call sendRedirect() after response has been committed" (see below).
Even when we comment this out we get the exception when we use the DateConverter (as this is somwhere calling getClientInfo as well).
Unfortunatly I could not yet reproduce this on a startup wicket project.

HTTP Status 500 - Cannot call sendRedirect() after the response has been committed
    java.lang.IllegalStateException: Cannot call sendRedirect() after the response has been committed
        org.apache.catalina.connector.ResponseFacade.sendRedirect(ResponseFacade.java:483)
	javax.servlet.http.HttpServletResponseWrapper.sendRedirect(HttpServletResponseWrapper.java:138)
	org.springframework.security.web.firewall.FirewalledResponse.sendRedirect(FirewalledResponse.java:25)
	javax.servlet.http.HttpServletResponseWrapper.sendRedirect(HttpServletResponseWrapper.java:138)
	org.springframework.security.web.context.SaveContextOnUpdateOrErrorResponseWrapper.sendRedirect(SaveContextOnUpdateOrErrorResponseWrapper.java:107)
	org.apache.wicket.protocol.http.servlet.ServletWebResponse.sendRedirect(ServletWebResponse.java:268)


> Ajaxified version of WebSession#getClientInfo should be added
> -------------------------------------------------------------
>
>                 Key: WICKET-5435
>                 URL: https://issues.apache.org/jira/browse/WICKET-5435
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>    Affects Versions: 6.13.0
>            Reporter: Maxim Solodovnik
>            Assignee: Martin Grigorov
>              Labels: features, patch
>             Fix For: 6.13.0, 7.0.0
>
>
> It would be nice to have Ajaxified version of WebSession#getClientInfo of of the box
> here is the link to the discussion: http://markmail.org/message/ex3hxtynnmnktzgy
> My implementation based on wicket quickstart is here: https://github.com/solomax/ajax-client-info/blob/master/src/main/java/org/ajax/ClientInfoBehavior.java
> Thanks in advance



--
This message was sent by Atlassian JIRA
(v6.2#6252)