We have specified the <class> persister attribute for some .hbm.xml files.

When we do a clean build we hit a 'chicken or the egg' problem.

We can't compile the persister since it relies on other classes, which are blown are by our 'clean' ant task.

We also can't run hiberatetool since it goes looking for the compiled persister class and of course its not there -- since it was 'clean'ed.

So, since the persister attribute doesn't (seem to) affect code generation, why does hibernatetool care about it?

Is there some way to tell hibernatetool to sort of ignore the persister attribute, since it doesn't do anything with it (as far as I can tell).

Thanks,

hard one to solve if its true...the persiter is needed for generating hbm.xml. i think it is already in jira; but please check.

It is something that requires a fix in how hibernate core parses mapping files.

hack/workaround: have a stubbed set of classes for the persister that just implements the interface and put that on the classpath when you use the codegeneration facilities.

but it doesn't affect the generated classes whatsoever.

We can look at the stubbed classes approach but would imagine it is probably easier if hibernate tools are changed to ignore the persister attribute contents, i.e. don't verify if its an existing class, or at least provide some tool options to ignore validating whether classes not used by hibernate tool are on the classpath.

Thanks,

yes, and as i wrote that is hibernate core parsing this; so it is the core that needs to have this change.