[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-5732) @OrderColumn not updated if @OneToMany has mappedby defined

Karsten Wutzke (JIRA) noreply at atlassian.com
Wed Jan 18 02:18:11 EST 2012


    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45162#comment-45162 ] 

Karsten Wutzke commented on HHH-5732:
-------------------------------------

What's the status on this? Has in been fixed for Hibernate 4? This is yet another Hibernate-JPA head-shaker. What's the voting system there for anyway?

> @OrderColumn not updated if @OneToMany has mappedby defined
> -----------------------------------------------------------
>
>                 Key: HHH-5732
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5732
>             Project: Hibernate ORM
>          Issue Type: Bug
>          Components: entity-manager
>    Affects Versions: 3.6.0
>            Reporter: Jaroslaw Lewandowski
>         Attachments: Screen shot 2011-01-10 at 21.41.27.png, TestOrderColumn.zip
>
>
> As I'm not able to reopen HHH-5378 I'm creating a new one. There is nothing said in JPA2.0 documentation that with @OrderColumn are any limitations regarding of usage mappedBy attribute on @OneToMany annotation. As I mentioned in the comments of that issue - even Hibernate documentation http://docs.jboss.org/hibernate/core/3.6/reference/en-US/html/collections.html#collections-indexed uses example which fails when executed with 3.6.0.Final version.
> Test case attached.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the hibernate-issues mailing list