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 2009/05/20 21:30:45 UTC
[jira] Commented: (SLING-979) Make Sling HTTP Servlet Request and
Response Adaptable
[ https://issues.apache.org/jira/browse/SLING-979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12711302#action_12711302 ]
Felix Meschberger commented on SLING-979:
-----------------------------------------
Extended the Sling API in Rev 776815:
* SlingHttpServletRequest and -Response extend Adaptable
* SlingHttpServletRequestWraper and -ResponseWrapper delegate adaptTo to delegatee
> 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.