[
https://issues.apache.org/jira/browse/SLING-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu resolved SLING-2192.
------------------------------------
Resolution: Won't Fix
With OSGi RFC 217 bringing official support to JAX-RS in the Enterprise
Specification I don't think we need to anything special in Sling.
https://github.com/osgi/design/tree/master/rfcs/rfc0217
I am resolving this as "Won't Fix", but please reopen if you think there is
still something to do for us. AFAIK the official implementation will live under
Apache Aries, but I did not yet find any sign of it.
> 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)
