-
1. Re: seam-gen vs. Oracle CHAR(n) and FLOAT
steve_of_ar May 9, 2007 3:00 PM (in response to steve_of_ar)PS: by changing the FLOAT column's generated property to java type "float" fixes that one.
Again, I'm more worried about the CHAR(n) problem: I'm assuming it wants an char[n] type entity property, but I'd rather have a regular String, if possible... -
2. Re: seam-gen vs. Oracle CHAR(n) and FLOAT
steve_of_ar May 9, 2007 3:03 PM (in response to steve_of_ar)PPS: JBoss 4.05, Seam 1.2.0.PATCH1
-
3. Re: seam-gen vs. Oracle CHAR(n) and FLOAT
steve_of_ar May 9, 2007 3:12 PM (in response to steve_of_ar)Actually it's Version 1.2.1.GA (somebody needs to change it in the readme.txt)
-
4. Re: seam-gen vs. Oracle CHAR(n) and FLOAT
steve_of_ar May 10, 2007 10:33 AM (in response to steve_of_ar)Anybody?
Recap: CHAR(n) in Oracle aren't usable currently (unfortunately I can't change the schema). Seam-gen maps it as a String, which fails during deployment. I tried changing the entity field to char[] but that also fails during deployment. It always expects the database field to be VARCHAR for some reason. -
5. Re: seam-gen vs. Oracle CHAR(n) and FLOAT
pmuir May 10, 2007 10:53 AM (in response to steve_of_ar)Seam-gen's reverse engineering is based on Hibernate Tools - you may have found a flaw. Please report it in JIRA (JBSEAM or Hibernate Tools). You'll need to correct the generated Entity yourself - you'll probably get more help on a Hibernate forum - I've never tried mapping hibernate onto oracle I'm afraid.