Add request filter for method overwrite
---
Key: SLING-53
URL: https://issues.apache.org/jira/browse/SLING-53
Project: Sling
Issue Type: New Feature
Components: Core, microsling
Roy T. Fielding wrote:
On Oct 11, 2007, at 6:56 AM, Carsten Ziegeler wrote:
Now, all this sounds very cool and indeed it is - but users always had
the problem that they had to use the source resolver instead of plain
java.net.url classes. So before getting content you needed to get a
source
hi roy,
but how i see the current design of (micro)sling - there is not any
intention of 'storing' actions in the uri. of course a user can still
code some 'actions' in his script - but this would not be the fault of
sling. the 'selectors' are primarily used to resolve to a different
'view'
microsling: add ServiceLocator?
---
Key: SLING-55
URL: https://issues.apache.org/jira/browse/SLING-55
Project: Sling
Issue Type: Improvement
Components: microsling
Reporter: Bertrand
[
https://issues.apache.org/jira/browse/SLING-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535175
]
Bertrand Delacretaz commented on SLING-50:
--
Ok for dropping MimeTypeResolver
microsling: complete the
[
https://issues.apache.org/jira/browse/SLING-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger reassigned SLING-54:
--
Assignee: Felix Meschberger
Drop RequestFilter interface for the real servlet Filter
Hi Roy,
Thanks for the clarification and links - comments inline.
On 10/15/07, Roy T. Fielding [EMAIL PROTECTED] wrote:
...The original Web design notes forbid the use of GET for any action
that is considered to have side-effects, because such an
implementation allows users to be tricked into
On 10/15/07, Bertrand Delacretaz [EMAIL PROTECTED] wrote:
...We could for example define that adding a slingMethod=PUT parameter
to the request causes SlingServlet.doPut to be called instead of
doPost
To clarify, note that I meant this for the POST method only, this
should *not* be done
Hi all,
Currently the SlingServlet is a very simple interface defining doXXX
methods for some HTTP request methods and a canProcess method to ask
whether the SlingServlet is willing to process the request. I think,
this interface is not required as is. I discussed this quickly with
Bertrand
Hi,
On 10/15/07, Bertrand Delacretaz [EMAIL PROTECTED] wrote:
To handle additional HTTP methods, we can always keep the service()
method, maybe renamed to doOtherHttpMethod(), and call it for HTTP
methods which are not covered by the SlingServlet's doX() methods.
This is one of the reasons
Hi,
On 10/16/07, Felix Meschberger [EMAIL PROTECTED] wrote:
What is your opinion on this: A separate SlingServlet interface/class
hieararchy or going along the lines of the HttpServlet (yet doing it
better with respect to non-core HTTP methods) ?
I'd go with HttpServlet, see my previous email
Have SlingException extend ServletException
---
Key: SLING-56
URL: https://issues.apache.org/jira/browse/SLING-56
Project: Sling
Issue Type: Improvement
Components: microsling
Affects
On 10/16/07, Felix Meschberger [EMAIL PROTECTED] wrote:
...What is your opinion on this: A separate SlingServlet interface/class
hieararchy or going along the lines of the HttpServlet (yet doing it
better with respect to non-core HTTP methods) ?...
I tend to agree with you guys about using
Jukka Zitting wrote:
Hi,
On 10/16/07, Felix Meschberger [EMAIL PROTECTED] wrote:
What is your opinion on this: A separate SlingServlet interface/class
hieararchy or going along the lines of the HttpServlet (yet doing it
better with respect to non-core HTTP methods) ?
I'd go with
[
https://issues.apache.org/jira/browse/SLING-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-54.
--
Resolution: Fixed
Replaced RequestFilter by standard Servlet Filter and added AbstractFilter
Resource: retarget the data to be the mapped object and add Item for the
addressed repository Item
--
Key: SLING-57
URL:
[
https://issues.apache.org/jira/browse/SLING-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535219
]
Felix Meschberger commented on SLING-57:
Extended Resource and JcrNodeResource as described. In addition I
[
https://issues.apache.org/jira/browse/SLING-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535219
]
fmeschbe edited comment on SLING-57 at 10/16/07 3:10 AM:
--
Extended Resource and
Add support for templated JavaScript
Key: SLING-58
URL: https://issues.apache.org/jira/browse/SLING-58
Project: Sling
Issue Type: Improvement
Components: microsling
Reporter: Felix
Make microsling code very easy to read
--
Key: SLING-59
URL: https://issues.apache.org/jira/browse/SLING-59
Project: Sling
Issue Type: Improvement
Components: microsling
Reporter:
[
https://issues.apache.org/jira/browse/SLING-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz resolved SLING-52.
--
Resolution: Fixed
Implemented in revision 585188
The name is build from the HTTP method
On Oct 16, 2007, at 1:18 AM, Bertrand Delacretaz wrote:
On 10/15/07, Bertrand Delacretaz [EMAIL PROTECTED] wrote:
...We could for example define that adding a slingMethod=PUT
parameter
to the request causes SlingServlet.doPut to be called instead of
doPost
To clarify, note that I
22 matches
Mail list logo