On Tue, May 22, 2012 at 10:12 AM, [email protected] < [email protected]> wrote:
> The Sling-Rs is useless for my scenario as it is sort of a "crippled" > Jax-Rs. It doesnt seem to support @Path. > That's correct. Sling-RS is mainly sling and is designed to be used in applications following sling design patterns, i.e. with resources bound to sling-types. It just allows to do sling development without having to use classes from the now very old servlet api. It supports injection of parameters to method argument as well as conversion from response objects to http entity bodies by mean of MessageBodyWriters. While this integrations in Sling requires renouncing on some jax-rs features I think it make developing for Sling much easier as it hides away more low-level apis. wink-osgi by contrast supports standard jax-rs with its @Path annotation. What could be added is a servlet that can be bound to specific paths so that within a certain uri-space all requests are handled exclusively by the jax-rs mechanisms. Would this satisfy your usecase? Cheers, Reto > > regards, > > Marius > > Links: > ------ > [1] mailto:[email protected] >
