You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2008/08/19 12:51:44 UTC
[jira] Resolved: (SLING-621) DefaultSlingScript should not flush
the output after the script ends
[ https://issues.apache.org/jira/browse/SLING-621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger resolved SLING-621.
-------------------------------------
Resolution: Fixed
Committed fix in Rev. 687015 and deployed snapshot build version 2.0.3-incubator-20080819.105057-2.
> DefaultSlingScript should not flush the output after the script ends
> --------------------------------------------------------------------
>
> Key: SLING-621
> URL: https://issues.apache.org/jira/browse/SLING-621
> Project: Sling
> Issue Type: Bug
> Components: Scripting
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: Scripting Core 2.0.4
>
>
> The DefaultSclingScript.service method prepares a SlingBindings instance to call the script. This prepared instance provides the request and response objects and sets the flush property to true, which in turn causes the response to be flushed (and hence committed) when the script terminates.
> It is not necessairy to actually forcibly flush the output here, instead it might create issues if the response is committed early.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.