Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 61531 invoked from network); 29 Mar 2007 01:53:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 29 Mar 2007 01:53:01 -0000 Received: (qmail 39827 invoked by uid 500); 29 Mar 2007 01:53:08 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 39784 invoked by uid 500); 29 Mar 2007 01:53:08 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 39773 invoked by uid 99); 29 Mar 2007 01:53:08 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Mar 2007 18:53:08 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of akarasulu@gmail.com designates 66.249.82.234 as permitted sender) Received: from [66.249.82.234] (HELO wx-out-0506.google.com) (66.249.82.234) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Mar 2007 18:53:00 -0700 Received: by wx-out-0506.google.com with SMTP id h31so38832wxd for ; Wed, 28 Mar 2007 18:52:39 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=X0XUhxdqCWXNgDybSxT/6skGqNydjiGTSgjbBIpQekbr820bwx6GZK1tVECN/gUElpS7/tyXlXqSrY5G52CJgd2NwEW+af8JVyHD2EB135qk2zuUd/rsx++E4zHaR94WZZM2srcjod4w2RIWlkHh86uJSTmkXfskRzCPw3QVWCY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=aS7mCxlRup9Wcw8xdVZom3+KPAnDM9TwukdmaagqYsaCQbocvPbNNAHRxhG+8FBDjfjzxt3jF81LLmonbUA3DEFWCkGauO3cCkfcxx5GpOpQlgh2FPgdOwq761XavHtJVTl001+GfCAA5Q0tynJ6VHmRcbJWtz1ldNmVQfPkDvU= Received: by 10.70.30.5 with SMTP id d5mr306233wxd.1175133159591; Wed, 28 Mar 2007 18:52:39 -0700 (PDT) Received: by 10.70.78.18 with HTTP; Wed, 28 Mar 2007 18:52:39 -0700 (PDT) Message-ID: Date: Wed, 28 Mar 2007 21:52:39 -0400 From: "Alex Karasulu" Sender: akarasulu@gmail.com To: "Apache Directory Developers List" Subject: Re: [LDAP DAS] Tuscany RDB DAS Users Guide In-Reply-To: <460A9DD3.7020406@gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_18304_7903619.1175133159498" References: <460A9DD3.7020406@gmail.com> X-Google-Sender-Auth: be1a30573b450822 X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_18304_7903619.1175133159498 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline 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 (2) complex subordinate objects and how to map that in LDAP There are solutions to these but they need to be discussed I guess. Alex On 3/28/07, Ole Ersoy 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 > > > ------=_Part_18304_7903619.1175133159498 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
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
(2) complex subordinate objects and how to map that in LDAP
 
There are solutions to these but they need to be discussed I guess.
 
Alex

 
On 3/28/07, Ole Ersoy <ole.ersoy@gmail.com> 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



------=_Part_18304_7903619.1175133159498--