[ https://issues.apache.org/jira/browse/SLING-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13577321#comment-13577321 ]
Justin Edelson commented on SLING-2726: --------------------------------------- While you *can* use suffixes, that may produce URLs which are unacceptable to stakeholders (whether these are good or bad reasons doesn't matter IMHO). Using rewriting rules should be considered a workaround and something worth avoiding. While I agree that adding wildcards to Sling's engine isn't necessary or appropriate, I do think that there's a legitimate problem here - some Sling users feel overly constrained by the use of the resource tree to define their URL space. I think the right solution (or at least a right solution) lies in making ResourceProviders easier to create. Similar to the way the FS Resource Provider works, what if we added a configuration factory-based provider? Something like a SimpleResourceProvider which would get configured with a root path, a resourceType, and (maybe) a set of key/value pairs. > 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