I agree, that we might want to wait for a real-life request.
On the other hand it is not only the end-users fault if not the correct
methods could be used, though browsers are probably the major number of
culprits. Many times it is just a question of firewall limitation which
can by no means be ci
URI path split is content dependent
---
Key: SLING-60
URL: https://issues.apache.org/jira/browse/SLING-60
Project: Sling
Issue Type: Improvement
Components: microsling
Reporter: Felix Mes
[
https://issues.apache.org/jira/browse/SLING-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-58.
--
Resolution: Fixed
Support has been added and this can now be closed.
> Add support for templated
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 m
[
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
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: Ber
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 M
[
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 JcrNod
[
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 modi
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
[
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
sim
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 w
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 usin
Have SlingException extend ServletException
---
Key: SLING-56
URL: https://issues.apache.org/jira/browse/SLING-56
Project: Sling
Issue Type: Improvement
Components: microsling
Affects Ver
[
https://issues.apache.org/jira/browse/SLING-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-56.
--
Resolution: Fixed
Fixed in Rev. 585079
> Have SlingException extend ServletException
> -
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 e
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 reason
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 yester
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
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 tricke
On 10/16/07, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> ...What do you think of (1) making microsling the "reference
> implementation" of the new Sling API and thus (2) promoting it
> to the trunk and finally (3) try to reuse parts of microsling
> code for the r
[
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 in
[
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 Sling
[
https://issues.apache.org/jira/browse/SLING-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535174
]
Bertrand Delacretaz commented on SLING-54:
--
Agreed, let's use the standard interface for this.
The idea in ha
microsling: add ServiceLocator?
---
Key: SLING-55
URL: https://issues.apache.org/jira/browse/SLING-55
Project: Sling
Issue Type: Improvement
Components: microsling
Reporter: Bertrand Delacret
[
https://issues.apache.org/jira/browse/SLING-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535166
]
Felix Meschberger commented on SLING-50:
> MimeTypeResolver: factor out the current SlingRequestContext.getMime
Drop RequestFilter interface for the real servlet Filter interface
--
Key: SLING-54
URL: https://issues.apache.org/jira/browse/SLING-54
Project: Sling
Issue Type: Improvement
> What do you think of (1) making microsling the "reference
> implementation" of the new Sling API and thus (2) promoting it
> to the trunk and finally (3) try to reuse parts of microsling
> code for the real Sling ?
+1
... loving it ;)
regards,
david
Hi all,
After the introduction [1] of microsling as a simple testbed for the
discussions around a new Sling API [2] and some discussions on the list,
I want to poll the communities opionion on the following question:
What do you think of (1) making microsling the "reference
implem
29 matches
Mail list logo
