Hbm2Java & custom UserType problem in Hibernate-3

esyed · **Joined:** Thu Jun 08, 2006 11:57 am **Posts:** 7

By mistake, I have posted the following problem in the Hibernate-Users mailing list. Not sure if it needs re-post here.. but here is the link to the thread.

http://forum.hibernate.org/viewtopic.php?t=960972

And, was there a reason why the tooling for hbm2java has changed the way it did from Hibernate-2.1.7 to Hibernate-3.1.0-beta4.

max · **Posted:** Wed Jun 21, 2006 3:19 am

It works as expected as long as you remember to put that usertype in the classpath otherwise we cannot load the usertype and determine the returned class.

esyed · **Joined:** Thu Jun 08, 2006 11:57 am **Posts:** 7

Just to clarify:
Are you saying that the following snippet from the hibernate-mapping file

Code:

        <property column="LAST_MODIFIED" length="11" name="lastModified"
            type="com.company.hibernate.usertypes.LastModifiedColumnType">
            <meta attribute="use-in-tostring">true</meta>
            <meta attribute="default-value">new java.util.Date()</meta>
        </property>

will still produce the following code using the new hbm2java (hibernate-tool) task when we add the Custom UserType to the tooling class-path.

Code:

 /** nullable persistent field */
protected Date lastModified = new java.util.Date(); 

Thanks for helping out..

max · **Posted:** Wed Jun 21, 2006 5:13 pm

yes of course, just as was required in the old tools.

esyed · **Joined:** Thu Jun 08, 2006 11:57 am **Posts:** 7

Max, .. the trick was Great. (adding the dependency to the tooling classpath) solved the problem with the usertype. Question: Does the trick also applies to the following ?

Code:

       <property column="UPDATE_DATE" length="11" name="updateDate" not-null="true"
          type="java.sql.Timestamp">
          <meta attribute="use-in-tostring">true</meta>
          <meta attribute="default-value">new java.util.Date()</meta>
       </property>

Here the java.sql.timestamp is from Sun's jav2sdk1.4.2/jre/lib/rt.jar. I added the rt.jar to the tooling classpath but I dont think hibernate is loading the class as it did for CustomUserType and produces the following code in pojo.

Code:

protected Timestamp updateDate = new java.util.Date();

Causing the following error:

Code:

/home/esyed/hibernate-migration/components/taxonomy/target/generated-src/hbm2java/com/company/portal/taxonomy/model/Link.java:[26,38] incompatible types
found   : java.util.Date
required: java.sql.Timestamp

In Hibernate-2, the same mapping snippet resulted in

Code:

protected Date updateDate = new java.util.Date();

I hope you have some trick that can solve this issue too..

esyed · **Joined:** Thu Jun 08, 2006 11:57 am **Posts:** 7

fyi.. I fixed the posted problem by writing a new Custom UserType (UpdateDateUserType) and the pojo's generate the same code as in hibernate-2. For some reason, in the mapping file you cant pass the java.sql.Timestamp in type for a property. Here is how the modified snippet looks like:

Code:

       <property column="UPDATE_DATE" length="11" name="updateDate" not-null="true"
          type="com.company.hibernate.usertypes.UpdateDateUserType">
          <meta attribute="use-in-tostring">true</meta>
          <meta attribute="default-value">new java.util.Date()</meta>
       </property>

and the generated code in pojo..

Code:

protected Date createDate = new java.util.Date();

Not sure, if there was any other way to accomplish the same. But, adding rt.jar from sun (has java.sql.Timestamp) to the tooling classpath didnt help. Going the route of creating a new CustomType fixed it. Max, might know the fix & suggest something else when he checks this. Thanks.

max · **Posted:** Thu Jun 22, 2006 5:01 pm

put that in jira - i'll need to check if it is correct behavior or not.