Hey danch, good to see you around again...
EJB3 is built upon Hibernate. if you look at the ejb3/build-test.xml you'll see a target entity2xml. This takes a set of classes and generates a Hibernate xml.
Also, did you change Hibernate.properties to use the postgres dialect?
also, JBoss's ejb3 impl currently ignores columnDefinition. There's still a lot of dotting of the 'i's and crossing of the 't's implementation left to do...
You know, I didn't even notice that the column definition wasn't getting picked up. I put that in earlier when I was going against the EJB3 preview release (which wasn't doing anything with my dependents).
I know hibernate would do what I need quite nicely, I'm looking for a way to tell it to do it through the EJB3 annotations, really. Do you think this sort of situation will be addressed in the spec at some point? Another thing that occurred to me is arrays of dependents (which I believe Hibernate will also do natively, but doesn't seem to be addressed by EJB3)