Re: How to create Rest APIs for non-JCR data in Sling 8??

Its my understanding that the question on ACL's depends on where it is inheriting the ACL from. Taking your code as literal, you've declared that you own everything under /things and it would inherit the ACL of /. So if you put your ROOT as /content/remote/things You could set JCR ACLs on

Re: How to create Rest APIs for non-JCR data in Sling 8??

Hi Lance, as Mike already mentioned the "Neba framework" offers you the full Spring power, meaning you can easily write Spring controllers which then for example inject your needed OSGi services and you then do whatever you need to do plus you have access to all the possibilities Spring offers

Re: How to create Rest APIs for non-JCR data in Sling 8??

Hey Oli, Isnt that the whiteboard that I gave? https://github.com/apache/aries-jax-rs-whiteboard Greets Roy > On 28 Jan 2017, at 09:43, olimination wrote: > > Hi Lance, > > as Mike already mentioned the "Neba

Re: How to create Rest APIs for non-JCR data in Sling 8??

Hi Henry, I agree with what you say about keeping it simple and using a servlet. However there are many frameworks and platforms today geared towards making it easier to implement REST APIs, and I think non-trivial APIs would probably benefit from using one. As such, to me an API should live

Re: How to create Rest APIs for non-JCR data in Sling 8??

In my opinion Sling is first and foremost a REST framework specifically designed for this kind of thing. It’s not only to serve JCR content. The paradigm Steven described earlier in this thread is EXACTLY the way to implement it. In the Sling world the resource IS the RESTful object addressable