The database has a VARCHAR(1) field that may be Y or N, and I want to have it mapped as a Boolean in the entity class.

hibernate.reveng.xml has this:


YNBooleanType inherits from org.hibernate.type.BooleanType, so its getReturnedClass() function already does the right thing and returns Boolean.class.

However, the generated Pojo has


Now I knew that the standard reason for this is that the user type isn't on the classpath.
So I placed YNBooleanType in a jar file that I specifically added to the classpath. This didn't change anything.
In fact I think the class isn't loaded, I had added
to the class body, but the message never turned up (I do get "didn't report any primary key columns" message, so I'm pretty sure I'm looking at the right console).
Somehow it's ignoring the specified classpath.

I'm using the Classpath tab on the Hibernate Configuration from the Hibernate view.
Maybe that's the wrong classpath setting?

I'd like to make it log the classpath it's using to resolve user types - is there a way to raise the logging level when it's running inside Eclipse?

Turned out that subclassing a standard type like BooleanType is not the way to go, you need to write a subclass of UserType.
Hibernate's standard types are handled very differently from user types; for example, no user type can specify a type shorthand (which, incidentally, means you have to specify the full darn.long.user.type.fully.qualified.TypeName in hibernate.reveng.xml).

Oh. And the difference between a UserType and standard types can be as minor as having the standard types using getReturnedClasss() and UserType using returnedClass().
The kind of detail you tend to miss :-(

I have a patch for that!. do you know if there is a ticket for it?

Is there a way to ignore the foreign keys of all tables from my database ?