Great this is going to be a nice thing to have. This basically takes care of my itch for an OR mapping tool for LDAP and whoa it's supported by standard interfaces. Can't beat that.
Alex On 3/28/07, Ole Ersoy <[EMAIL PROTECTED]> wrote:
Alex Karasulu wrote: > I'm too busy reading about fishing lures ATM :). Maybe in a few > days. However I am very interested in this. > > Already thinking about a couple road blocks that you will encounter: > > (1) cardinality of members and mapping that to LDAP Yeah - I think I got these covered. I'll write it up in the design guide - And then we can discuss further. > (2) complex subordinate objects and how to map that in LDAP > Yup - I thought about that too. I think I have it, and we'll soon see :-) > There are solutions to these but they need to be discussed I guess. > Yeah - The SDO specification, along with a few simple conventions, will give us a very elegant solution to this I think. > Alex > Ole > > On 3/28/07, *Ole Ersoy* <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > Hey Guys, > > This thing is a little tricky to find on the Tuscany site: > http://wiki.apache.org/ws/Tuscany/TuscanyJava/DAS_Java_Overview/RDBDAS_Java_User_Guide > > But it explains how the RDB DAS works, which may help illuminate > how the LDAP DAS will work. I'm going to use this guide > as a starting point for driving the design of the LDAP DAS. > > So if you combine this info with this SDO Tutorial: > http://help.eclipse.org/help32/index.jsp?topic=/org.eclipse.emf.ecore.sdo.doc/tutorials/datagraph/datagraph.html > > you'll have a pretty good idea of how this stuff works. > > Cheers, > - Ole > > >
