Hey Luciano,
Luciano Resende wrote:
Hi Ole
After you mentioned you are almost done with a initial version of
LDAP DAS that provides CRUD operations [1] I went to your sandbox [2]
to take a quick look at the current implementation and have couple
questions :
- Where is the latest implementation of LDAP DAS available ? Is the
code you have in your sandbox current and the most update one ?
As soon as I have finished up the DAS interface code, commented everything, and removed
left over scraps I'll do another check in the "Working" version. The sandbox
is still the old stuff from when I first got reading and writing graphs working.
- Your sandbox looks like still using a lot of EMF dependencies. Do
you have any plans to base the LDAP DAS implementation on current
Tuscany SDO (SDO 2.1 specification implementation)?
I think we might want to shoot for having it compliant with the SDO 3.0 spec.
2.1 seems to be missing some key API features such as something equivalent to
getEIDAttributes() which returns the EAttribute where id is true. Also another
thing that both EMF and SDO 2.1 are missing is getEAllCrossReferences (which is
the opposite of getEAllContainmentReferences()...EMF does provide an
implementation specific way of doing this though, although it's not part of the
API). Having these in the SDO spec would give us a head start of having a
consistent programming model across DASs.
- The beauty of "Heterogenous DAS" is to have a consistent
programming model and a single set of APIs to access data from
heterogeneous data sources, such as RDB and LDAP. Looks like the
current implementation of LDAP DAS is using a different set of APIs
for it's implementation, thus introducing a new programming model and
a new set of APIs. What are your plans here ?
I totally agree with you. The LDAP DAS should work with the standard SDO API
asap. So we need to identify the gaps between the EMF API parts used currently
and the SDO API and bridge them. Meanwhile, those users needing a common
interface for both the LDAP DAS and RDB DAS would have to use the EMF SDO
implementation.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
