Mailing-List: contact users-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@directory.apache.org
MIME-Version: 1.0
In-Reply-To: <b4e760d0-1d3e-5fb1-78dc-78a96861f2b0@gmail.com>
References: <CA+GjePVidw5KY8tUR1iiRmzAzKRAxj_2MeLdb5aCwyoF24-uyw@mail.gmail.com>
 <b4e760d0-1d3e-5fb1-78dc-78a96861f2b0@gmail.com>
From: Greg Thomas <greg.d.thomas@gmail.com>
Date: Wed, 14 Dec 2016 08:38:50 +0000
Message-ID: <CA+GjePXkWzoDcnPXOZb7tVvSXRBwWTJbDQ3QJSeVq0+obLLv1A@mail.gmail.com>
Subject: Re: Mapping hierarchical models
To: users@directory.apache.org
Content-Type: multipart/alternative; boundary=001a113540922bc9cb05439a44a6
archived-at: Wed, 14 Dec 2016 08:39:01 -0000

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

> when you need to get back 2 different
> informations from a LDAP server, you need to send 2 different LDAP
> requests.

That was the conclusion I came too, as well.

> LDAP accepts multi-value
> attributes, so you can imagine adding the equipements into a dedicated
> AttributeType in a version of person.

Unfortunately I don't have control of the schema (I've also over-simplified
it for the purposes of the example).
I think the tactic we're going to go for is;

a) Find all the people, create objects for them.
b) Find all the equipment, create objects for them. We know which person
each item is for from the DN, as we can add each equipment object to the
appropriate person object.

It's two queries, but a lot quicker than on query for each person.

Thanks,

Greg

On 13 December 2016 at 20:25, Emmanuel L=C3=A9charny <elecharny@gmail.com> =
wrote:

>
>
> Le 13/12/16 =C3=A0 18:26, Greg Thomas a =C3=A9crit :
> > Firstly, apologies for all the recent questions. I recently started
> looking
> > at our LDAP code, and would like to migrate away from JNDI, The Apache
> LDAP
> > API seems like the way to go, but I'm having fun with the API.
> >
> > Secondly, can I say congratulations on all the good work that you've
> done;
> > the API seems streets ahead of JNDI, and it makes it /much/ easier to
> use.
> >
> > Finally, my question. Our LDAP server is, from the client we're
> > considering, read-only - so I'm only interesting in reading information
> out
> > of it. It models what I suspect is a fairly normal hierarchy of objects=
.
> > For simplicity, let's assume it models equipment that people are
> > responsible for, which is close enough to explain my problem. So
> > conceptually, we may have
> >
> > Alice (objectclass=3Dperson)
> > |
> > +--> PC (objectclass=3Dequipment)
> > +--> Monitor (objectclass=3Dequipment)
> > +--> Phone (objectclass=3Dequipment)
> >
> > Bob
> > |
> > +--> PC (objectclass=3Dequipment)
> > +--> Monitor (objectclass=3Dequipment)
> > +--> Phone (objectclass=3Dequipment)
> >
> > etc. etc.
> >
> > Now, I can find just the people
> >
> > connectionTemplate.search(baseDn.add("ou=3Dpeople"),
> "(objectClass=3D*person*
> > *)"*, SearchScope.ONELEVEL, PERSON_MAPPER);
> >
> > I can also find just the equipment
> >
> > connectionTemplate.search(baseDn.add("ou=3Dpeople").add("ou=3Dequipment=
"),
> > "(objectClass=3Dequipment*)"*, SearchScope.ONELEVEL, EQUIPMENT_MAPPER);
> >
> > Is there a way I could use an EntryMapper to somehow map both people an=
d
> > equipment in the one search? Something like ...
> >
> > connectionTemplate.search(baseDn.add("ou=3Dpeople"),
> "(|(objectClass=3D*person*
> > )(objectClass=3Dequipment*))"*, SearchScope.SUBTREE,
> > PEOPLE_AND_EQUIPMENT_MAPPER);
> >
> > Although that does pass in a sequence of Entry objects to the mapper, t=
he
> > order is "all the people" followed by "all the equipment". Unless I've
> > missed something, there's no easy way to add the equipment to the perso=
n
> as
> > part of the mapper - i.e. it has to be done as part of a two part
> process;
> > find all the people, find all the equioment, and then assign the
> equipment
> > back to the people.
> >
> > Have I missed anything here?
>
> Hi Greg,
>
> Lucas, please correct me if I'm wrong.
>
> LDAP does not do any joint, so when you need to get back 2 different
> informations from a LDAP server, you need to send 2 different LDAP
> requests. Here, it's even worse, because youc an get all the users in
> one single request, but you will have to iterate on all the result
> etries in order to grab the sub entries containing their equipement, one
> by one.
>
> This is clearly not efficient.
>
> Now, you should consider another path : LDAP accepts multi-value
> attributes, so you can imagine adding the equipements into a dedicated
> AttributeType in a version of person. Of course, if you need to add some
> more informations related to each equipement, you will have to augment
> your person ObjectClass up to a point it becomes quite coplicated to
> manage.
>
>
> --
> Emmanuel Lecharny
>
> Symas.com
> directory.apache.org
>
>

--001a113540922bc9cb05439a44a6--