Clean up content data and request data handling
---
Key: SLING-2042
URL: https://issues.apache.org/jira/browse/SLING-2042
Project: Sling
Issue Type: Improvement
Components: Engine
Aff
Upon installation of a fragment bundle refresh packages on the host bundle
--
Key: SLING-2041
URL: https://issues.apache.org/jira/browse/SLING-2041
Project: Sling
Issue
[
https://issues.apache.org/jira/browse/SLING-2040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-2040.
-
Resolution: Fixed
Fixed in revision 1086978
> Avoid logger instantiation and extra servl
Hi all,
I noticed a subtle issue with how the Sling Engine buffers output
(response data) from servlets and scripts. See SLING-2039 [1] for
details.
I have now removed all output buffering from the Sling Engine. This
makes request processing and the RequestData and ContentData objects
much simple
Avoid logger instantiation and extra servlet resolver null check in RequestData
---
Key: SLING-2040
URL: https://issues.apache.org/jira/browse/SLING-2040
Project: Sling
[
https://issues.apache.org/jira/browse/SLING-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated SLING-2039:
-
Attachment: SLING-2039-test.xml
Simple test scenario for this issue. Upload attached file
[
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
[
https://issues.apache.org/jira/browse/SLING-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012890#comment-13012890
]
Felix Meschberger commented on SLING-2039:
--
Investigation shows a problematic int
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.