Hi,

We've created a program that creates pojos, hbm files and schemas.

The hbm part is based of the same technology as the usual ant task that everybody uses to create hbm from XDoclet-tagged pojos.

It works pretty well, despite all the guessing we did to build. It seens references to this kind of thing can't be found anywhere on the net.

The problem is, whenever the program comes across an @hibernate.set it locks up with an error in HibernateTagsHandler saying something about invoking method roleAtribute from template file hibernate-properties.xdt where it apparently didn't find something.

Ant generated pojos or the ones generated by our program work well with the old ant task, but none of them seens to escape this exception fate when our hbm generator is trying to generate the hbm files.

What can be wrong?

I use XDoclet 1.3.x on a production level software and we don't have many issues ever with it. You message sounded like you have created your own generator. Is that correct? Not sure that anyone can help you.

I'm using XDoclet 1.2.3 and yes, we've built our own generator using the same classes (libraries) used by the ant.

(I actually didn't do it, but I kept and eye on it since the beggining, once the guy who made it, or more actually 'guessed' it, sits by me.)

It's very strange, because it works nicelly with everything but 'set', it keeps spitting out this wierd error.

You said XDoclet 1.3.x? Where can I get it? On the XDoclet site I can only see the version I'm using. Maybe replacing the libraries (and with a little of adapting) it could work.

Because this looks to me like a technology bug (not exactly our own) although I can obviously be very wrong.

EDIT: To make it clearer: We rebuilt the ant process using java classes and the libraries the Ant uses. So, our code follows the same steps for generating the hbm.xml files the Ant follows. But, somehow, this results in a bug with @hibernate.set at some point. It's weird because we don't actually define anything in that direction within the code, much like the ant, so it shouldn't be messed.

Although we also have a strange problem with folders and pojo finding we don't have with the ant. But this one we managed to solve in a not very fine way.

The 1.3.x series is in source. A few binaries live around the joint because it has good support for Hibernate 3.x . Using Xdoclet 1.2.3 us fine and @hibernate.set works fine for me on a simple test case. If this did not work then there would be many-many users complaining. I suspect your integration some how is at fault - but you never know.

Good luck.

It's very strange. As I said, using an ant will result in sucess always.

But our program will always crash. And complaining about not finding the hibernate-properties.xdt but it finds the file when it needs it for hibernate.property or hibernate.many-to-one tags...

We just can't figure out what is happening. And the fact that what we're doing is not officially supported does not help...

I can understand that it is an odd case. Good luck finding the solution.