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

Marc Schipperheyn (JIRA) noreply at atlassian.com
Wed Nov 23 11:00:20 EST 2011


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

Marc Schipperheyn commented on HHH-5732:
----------------------------------------

A suggestion I saw elsewhere seems to resolve the issue for me, although it shouldn't 
replacing 

cascade=CascadeType.All

with

cascade={ CascadeType.MERGE, CascadeType.REMOVE, CascadeType.REFRESH, CascadeType.PERSIST }

> @OrderColumn not updated if @OneToMany has mappedby defined
> -----------------------------------------------------------
>
>                 Key: HHH-5732
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5732
>             Project: Hibernate Core
>          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