You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Oliver Lietz (JIRA)" <ji...@apache.org> on 2015/01/12 18:52:34 UTC

[jira] [Commented] (SLING-4298) make BufferedServletOutputStream and CaptureResponseWrapper available to other scripting implementations

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

Oliver Lietz commented on SLING-4298:
-------------------------------------

[~cziegeler] please review r1651147 and r1651150

* new package {{servlet}} in {{org.apache.sling.scripting.core}} ok or move classes one up and increase package version?
* new dependency {{org.apache.sling.scripting.core}} for {{org.apache.sling.scripting.jsp.taglib}} ok (should be present at runtime anyway)?

> make BufferedServletOutputStream and CaptureResponseWrapper available to other scripting implementations
> --------------------------------------------------------------------------------------------------------
>
>                 Key: SLING-4298
>                 URL: https://issues.apache.org/jira/browse/SLING-4298
>             Project: Sling
>          Issue Type: Improvement
>          Components: Scripting
>            Reporter: Oliver Lietz
>            Assignee: Oliver Lietz
>             Fix For: Scripting Core 2.0.30, Scripting JSP-Taglib 2.2.6
>
>
> move private (inner) classes {{BufferedServletOutputStream}} and {{CaptureResponseWrapper}} ({{org.apache.sling.scripting.jsp.taglib.IncludeTagHandler}}) from _Scripting JSP Taglib_ to _Scripting Core_



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)