On 11/2/06, Ole Ersoy <firstname.lastname@example.org> wrote:
How did you get the sexy vertical lines in the reply?
Way better than all the >>>
gmail do it for me :)
Are you using thunderbird?
yes, but not in office.
--- Emmanuel Lecharny <
> Hi Ole,
> On 11/2/06, Ole Ersoy <email@example.com> wrote:
> > Hi Ersin,
> > <snip/>
> > Personally I need to be able to go between an LDAP
> > format, XML Schema format, and a relational
> This will be possible really soon, at least from
> ldap to XML. Pam is
> writting a DSML codec, so you will be able to
> extract data from LDAP and put
> them in XML format (using DSML V2). You will also be
> able to send data to a
> ldap server using DSML.
That's really sweet.
Here's one of the use cases I want to support for
generating applications (Note that for virtual
directories there will probably at least another use
First create a model that gets translated into Ecore
(XMI). This is the Model part of an MVC architecture,
but it's generic and can map to XML, Relational, LDAP,
Translate the Ecore XMI into a java model (Beans) for
in Memory Persistance (Incidentally Ecore is also used
to Generate Service Data Objects (SDO) - The purpose
of SDO is to unify data programming...Like JDO...but
using Ecore Meta Data as the driver....
Generate the Schema for the persistance solution used
(Relational, LDAP, xml, whatevva)
Note that with Hibernate if you generate the hibernate
configuration file, Hibernate can then generate the
Relational Schema for you. There's already projects
doing this that can be found in the Eclipse EMF
Corner...on the Eclipse EMF site.
So DSML is cool because if Ecore can be used to
generate DSML and then PAM can be used as the driver
to go from DSML to LDIF and back...which means the
result can be imported back into a Ecore generated
Java model...if I understand correctly.
I hope to have some samples worked up soon, just gotta
get this JPackage plugin out the do!
> 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.
> At this point, I really think that DSML might be the
> perfect pivot
> description, because LDIF is only representing data
> while DSML can express
> operations. For instance, if you want to write a
> LDAP proxy, you can do that
> with DSML requests and response (and the LdapStudio
> ldap browser is working
> this way, so, yes, this is possible :). I don't
> think we need a 4th
> description meta-stuff :) KISS, bros !
> So the initial thinking is that ldap attributes will
> > be mapped to attributes on an Ecore based model
> > (Just a pojo really supported by the Eclipse EMF
> > The same Ecore model is used to generate the
> > mapping (Preferably using annotations).
> > Then it's done. Hibernate takes care of the rest.
> Well, this is a vision which is not taking into
> account the performance
> issues you will have if you do that. I may be wrong
> - and I hope to be,
> because this seems to be _so_ simple that I really
> want it to work -, but as
> an old programmer, I don't believe in god or in
> 'snap your finger and the
> tool will do the rest' thingy ... Yeah, I'm an
> agnostic old fart ;) Make me
> believe in it : I want a working sample !
> 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
> > done.
> Yeah, that's seems pragmatic :) Thanks for the work
> done on RPM, man !
> > - Ole
Low, Low, Low Rates! Check out Yahoo! Messenger's cheap PC-to-Phone call rates