-->
These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

All times are UTC - 5 hours [ DST ]



Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 3 posts ] 
Author Message
 Post subject: @MappedSuperclass not saving after upgrading to 5.0
PostPosted: Fri Jan 27, 2017 8:18 am 
Newbie

Joined: Fri Jan 27, 2017 8:11 am
Posts: 2
We're just moving from wildfly 9.0 to 10.1 (hibernate 4.3.10 to 5.0.10) and have found that for some of our @MappedSuperclass usage updates to Entities are no longer saved to the database.

Specifically when the extending class does not add any additional @Columns updating an Entity fails (the updates are not persisted). Adding one or more additional @Columns and all works fine.

Creating and em.persist()ing a new Entity works fine, its later find()ing the Entity and updating it that does not get saved.

As a workaround we've moved one of the @Columns into the extending classes so we can continue testing the system for the update to wf10


Top
 Profile  
 
 Post subject: Re: @MappedSuperclass not saving after upgrading to 5.0
PostPosted: Fri Jan 27, 2017 8:42 am 
Hibernate Team
Hibernate Team

Joined: Thu Sep 11, 2014 2:50 am
Posts: 1638
Location: Romania
Sounds like a bug. You should provide a replicating test case and open a Jira issue. I think you can just replicate it with Hibernate alone, you probably don't need Wildfly. Just test it with the particular version of Hibernate that Wildfly comes bundled with.

_________________
If you liked my answer, you are going to love my High-Performance Java Persistence book and my blog as well.


Top
 Profile  
 
 Post subject: Re: @MappedSuperclass not saving after upgrading to 5.0
PostPosted: Fri Jan 27, 2017 10:26 am 
Newbie

Joined: Fri Jan 27, 2017 8:11 am
Posts: 2
vlad wrote:
Sounds like a bug. You should provide a replicating test case and open a Jira issue. I think you can just replicate it with Hibernate alone, you probably don't need Wildfly. Just test it with the particular version of Hibernate that Wildfly comes bundled with.


Thanks.

I think the best plan may be to continue testing everything else with our current workaround, and then I should be able to carve out some time next week to put together a test case for submission (we're a little against the clock right now :)


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 3 posts ] 

All times are UTC - 5 hours [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.