Hi Mike,

Hmm, that makes sense. Thanks for reminding. I have just done it.

Regards
Felix


Mike Müller schrieb:
> Hi Felix
> 
> Just to be sure: Shouldn't the SLING-972 [1] now be updated/commented
> to reflect, that the dependencies of lanuchpad/bundles to
> org.apache.sling.api and org.apache.sling.engine changed now to the new
> SNAPSHOT versions?
> Sorry, maybe I'm wrong and still haven't got the right point of view
> to understand when and why a dependency is changed in launchpad/bundles.
> Maybe this actual case can clear up my mind ;-))
> 
> best regards
> mike
> 
> [1] https://issues.apache.org/jira/browse/SLING-972
> 
> 
> 
> Felix Meschberger commented on SLING-979:
> -----------------------------------------
> 
> Updated reference to the API and Engine bundles in the launchpad/bundles 
> module in Rev. 776820.
> 
>> Make Sling HTTP Servlet Request and Response Adaptable
>> ------------------------------------------------------
>>
>>                 Key: SLING-979
>>                 URL: https://issues.apache.org/jira/browse/SLING-979
>>             Project: Sling
>>          Issue Type: New Feature
>>          Components: API
>>    Affects Versions: API 2.0.4
>>            Reporter: Carsten Ziegeler
>>            Assignee: Felix Meschberger
>>
>> It would be nice if the SlingHttpServletRequest and SlingHttpServletResponse 
>> would extend the Adaptable interface.
>> Adapting the request/response is interesting in several situations. For 
>> example, in a portlet environment the req/response could be easily adapted 
>> to the Portlet request/response.
>> Or if Sling is used in combination with another web framework the 
>> request/response could be easily adapted to the corresponding objects of 
>> that particular framework.
>> Another use case is the rewriter (in the whiteboard currently) which makes 
>> the response adaptable to a ContentHandler which receives SAX events. This 
>> allows direct streaming of XML events from within Sling without the need of 
>> creating an output stream and later on reparsing.
>> As the request and response object are implemented using the wrappers, 
>> extending the interface does not create problems.
> 
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
> 

Reply via email to