Hi Ersin, Alex and I talked about doing this.
I need to finish the first version of the the design document. OpenLDAP supports relational backends. They also have this command: ldbmcat - LDBM to LDIF database format conversion utility I think that performs relational to LDIF conversion. Personally I need to be able to go between an LDAP format, XML Schema format, and a relational format. I'm planning on going with need a 4th representation of those 3, which will be Eclipse EMF Ecore (A subset of OMG's meta object facility). That way ecore is the common denominator. So the initial thinking is that ldap attributes will be mapped to attributes on an Ecore based model object (Just a pojo really supported by the Eclipse EMF API). The same Ecore model is used to generate the Hibernate mapping (Preferably using annotations). Then it's done. Hibernate takes care of the rest. I still need to put this in complete context, adding in Alex's thoughts on virtual directories, etc. That's a little off though...after the rpm mojo gets done. Cheers, - Ole --- Ersin Er <[EMAIL PROTECTED]> wrote: > Hi all, > > I need some advice on implementing a partition for > ADS based on the > relational model and using SQL or Hibernate or JPA, > or framework like > them.. > > First of all, is this realistic? Can we reach a > usable result? > > How can we map Attributes to SQL model? Should we > hold Attribute > Values in blobs? > > Can we leverage the power of SQL SELECT for LDAP > search operations? > > How much of the partition code in ADS can be used > for this task? > > And please share any more ideas you have. > > Thanks in advance. > > -- > Ersin > ____________________________________________________________________________________ Low, Low, Low Rates! Check out Yahoo! Messenger's cheap PC-to-Phone call rates (http://voice.yahoo.com)
