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

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 :)