[arquillian-issues] [JBoss JIRA] (ARQ-1320) Warp - The NonWrittingResponse does not override the flushBuffer() method allowing for commiting response.

[Jakub Narloch (JIRA)]

     [ https://issues.jboss.org/browse/ARQ-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jakub Narloch updated ARQ-1320:
-------------------------------

    Description: 
The flushBuffer(http://docs.oracle.com/javaee/6/api/javax/servlet/ServletResponse.html#flushBuffer()) which causes the response to be marked as commited. and Adding afterwards any headers to the response has no effect.

We should override the that method and prevent it's default behaviour.

Also, it would be good idea to check the specs for any other method that could commit the message and prevent from enriching it by Warp.

  was:
The flushBuffer(http://docs.oracle.com/javaee/6/api/javax/servlet/ServletResponse.html#flushBuffer()) which causes the response to be marked as commited. and Adding afterwards any headers to the response has no effect.

We should override the flushBuffer method and prevent it's default operation.

Also, it would be good idea to check the specs for any other method that could commit the message and prevent from enriching it by Warp.


    
> Warp - The NonWrittingResponse does not override the flushBuffer() method allowing for commiting response.
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: ARQ-1320
>                 URL: https://issues.jboss.org/browse/ARQ-1320
>             Project: Arquillian
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Extension - Warp
>    Affects Versions: warp_1.0.0.Alpha2
>            Reporter: Jakub Narloch
>            Assignee: Lukáš Fryč
>
> The flushBuffer(http://docs.oracle.com/javaee/6/api/javax/servlet/ServletResponse.html#flushBuffer()) which causes the response to be marked as commited. and Adding afterwards any headers to the response has no effect.
> We should override the that method and prevent it's default behaviour.
> Also, it would be good idea to check the specs for any other method that could commit the message and prevent from enriching it by Warp.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira