Mailing-List: contact dev-help@sling.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@sling.apache.org
Received-SPF: pass (athena.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <CAKkCf4ok_CA1a6fGeLV3ZMmh4xgNCO6gVEK6KK74nOK3uKb71A@mail.gmail.com>
References: 
 <CANOcS=akR=fOwwSL3NQeCOC5baJaTeCqSD5TnsPL7aSjfgwBBg@mail.gmail.com>
	<CAKkCf4ok_CA1a6fGeLV3ZMmh4xgNCO6gVEK6KK74nOK3uKb71A@mail.gmail.com>
Date: Wed, 2 Oct 2013 14:06:04 +0200
Message-ID: 
 <CANOcS=ZP2HiPJLQ2++1rfxAt1M7o1FprQ9cKc7KCfXQVQFV9DQ@mail.gmail.com>
Subject: Re: [DISCUSS] Generic ServiceMap for ServiceResolver
From: Mike Hummel <mh@mikehummel.de>
To: dev@sling.apache.org
Content-Type: multipart/alternative; boundary=047d7b677afac6726704e7c0e48c

--047d7b677afac6726704e7c0e48c
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

In my understanding the service registry is not able to differ between the
resource implementations like mongo or jcr. If the operation is provided
from the resource provider it is specialised for the underlying
implementation.

This is what you need for ResourceSecurityAccess or manipulating rights on
the resource - without knowledge of the underlying data store.


2013/10/1 Carsten Ziegeler <cziegeler@apache.org>

> Hi,
>
> I'm not sure I completely understand your proposal. What's the difference
> to looking up the MoveOperation (or other services) directly from the
> service registry?
>
> Carsten
>
>
> 2013/9/30 Mike Hummel <mh@mikehummel.de>
>
> > Hi,
> >
> > with ResourceAccessSecurity there's the first service depending on the
> > ServiceResolver and loaded by the ServiceTracker. For further services =
we
> > should use a generic way to handle this.
> >
> > Another goal is that we can implement operations in this way for
> different
> > ServiceResolver in a generic way. For example default operations like
> > 'move' 'copy' 'checkout' 'checkin' can then be implemented for differen=
t
> > Resources (jcr, mongodb).
> >
> > On next step it can be used by the post servlet to access it via REST.
> >
> > I implemented a try like this
> >
> > public interface ServiceMap {
> >
> >
> >  /**
> >
> >  * Return the instance of the Service for the requested interface
> >
> >  *
> >
> >  * @param requestedInterface The Service or null if not found
> >
> >  * @return
> >
> >  */
> >
> > <T> T getService(Class<T> requestedInterface);
> >
> >  }
> >
> > public interface ResourceResolver {
> >
> > =E2=80=A6
> >
> >     /**
> >
> >      * Return the service map for this resolver.
> >
> >      *
> >
> >      * @return
> >
> >      */
> >
> >     ServiceMap getServiceMap();
> >
> > }
> >
> > To use a service use
> >
> > ResourceAccessSecurity  service =3D
> >
> >
> resource.getResourceResolver().getServiceMap().getService(ResourceAccessS=
ecurity.class);
> >
> > or maybe
> >
> > MoveOperation  service =3D
> >
> >
> resource.getResourceResolver().getServiceMap().getService(MoveOperation.c=
lass);
> > service.move(resource,targetPath);
> >
> > Ok, what's the goal?
> >
> > 1. We do not need to change resource providers if we initiate a new
> service
> > for resources
> > 2. A generic way to access operations if the service implement an
> > Operation-Interface via REST / Post-Servlet
> >
> > What do you think?
> >
> > Mike
> >
>
>
>
> --
> Carsten Ziegeler
> cziegeler@apache.org
>

--047d7b677afac6726704e7c0e48c--