Using latest compilation from CVS of hibernate-tools3.0.1-beta1


I've been reading and experiencing the different ways the newest tools generates java types such as Boolean vs boolean, and Integer vs integer.

I just want to confirm my findings before I go ahead and change all my exisiting mapping files.

First, Is it true that if my old tools code produced "Boolean" or "Integer" (the higher level Java type) when my mapping documents had the type equal to "boolean" and "integer", that will no longer work? With the latest code I'm seeing that it produces the primitive types "boolean" and "integer".

Second, to fix this, am I going to have to change all my mapping documents to explicitly say "Boolean" and "Integer" to produce the same code as before?

Thanks.

as far as i know we actually have the same rules as before - but we used nullability to influence it but that is also wrong in other cases.....because nullability in the db level does not mean it cannot be null in the oo model. but yes, right now you will have to change the mappings to list what you actually want.