Forcing java.sql.Date datatype with Hbm2JavaTask

rich · **Joined:** Sat Dec 20, 2003 5:09 pm **Posts:** 38

Does anyone know if it's possible to force the hibernate class generation tool to import java.sql.Date in the resultant class? No matter what I do, the resultant class always imports java.util.Date.

beanUtils bails when I try to do a bean copy/type translation from a HashMap to the hibernate bean when the corresponding field in the Hibernate bean is of type java.util.Date.

Thanks in advance,

Rich

max · **Posted:** Fri Jul 16, 2004 1:32 am

use type="java.sql.Date" ?

rich · **Joined:** Sat Dec 20, 2003 5:09 pm **Posts:** 38

I thought that too, but when I explicitly set the type in the conf file, e.g.

property name="cc_date" column="cc_date" type="java.sql.Date">
<meta attribute="field-description">The visit date.</meta>
</property>

The hibernate tool still puts

import java.util.Date;

at the top of the resultant src file. Dunno.

max · **Posted:** Fri Jul 16, 2004 9:02 am

if you are sure - then please make a jira bug for it

rich · **Joined:** Sat Dec 20, 2003 5:09 pm **Posts:** 38

I'll create a simple test to verify and be absolutely sure. (My particular mapping file has a lot of stuff in it).

Thanks for the notes.

rich · **Joined:** Sat Dec 20, 2003 5:09 pm **Posts:** 38

I finally found the time to create a simple test and my first observation was correct. For interest, I included the XML, the java task, and the resultant file below.

Thanks for the input.

XML file:

Code:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD 2.0//EN"
                                   "http://hibernate.sourceforge.net/hibernate-mapping-2.0.dtd">


<hibernate-mapping>

    <class name = "com.myTest.hibernate.Test" table="test">

        <id name="id" type="int" column="id" unsaved-value="0">
            <meta attribute="scope-set">protected</meta>
            <meta attribute="field-description">prospects primary key</meta>
            <generator class="sequence">
                <param name="sequence">mmseq</param>
            </generator>
        </id>

        <property name="test_field" column="test" type="java.sql.Date" not-null="true"></property>
                                      
    </class>
    
</hibernate-mapping>

Ant Task used to build:

Code:

    <taskdef name         = "hbm2java"
             classname    = "net.sf.hibernate.tool.hbm2java.Hbm2JavaTask"
             classpathref = "project.class.path"/>
             
    <target name="codegen" description = "Generate Java source from the O/R mapping files">
   
       <hbm2java output = "src">
           <fileset dir = "src">
               <include name = "**/*.hbm.xml"/>
           </fileset>
      </hbm2java>
          
   </target> 

And the resultant file (I only listed the top for brevity). Note that java.util.Date is imported, not java.util.SQL

Code:

package com.myTest.hibernate;

import java.io.Serializable;
import java.util.Date;
import org.apache.commons.lang.builder.ToStringBuilder;


/** @author Hibernate CodeGenerator */
public class Test implements Serializable {

    /** identifier field */
    private int id;

    /** persistent field */
    private Date test_field;

    /** full constructor */
    public Test(Date test_field) {
        this.test_field = test_field;
    }

    /** default constructor */
    public Test() {

rich · **Joined:** Sat Dec 20, 2003 5:09 pm **Posts:** 38

Hmm, same thing happens with java.sql.Time and java.sql.Timestamp

max · **Posted:** Fri Jul 16, 2004 6:49 pm

Until I get time to look into this you should be able to override the behavior by supplying <meta attribute="property-type">whateveryouwant</meta>

rich · **Joined:** Sat Dec 20, 2003 5:09 pm **Posts:** 38

Very cool. Didn't know I could do that. Thanks a million.

rich · **Joined:** Sat Dec 20, 2003 5:09 pm **Posts:** 38

That sort of works ...

The type of all the variables has been changed, but the import statement stays the same. So compilation fails due to "cannot resolve symbol". Still, it's much better. Thanks for the tip.

I noticed Gavin posted a comment to the bug report and thought the code generatio tool was working as it should. This is my first stab at using the codegent tool - am I going about it in the wrong way?

rich · **Joined:** Sat Dec 20, 2003 5:09 pm **Posts:** 38

OK, I'm a dummy. I should of seen <extra-import>. I still get compiler errors using that attribute, but I'm getting closer. I'll play with it.

Thanks again for the comments.