Abator generated classes are placed in directories based on the "targetProject" and "targetPackage" attributes - in effect, those two values are added together to determine the directory.  If you set the "enableSubPackages" property to true, then sub directories based on the database catalog and schema might be generated.
 
What results are you getting that don't seem right to you?
 
Jeff Butler
 
On 6/21/06, jeremy jardin <[EMAIL PROTECTED]> wrote:

Yes ! that's fine !

 

Don't you know how to precise where Abator should generate javabeans ?

Because I've tried to set it ine the target but it doesn't work ..

 

And so, my javabeans are generated in an unexpected package ..

 

??

 

 

 

-----Message d'origine-----
De : Jeff Butler [mailto: [EMAIL PROTECTED]]
Envoy� : mercredi 21 juin 2006 15:05
� : [email protected]
Objet : Re: "invalid column type'

 

Try this...in your Abator configuration, add a <columnOverride> for the timestamp fields like this:

 

<table tableName="myTable">

  <columnOverride column='TSTMPINSR" javaType="java.util.Date" jdbcType="TIMESTAMP"/>

  <columnOverride column='TSTMPUPDT" javaType="java.util.Date" jdbcType="TIMESTAMP"/>

</table>

 

then regenerate.

 

Strange that it didn't generate that way originally - the Oracle driver must be returning something wierd as the datatype for the columns.

 

Jeff Butler



 

On 6/21/06, jeremy jardin < [EMAIL PROTECTED]> wrote:

Hello,

 

I'm trying to insert user in my oracle database using ibatis framework.

I generated sql-map file using Abator plugin.

 

My table look like that :

 

UID       CHAR(36 Bytes)          

MOBILE           CHAR(12 Bytes)

 ORIGINE_UUID            CHAR(36 Bytes)

 ETAT   CHAR(10 Bytes)

LOGIN  CHAR(20 Bytes)

 ETAT_MODIFIE           CHAR(1 Bytes)

TSTMPINSR     TIMESTAMP(6)                        

TSTMPUPDT    TIMESTAMP(6)

 

I can see that Timestamp columns have been set as 'Object' in my javabean..

It should have been a "Date" type !

 

 

So, when I try to store my user, I have that exception :

 

--- Check the parameter mapping for the 'TSTMPUPDT' property. 

--- Cause: java.sql.SQLException: Type de colonne non valide

Caused by: java.sql.SQLException : Type de colonne non valide

 

What should I do ??

 

 

Thx

     

 

 

 


Reply via email to