Thanks! That makes sense, it would probably be like this for us: /_user/contacts/key1.key2.connections.json
So, this prompts 2 other questions: 1) Does this mean I would get the request/resource for things like this as well? /_user/contacts/stuff/morestuff/key1.key2.connections.json 2) Is it possible to get all the requests/resources that are under the contacts node (in this case based on the resourceType) without specifying a selector? In other words, a request like: /_user/contacts/stuff/morestuff/thing.json If there is some documentation somewhere then you can feel free to tell me to RTFM. :-) -AZ On Fri, Jun 19, 2009 at 3:11 PM, Bertrand Delacretaz <[email protected]> wrote: > > Hi Aaron, > > On Fri, Jun 19, 2009 at 4:00 PM, Aaron Zeckoski<[email protected]> wrote: > > I am trying to handle requests for certain resourceTypes (e.g. > > sakai/contactstore) a special way. > > What I really want to do is handle something like: > > /_user/contacts/key1.key2.json > > > > Where key1 has an unlimited set of values (it would not be a real > > node) and key2 has a set of about 8 values. > > If you can, the simplest might be to add another selector that's constant: > > /_user/contacts/key1.key2.userinfo.json > > Then, declare your servlet to handle the userinfo selector, and use > SlingHttpServletRequest.getRequestPathInfo() .getSelectors() to list > all selectors. > > -Bertrand -- Aaron Zeckoski (azeckoski (at) vt.edu) Senior Research Engineer - CARET - University of Cambridge https://twitter.com/azeckoski - http://www.linkedin.com/in/azeckoski http://aaronz-sakai.blogspot.com/ - http://confluence.sakaiproject.org/confluence/display/~aaronz/
