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

Carsten Ziegeler commented on SLING-2726:
-----------------------------------------

I'm not against doing such a simple resource provider, however I'm not sure if 
it really helps in this use case.

I'm not in favour of allowing wild cards in registration as this is 
contradicting the idea of the resource tree a little bit and I'm definitly 
against mixing data (= resources) with their rendering (servlets/scripts).

As I noted above, if the resource approach does not work for a use case, there 
is still the possibility to register a servlet using the http service (not the 
Sling engine) and implement the logic here. As this is an OSGi service it can 
access the resource resolver and get resources from the tree. This is very 
simple and straightforward.
                
> allow simple wildcards in servlet paths
> ---------------------------------------
>
>                 Key: SLING-2726
>                 URL: https://issues.apache.org/jira/browse/SLING-2726
>             Project: Sling
>          Issue Type: Improvement
>          Components: Servlets
>            Reporter: Nicolas Peltier
>            Priority: Minor
>
> While i'm a big fan/evangelist of sling unique servlet management. I tend to 
> think this would be nice to allow minimum wildcard for servlet paths, i.e. 
> /a/b/* (no suffix), as some use cases can't be cover right now with jcr based 
> resources + path servlets.
> Basically every resource model where you don't need a jcr node for (while 
> it's very convenient most of the time).
> I'm thinking for example of having a profile servlet with a nice public 
> /profile/jdoe.html url. Right now my possibilities are 
> * to create a flat tree of fake user nodes under a profile node just for the 
> sake of my urls (don't need righs handling, don't need other verbs for the 
> same resource), 
> * to have tons of vanityUrls (not meant for that kind of usage)
> * to create my own ResourceProvider that map that kind of URLs to existing 
> jcr resources.
> * to switch to /profile.jdoe.html, or /profile.html?uid=jdoe
> And i tend to think a tiny wildcard in a path parameter would be nicer :-)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to