[
https://issues.apache.org/jira/browse/OPENJPA-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812530#comment-13812530
]
Mark Struberg commented on OPENJPA-2335:
----------------------------------------
The issue happens if an @OrderColumn on the @OneToMany side references a
(read-only) attribute in the entity. I'm not really sure if this is allowed by
the spec though:
" The order column is not visible as part of the state of the entity or
embeddable class."
It used to work without problems in openjpa-2.2.2 though.
This also seems to work fine in hibernate
http://stackoverflow.com/questions/2956171/jpa-2-0-ordercolumn-annotation-in-hibernate-3-5
> Constrained foreign key column value setting needs to be flexible
> ------------------------------------------------------------------
>
> Key: OPENJPA-2335
> URL: https://issues.apache.org/jira/browse/OPENJPA-2335
> Project: OpenJPA
> Issue Type: Bug
> Reporter: Pinaki Poddar
> Assignee: Pinaki Poddar
> Priority: Blocker
> Fix For: 2.3.0
>
>
> Should allow setting a column from default value to a non-default value. The
> logic had a bug.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
