On Fri, Aug 17, 2012 at 11:22 AM, Branden Visser <mrvis...@gmail.com> wrote: >>> Anyway, the /api/people/me endpoint was advised by Zach. Does it need to be >>> moved? > > Nah, I'll convert it to use JAX-RS as part of KERN-3120. >
It looks like the SlingHttpServletRequest dependencies spread deeper than I thought from the servlet -- a lot of shared services are used that take requests as parameters. I'd like to out-scope this refactoring to keep pace on the sprint. Problem is that the JAX-RS servlet does in-fact break the /api/people/me context, as it looks for a JAX-RS resource on that path. Zach: Do you mind if I move this back to /system/*, while I create a task for refactoring the dependent services away from SlingHttpServletRequest in a later sprint? Perhaps "/system/me-light", on the basis that it just returns less data than the other. Thanks, Branden >>> >>> >>> -Duffy >>> >>> ------------------------------ >>> Duffy Gillman >>> Sr. Software Engineer >>> The rSmart Group, Inc. >>> >>> On Aug 17, 2012, at 7:13 AM, Branden Visser <mrvis...@gmail.com> wrote: >>> >>>> Hi everyone, >>>> >>>> I see LiteRevisedMeServlet, a sling servlet, was bound to the /api >>>> context. Is there any particular reason for this? It could collide >>>> with the JAX-RS servlet as it listens (by default) on /api. >>>> >>>> Also, it's identical to the LiteMeServlet, just on a different path... >>>> >>>> -- >>>> Cheers, >>>> Branden >>>> _______________________________________________ >>>> oae-dev mailing list >>>> oae-dev@collab.sakaiproject.org >>>> http://collab.sakaiproject.org/mailman/listinfo/oae-dev >>> >> -- Cheers, Branden _______________________________________________ oae-dev mailing list oae-dev@collab.sakaiproject.org http://collab.sakaiproject.org/mailman/listinfo/oae-dev