You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Ben Conlan (JIRA)" <ji...@apache.org> on 2010/05/20 10:07:53 UTC

[jira] Commented: (SLING-1173) Support selecting non-GET scripts as per the request extension

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

Ben Conlan commented on SLING-1173:
-----------------------------------

I assume that this will also solve problems where a user wishes to create a particular node type but the servlet resolver identifies the resource as "sling:nonexisting"?

ie "curl -X POST -f"sling:resourceType=foo/bar" http://admin:admin@xxx.com/content/new"

(where the servlet service is registered to process the "POST" method of resource type "foo/bar")

> Support selecting non-GET scripts as per the request extension
> --------------------------------------------------------------
>
>                 Key: SLING-1173
>                 URL: https://issues.apache.org/jira/browse/SLING-1173
>             Project: Sling
>          Issue Type: Improvement
>          Components: Servlets
>    Affects Versions: Servlets Resolver 2.0.8
>            Reporter: Felix Meschberger
>             Fix For: Servlets Resolver 2.0.10
>
>
> It is currently not possible to register scripts for non-GET requests for the request extension, yet SLING-754 added support for scripts registered with request selectors.
> Now, for SLING-1172 it is required to be able to register scripts for non-GET requests for the request extension. The idea is that the extension indicates the type of content being uploaded (mostly in the case of POST requests). So JSON file upload could create by "unpacking" the data (as could for example an XML upload).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.