[jira] [Resolved] (SLING-2039) Output lost with JSPs and sling:include

["Felix Meschberger (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger resolved SLING-2039.
--------------------------------------

    Resolution: Fixed

Removed Sling's internal output buffering completely in Rev. 1086883

For historical reasons predating Apache Sling by years (aeons I dare say) Sling Engine maintained its own response buffering down to a processing component level.

Since servlet containers nowaydays all implement response buffering there is no reason for Sling to do it, too.

> Output lost with JSPs and sling:include
> ---------------------------------------
>
>                 Key: SLING-2039
>                 URL: https://issues.apache.org/jira/browse/SLING-2039
>             Project: Sling
>          Issue Type: Bug
>          Components: Engine
>    Affects Versions: Engine 2.2.2
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: Engine 2.2.4
>
>
> Using a single output buffer per included resource may lead to loss of response data.
> Consider this setup:
>    - main request handled by html.jsp. Some data is written to "out" (buffering JspWriter)
>    - html.jsp incudes another jsp (list.html.jsp) which in turn writes more data
>    - html.jsp continues writing to the output
> If list.html.jsp sends less than the JspWriter's buffer, everything is fine.
> As soon as the JspWritter buffer overflows, though, only the first bytes of the actual response (exactly the size of the JspWriter buffer) is returned.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira