[ https://issues.apache.org/jira/browse/OPENJPA-1100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated OPENJPA-1100: ---------------------------------- Affects Version/s: 1.3.0 2.0.0-M2 Fix Version/s: (was: 2.0.0-M4) (was: 2.0.0) > @Version-Annotation on Column with unsupported type (e.g. BigDecimal) is silently ignored, but should raise an error > -------------------------------------------------------------------------------------------------------------------- > > Key: OPENJPA-1100 > URL: https://issues.apache.org/jira/browse/OPENJPA-1100 > Project: OpenJPA > Issue Type: Bug > Affects Versions: 1.2.1, 1.3.0, 2.0.0-M2 > Environment: Windows XP, Java SDK 1.6, Websphere 6.1 + openJPA 1.2.1 > Reporter: Heiko Kopp > Assignee: Pinaki Poddar > Fix For: 2.0.0-M3 > > > In the following example, the @Version annotated field 'version' does have a wrong type (none of the supported ones). > @Entity > @Table(name = "PARTNER", schema = "PART") > public class Partner > { > @Id > @Column(name = "PART_KEY") > private BigDecimal partKey; > @OneToMany(mappedBy = "partner", fetch = FetchType.LAZY) > private List rollen; > } > @Entity > @Table(name = "PARTNERROLLE") > public class PartnerRolle > { > @EmbeddedId > private PartnerRolleKey key; > @Version > @Column(name = "VERSION") > private BigDecimal version; > @ManyToOne(fetch = FetchType.LAZY) > @JoinColumn(name = "PART_KEY") > private Partner partner; > } > This does NOT lead to an error but silently omits the column in any query statements. The prepared statement (prepstmt) simply omitts the column. If the @Version is removed or a supported type like 'long' is used, the behaviour is correct. > Best regards, > Heiko -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.