Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 6127 invoked from network); 29 Mar 2007 05:42:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 29 Mar 2007 05:42:01 -0000 Received: (qmail 57019 invoked by uid 500); 29 Mar 2007 05:42:08 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 56986 invoked by uid 500); 29 Mar 2007 05:42: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 56975 invoked by uid 99); 29 Mar 2007 05:42: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 22:42: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.236 as permitted sender) Received: from [66.249.82.236] (HELO wx-out-0506.google.com) (66.249.82.236) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Mar 2007 22:42:00 -0700 Received: by wx-out-0506.google.com with SMTP id h31so80233wxd for ; Wed, 28 Mar 2007 22:41: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=VzFfJtXDWFx8W4oQTEgfKMmp3XsO0XadnQRRulpg0ax0GIdrKl1q64XmZHpjgjxMfwkgELqLDqB0+K3YbwFf8qY9FHaFGXzzNMxD1Kx3z1yseA4BAsMzxgl9ok85fGq8eT1cP1x7wmy29RrRLDmvlKyvYuynWZlpqVpZrDRrg3M= 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=iLR7D6JVzxh64xJPIc+jCXWQv77CGEArIZKcMjloig5gVu0rQ0L5/nPTTdMctqQw9EzBn2Fbye8ephVP3C9ryMRExXC2dqKmc/QSWLLuUmGkkWlGQPTyT5ZOktAIT53A21VJmTwqaAi3l9g1JRM19vF5LQDvKSI68q13PY1/NUs= Received: by 10.70.17.1 with SMTP id 1mr547340wxq.1175146899479; Wed, 28 Mar 2007 22:41:39 -0700 (PDT) Received: by 10.70.78.18 with HTTP; Wed, 28 Mar 2007 22:41:39 -0700 (PDT) Message-ID: Date: Thu, 29 Mar 2007 01:41: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: <460B209B.9060306@gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_19786_16337283.1175146899436" References: <460A9DD3.7020406@gmail.com> <460B209B.9060306@gmail.com> X-Google-Sender-Auth: 5bda03bfffa53580 X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_19786_16337283.1175146899436 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline 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 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* > > 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_19786_16337283.1175146899436 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
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 <ole.ersoy@gmail.com> 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* < ole.ersoy@gmail.com
> <mailto: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_19786_16337283.1175146899436--