[
https://issues.apache.org/jira/browse/SLING-748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-748.
-----------------------------------
Resolution: Fixed
Applied the changes from my whiteboard to trunk in Rev. 722089.
Closing this now. Any failures should be reported with new issues.
> Consider request selectors for all requests (not just GET/HEAD)
> ---------------------------------------------------------------
>
> Key: SLING-748
> URL: https://issues.apache.org/jira/browse/SLING-748
> Project: Sling
> Issue Type: Bug
> Components: Servlets Resolver
> Affects Versions: Servlets Resolver 2.0.4
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: Servlets Resolver 2.0.6
>
>
> From http://markmail.org/message/r4pbv5ksiwse4gbk:
> After the big reorganization of servlet resolution in April of this year and
> some more experiences with using Sling, I propose the extension of our
> servlet/script resolution process.
> Actually it is a single change only: Consider request selectors for all
> requests. Currently request selectors are only considered for GET or
> HEAD requests and ignored for any other requests.
> Over time use cases arose, which would be easier implementable if we would
> support using selectors to influence servlet/script resolution for all
> methods.
> Example: Say you are building an application providing a configurable input
> form system. The most important configuration would be the action upon form
> submission. Submitted forms are sent back to the resource providing the form.
> The actual action would be encoded as a request selector:
> For example we would like to be able to send a form based mail message. We
> would have script "/apps/myapp/form/mail/POST.esp", which handles the
> "myapp/form" resource type and is called using the "mail" selector. The form
> itself together with some nice GUI surroundings etc. would be stored in the
> /content/feedback resource.
> Now updating the /content/feedback resource should be handled by Sling's
> default POST servlet. Thus POSTing to /content/feedback would update the
> content. Submitting the form would POST to /content/feedback.mail.html and
> should thus not store any form input but trigger the mail/POST.esp script.
> I have prepared a prototype implementation of this new mechanism in my
> sandbox at [1].
> A nice side effect of this prototype is, that it is much simpler codewise.
> [1]
> http://svn.apache.org/repos/asf/incubator/sling/whiteboard/fmeschbe/servlet_resolver
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
