How is it possible to configure XDoclet to split a class and a subclass definition in two different mapping files?

At the moment it is not possible.
Why do you need this? Is there use case for it?

I'd like to provide an entity base class with appropriate hibernate annotations inside a framework. Each concrete application entity should be a subclass of this class. The framework should be deployed as jar.
If I use the @hibernate.subclass tag inside a concrete entity, xdoclet would generate no mapping files for me.

Juat a question, you like to have polymorphic persistence this way? Shall different applications ( class implementation) share the same table?

Or you like to provide some basic functionality, and applications persisten classes do not know
eachs other and live in different tables?

In this case @hibernate.class on concrete entity shall be sufficient.

I need different tables aka one for each entity and no polymorphic behaviour for all entities. But I'd like to provide a base class with an id and version property.

You can just use a base-class, you can just add its properties to the mappings of the subclasses. There is no need to use <subclass> or even seperate mapping files.

In this case forget about subclass. @hibernate.class would suffice.

And you can ( of course ) define common properties ( and of course
ID ) in base class - xdoclet will firn em there without problems.

Thank you so much! This approach works nicely

P.S. coincidentally I've been in Wiesbaden last weekend :-)

Next time you can drop me a note , I'll try go get a leave from my girlfriend and you can spend me a beer :)

I know some nice places to drink it.

Time to start some HUGs (Hibernate User Groups) :)

Can I have "Xdoclet Team" on my badge instead of "Hibernate Expret"? :) BItte bitte bitte...

Good idea. I know a lot of people who consider to use hibernate or who are already using it. Especially when adopting hibernate in big applications there is actually no real platform for the exchange of experiences (eg. further design patterns than described in the hibernate website or in the book).
I gonna suggest a possible HUG at the next Java User Group Munich meeting.

Actually, there are still some ideas open after the last user poll we had. We are going to implement some new stuff soon (also move to a new server machine, the old one has serious load problems...). Not sure if the icons and names will be the same after this.

Nice idea. If you send me a message (michael@hibernate.org) with the date and location, I would be happy to come by and chat about Hibernate and Java in general :)

For those in Rhein-Main I could propose some nice locations in wiesbaden - like