Hibernate version:
Hibernate 2.1.7c
XDoclet 1.2.2

I see that it is possible to have <subclass> and <joined-subclass> in a separate mapping files. I would like to use XDoclet to generate my mapping files, but it seems that it does not support this feature.

I have classes like:



But here is the thing, Bar is in a separate compilation unit than Bar, and in general most subclasses of Foo are unknown at compile time for Foo. When I try to generate for Bar, since Foo is not in the fileset, it is silently ignored by XDoclet (even with the surprisingly mute verbose feature turned on).

I see the same issue reported here:

http://forum.hibernate.org/viewtopic.php?t=935109
http://forum.hibernate.org/viewtopic.php?t=931574

I'm just starting out with XDoclet, so I am wondering if I am better off I'm better off writing the hbm files by hand. This just seems like the tip of the iceburg to me as far as XDoclet is concerned (along with lack of support for the 1.5 grammar).

Try: http://www.downside.ch/hibernate/ for an Xdoclet tutorial.

Let me clarify, I have actually read a lot of the hibernate book already and all of the reference documentation guide. I have already been pretty successful with integrating Hibernate itself into my app.

In the document you refered me to, I see on pg 11 "XDoclet will only generate one mapping file (animal.hbm.xml) for all three classes". So I guess the answer to my original question is "No".

It doesn't seem like its worth digging around and maybe fixing the problem when it doesn't look like the XDoclet folks care to support the 1.2 version (see http://opensource.atlassian.com/project ... wse/XJD-41 ). It seems like they want to indulge in the fantasy that annotations don't make them irrelevant as they forge ahead on a whole new architecture. In the XDoclet postmortum, it will probably say something about them abandoning a stable program while their users jump ship: http://www.joelonsoftware.com/articles/ ... 00069.html

I hope im not coming off like a dick here. I actually like Hibernate a lot, the more I read and learn about it, the more I think "these guys really get it". Unfortunately, the more I look at XDoclet, the more I feel like Linda Blair.

I understand your view. The hibernate team is embracing annotations and once you see the annotation support start to come to light (very soon a alpha release with the beta 1 H3 release) you will start to see the 'Use Annotations Mantra'. The issue is just as you have said, the orginal XDoclet support 1.2.2 has been dropped for XDoclet2. My view is XDoclet 2 has not been managed well (even if its a good product etc bad PR, no offical releases etc). Having said that it appears XDoclet 2 does have good support for Hibernate and is being actively worked on.

http://www.sourceforge.net/projects/xdoclet-plugins/

In the short term I would like to see someone step up and just polish a few items in the XDoclet 1.2.x branch while XDoclet2 gets orgainsed. This will give the user base time to move the jdk5.0 and the future.

xdoclet 2 is organized and can be used in production. you only have to grab
relevant dependency specification for your maven.xml ( or download dependecies manually if you use ant ) and you are ready to go.

tag documentation is also up to time - it's generated automatically on regular basis