Hi all,
I want to propose an extension to the current Servlet Resolution
process. At the moment Servlets in Sling (and microsling) are only
selected based on the Resource Type (Resource.getResourceType()) while
scripts are selected by resource type, selectors, HTTP request method
and response
Hi all,
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
hi,
i face a problem with the servlet resolution. i want to use my own
servlet for GET requests, but the default ujax post servlet for POST
requests. the servlet resolver finds my servlet for the respective
resource type, but does not check may service later:
SlingServletResolver
I'm trying to register a servlet to handle requests with a ".menu" extension:
* @scr.property
* name="sling.servlet.extensions"
* value="menu"
Then I post some content:
curl -F"sling:resourceType=foo/bar" -F"title=some title"
http://admin:[EMAIL PROTECTED]:/content/mynode
If I now visit
On 11/26/08, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> 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.
>
> Act
+1. I think this is a possibly very common use case.
BR,
Juanjo.
On Wed, Nov 26, 2008 at 10:39 PM, Felix Meschberger <[EMAIL PROTECTED]>wrote:
> Hi all,
>
> After the big reorganization of servlet resolution in April of this year
> and some more experiences with using Sl
On Wed, Nov 26, 2008 at 10:39 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> Over time use cases arose, which would be easier implementable if we
> would support using selectors to influence servlet/script resolution for
> all methods.
+1
Regards,
Alex
--
Alexander Klimetschek
[EMAIL PROTEC
> +1 to allow selector mapping for all methods.
+1
-Bertrand
Felix Meschberger schrieb:
> Hi all,
>
> 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: Consi
Hi all,
Thanks for your feedback. I have created SLING-748 and applied the
changes of my whiteboard into trunk in Rev. 722089
Regards
Felix
[1] https://issues.apache.org/jira/browse/SLING-748
Felix Meschberger schrieb:
> Hi all,
>
> After the big reorganization of servlet resolution
uot;. POST requests
as well as any other GET requests are not handled by your servlet.
More information on servlet resolution is to be coming soon on the
wiki
Hope this helps so far.
Regards
Felix
Am Freitag, den 25.01.2008, 16:48 +0100 schrieb Tobias Bocanegra:
> hi,
> i face a problem
ot;html" ]
>
> Now your servlet is only called for GET requests with extension "html"
> to resources whose resource type is "your/resourceType". POST requests
> as well as any other GET requests are not handled by your servlet.
>
> More information on
Hi Vidal,
The sling.servlet.resourceTypes annotation is required, otherwise the
servlet is just ignored. That is, in your first example, where you just
define the sling.servlet.extensions, Sling does not know to which
resource type the servlet applies and cannot handle it.
@scr.property name="s
On 2/15/08, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> Hi Vidal,
>
> The sling.servlet.resourceTypes annotation is required, otherwise the
> servlet is just ignored. That is, in your first example, where you just
> define the sling.servlet.extensions, Sling does not know to which
> resource
Hi Vidal,
Am Freitag, den 15.02.2008, 15:39 +0100 schrieb Vidar Ramdal:
> On 2/15/08, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> > Hi Vidal,
> >
> > The sling.servlet.resourceTypes annotation is required, otherwise the
> > servlet is just ignored. That is, in your first example, where you ju
On Feb 15, 2008 3:50 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> >... Ah, I see. I wanted to make a servlet that would respond to the .menu
> > extension regardless of resourceType, but if that's not possible, I'll
> > work around it. Thanks for your help!
> >
>
> That is possible: just use
hi,
currently sling uses @scr javadoc comments to specify the bindings
from the request infos to servlets. for example:
/**
* @scr.service
* @scr.property name="sling.servlet.resourceTypes" values="bin/test"
* @scr.property name="sling.servlet.extensions" values="txt, html"
*/
public class Tes
Update Servlet Resolution Description
-
Key: SLING-421
URL: https://issues.apache.org/jira/browse/SLING-421
Project: Sling
Issue Type: Sub-task
Components: ServletResolver
Reporter
work on this yet
and I do not consider this a release blocker.
> Update Servlet Resolution Description
> -
>
> Key: SLING-421
> URL: https://issues.apache.org/jira/browse/SLING-421
> Project: Slin
Tobias Bocanegra wrote:
this has the following drawbacks:
- the possible @scr properties are hard to guess if not documented
Hmm, I think they are documented, but perhaps not as prominent as this
should be.
- the @scr properties are not "type safe"
This depends. You can use @scr.property name
Servlet resolution examples and integration tests
-
Key: SLING-923
URL: https://issues.apache.org/jira/browse/SLING-923
Project: Sling
Issue Type: Improvement
Components: Testing
://incubator.apache.org/sling/site/servlet-resolution.html (will be
published in a few hours).
> Servlet resolution examples and integration tests
> -
>
> Key: SLING-923
> URL: https://issues.apache.org/ji
Document Servlet Resolution and Error Handling
--
Key: SLING-992
URL: https://issues.apache.org/jira/browse/SLING-992
Project: Sling
Issue Type: Task
Components: Documentation
Apply same logic to servlet resolution as is used for script resolution
---
Key: SLING-145
URL: https://issues.apache.org/jira/browse/SLING-145
Project: Sling
Issue Type
integration
into trunk as part of SLING-197. Therefore I close this issue.
> Apply same logic to servlet resolution as is used for script resolution
> ---
>
> Key: SLING-145
> URL: https://is
25 matches
Mail list logo
