Hi,
I wanted to let you know that we have developed a first version of an
open source integration between EMF and Hibernate. The integration is very much alpha version software but it is maybe already interesting for someone to look at.

Some of the supported (in alpha mode) features:
- Automatically generate hibernate mapping file
- One-to-One, One-to-Many, Many-to-Many relations (elist), one-way,
two-way, contained and non-contained
- Specific EMF Resource implementation for Hibernate, including
validation of resource content
- Retrieve EMF EObjects using HQL
- Most primitive types and lists of primitive types are supported
- EMF Enumerations
- Root object only needs to implement InternalEObject interface

In the near future we will add support for Feature Maps and related XML
Schema constructions (e.g. substitution groups).
For more information and to download the software please visit:
http://www.elver.org/hibernate/

We hope this is of interest to you and are very interested in your feedback.

Thanks for your interest,
Martin Taal

Just to check I understand the implications of this.

When finished would this allow a user to create a UML diagram and have this automatically converted into the domain objects and mapping files?

Hi,
Yes, using EMF then ofcourse:
1) The UML diagram is imported into EMF and an ecore model is created automatically
2) EMF generates the java source code
3) The Elver solution creates the hibernate mapping file and includes a runtime to solve different kinds of EMF - Hibernate runtime integration issues.

It takes a few mouse clicks though :-).

Note that the integration is alpha software, so it is probably unstable in some areas, a number of real EMF specifics are supported though (Elists for example).
Also the integration will need to be extended to make use of more Hibernate features (for example different inheritance mapping strategies).

gr. Martin

Cool (for those who likes EMF ;)

I just want to be clear here that EMF is not directly supported by Hibernate because EMF is a very intrusive and propritiary model (so only choose if it if you really really need it ;)

But it is great to have a showcase of the flexibility of Hibernate 3 in the area of supporting non-pojo models.

/max