Ok, so after spending days sorting through the docs for the hibernate tools there seems to be some sort of transition going on. A lot of the examples were written for hibernate2 and apparently a different strategy is going on in hibernate3.

Could someone clearly describe what is going on? I am after this functionality: from an ant task, generate pojo's from HBM files using the split pattern (generated super class and concrete subclass, empty initially) using a custom template (velocity...)

Can this be done with hibernate3 tools? If so, would someone be kind enough to point me in the right direction for a working example? The docs on the hibernate.org site for tools seem to be gone too...

Thank you in advance, sorry if this has been answered -- there is just so little information that I can find and most of it contradicts each other...

-s

Sigh.

Even if this link worked, which it doesn't right now, there is no working example of a split java generation operation from ant with custom templates.

http://www.hibernate.org/hib_docs/tools/ant/index.html

404 error...

Is ANYBODY doing this?

why are you referring to old links that is nowhere near tools.hibernate.org ?

http://www.hibernate.org/hib_docs/tools ... l/ant.html

that one is available from tools.hibernate.org

sigh!

Ooops...my bad. The bookmark came from an answer you gave to someone else earlier -- sorry about that. :)

I've read those docs now and I have a custom velocity template working by placing a directory named "pojo" with a pojo.vm in it in the classpath before the tools jar and using the hbm2java task.

However, I really don't see a way to do the generation gap pattern _Entity.java with the properties and creation of an Entity.java that derives from _Entity.java if it doesn't exist for concrete code.

I'm willing to believe that I'm being dense... a pointer would be appreciated in that case. Sorry about the "sigh" up above, I was feeling pretty frustrated that day, I appreciate the work of the tools team!

Thanks,

<class name="Entity">
<meta attribute="generated-class">_Entity</meta>
....
</class>

we will hopefully get around adding the feature where all classes does this automatically (which some people seem to prefer for some weird reason ;)