Hi,

I'm using JPA annotations on some interfaces and using the hibernate tools hbm2ddl and hbm2java with a jpaconfiguration to generate my SQL schema and model POJOs.

All is working fine apart from two serious issues with the generated POJOs:

• The generated POJOs are created with the same package name-space and with the same name as my interfaces (which obviously leads to compilation errors)
• The generated POJOs do not inherit from the annotated interfaces.

I originally tried to solve this by looking for some property to set in the hbm2java tag but none seem appropriate for my needs.

I then found some documentation on using the <meta> tag in the hbm.xml mapping files to specify which interfaces the generated POJOs should implement. However as I do not use hbm.xml mapping files this isn't an option for me. Is there a way to achieve the same thing using hibernate annotations? (I had a look but could not find anything)

The only other thing I've read about that might provide a solution for me is customizing an *.ftl file.

Could some knowledgeable person tell me if the *.flt route is the right one for my needs or is there a simpler way to alter the behaviour of the hbm2java tool that I have not come across yet.

Many thanks in advance,

Tim

Ok, so looks like I had higher expectations of ORM than are currently possible.

I was trying to get hibernate to generate my database schema, DAOs and concrete POJOs from my JPA annotated interfaces. Reading this forum post:

http://stackoverflow.com/questions/2912 ... -hibernate

I found that: "From Java Persistence with Hibernate (p.210): Note that the JPA specification doesn’t support any mapping annotation on an interface! This will be resolved in a future version of the specification; when you read this book, it will probably be possible with Hibernate Annotations."

From what I've seen it is still not currently possible with Hibernate Annotations.

So I've resigned myself to having to hand-craft my POJOs and annotate them to generate my DAOs and database schema.

Tim

Maybe you should try @Inheritance annotation, it worked for me when working with abstract classes. But not sure for interfaces, it didn't work for me but maybe you'll get it to work.