Jason E Bailey wrote
> Looking at the API I actually have something similar already written
> that uses a resource as a starting point and iterates down through the
> child resources to perform the query.
>
> In that manner it's agnostic as to what's providing the resource, as
> long as we are a
Looking at the API I actually have something similar already written
that uses a resource as a starting point and iterates down through the
child resources to perform the query.
In that manner it's agnostic as to what's providing the resource, as
long as we are able to obtain the children of a r
Steven Walters wrote
> I've seen this API (mentioned) before, and I don't understand why it
> has to get passed onto the ResourceProvider to handle the logic.
> It could instead be ResourceProvider agnostic, so always
> available/functioning no matter what providers are around/in use.
Really? How?
I've seen this API (mentioned) before, and I don't understand why it
has to get passed onto the ResourceProvider to handle the logic.
It could instead be ResourceProvider agnostic, so always
available/functioning no matter what providers are around/in use.
Continuing to depend on ResourceProviders
Jason E Bailey wrote
> Which api proposal is that?
>
https://issues.apache.org/jira/browse/SLING-4752
Carsten
> --
> Jason
>
>
>
> On Thu, Jun 16, 2016, at 01:14 AM, Carsten Ziegeler wrote:
>> Steven Walters wrote
>>> The other providers sling manages in its codebase don't appear to
>>> g
Which api proposal is that?
--
Jason
On Thu, Jun 16, 2016, at 01:14 AM, Carsten Ziegeler wrote:
> Steven Walters wrote
> > The other providers sling manages in its codebase don't appear to
> > get much
> > TLC, such as that they're all still using the older deprecated
> > ResourceProvider s
Steven Walters wrote
> The other providers sling manages in its codebase don't appear to get much
> TLC, such as that they're all still using the older deprecated
> ResourceProvider system, instead of the new one (which the JCR
> ResourceProvider does use).
>
> Also, it appears that a number of th
The other providers sling manages in its codebase don't appear to get much
TLC, such as that they're all still using the older deprecated
ResourceProvider system, instead of the new one (which the JCR
ResourceProvider does use).
Also, it appears that a number of the sling components/functionalitie
Has anyone played around with using Sling without utilizing the JCR resource
provider and utilizing one of the other providers instead?
-Jason
