[
https://issues.apache.org/jira/browse/SLING-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz updated SLING-2192:
---------------------------------------
Description:
It should be possible to register jax resource classes and providers as
services. As they don't implement a specific interface services that expose
java.lang.Object should be considered as javx-rs services iff they have the
service property "javax.ws.rs" set to true.
_Edit, December 2015: the discussions below suggest
https://github.com/wcm-io-caravan/caravan-jaxrs as a good and Sling-friendly
way of doing that._
was:It should be possible to register jax resource classes and providers as
services. As they don't implement a specific interface services that expose
java.lang.Object should be considered as javx-rs services iff they have the
service property "javax.ws.rs" set to true.
> Support JAX-RS resource classes
> -------------------------------
>
> Key: SLING-2192
> URL: https://issues.apache.org/jira/browse/SLING-2192
> Project: Sling
> Issue Type: New Feature
> Reporter: Reto Gmür
> Attachments: SLING-2192-20110310.patch, SLING-2192-20111004.patch,
> SLING-2192-20111013.patch, SLING-2192-new-jax-rs-bundle.patch,
> SLING-2192-new-jax-rs-bundle.patch,
> SLING-2192-with-sling-style-style-registration.patch,
> SLING-2192-with-tests.patch, jaxrs-in-contrib.patch, slingr-on-wink-osgi.patch
>
>
> It should be possible to register jax resource classes and providers as
> services. As they don't implement a specific interface services that expose
> java.lang.Object should be considered as javx-rs services iff they have the
> service property "javax.ws.rs" set to true.
> _Edit, December 2015: the discussions below suggest
> https://github.com/wcm-io-caravan/caravan-jaxrs as a good and Sling-friendly
> way of doing that._
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)