On Wed, Jul 2, 2008 at 6:46 AM, Bryce Ewing <[EMAIL PROTECTED]> wrote:
> ...I was thinking that it may be that I should just mount the Restlet servlet > on certain root uri's, which will override sling... but then this data would > not be accessible through sling at all. This may be a good short term > solution (and one that it would be good to be able to know how to do?) > > Preferably I would like all of the data to be visible directly within > sling.... I'm not sure if I understand exactly what you're after, is that something like GET /users -> served by Restlet GET /users.html -> served by Sling If that's the case, the simplest way might be to create a front-end servlet that implements this decision and forwards to the appropriate servlet, to avoid having to hack the Sling or Restlet servlets. Another approach, if you have an httpd front-end, would be to rewrite URLs to redirect them to the appropriate backend. -Bertrand
