[
https://jira.jboss.org/jira/browse/JBSEAM-3298?page=com.atlassian.jira.pl...
]
Valerie Griffin updated JBSEAM-3298:
------------------------------------
Attachment: EntityHome.java.ftl
GetPropertyAnnotation.ftl
These files allow use of hibernate yes_no. The change to EntityHome resolves a syntax
error caused by a boolean value in a composite key.
This is not really a complete fix because there is no test in the code for the hibernate
type. According to a post in the hibernate forum, Hibernate is failing to include the
yes_no annotation so I don't know if all of this belongs in seam-gen.
seam-gen doesn't handle hibernate types such as yes_no
------------------------------------------------------
Key: JBSEAM-3298
URL:
https://jira.jboss.org/jira/browse/JBSEAM-3298
Project: Seam
Issue Type: Bug
Components: Tools
Affects Versions: 2.0.3.CR1
Environment: JBoss 4.2.2, DB2, Linux
Reporter: Valerie Griffin
Attachments: EntityHome.java.ftl, GetPropertyAnnotation.ftl
My database has quite a few CHAR(1) entries used as boolean values where the field can
contain Y or N. I defined these entries as hibernate yes_no in the seam-gen.reveng.xml
file, but the code didn't reflect the data type. To work, the field needs to be
annotated with
@Type(type = "yes_no")
and needs to not contain an annotation like:
@Length(max = 1)
If the Type annotation is absent, hibernate detects a schema mismatch. (It expects a
numeric boolean value.)
If there's a Length annotation, the UI's checkbox displays a surprising error
message about the data length.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira