In our project we have a overridden attribute in an sub class of a mapped superclass.
Doing so to add a BeanValidation @NotEmpty annotation.

With Hibernate Version 4.3.1 everything was OK

We updated to hibernate 5.0.10 (coming with wildfly 10.1).
After that the metamodel for the overridden attribute of the sub class is not initialized and staying null.
Only the metamodel attribute for the mapped superclass is initialized.

I am not sure is this a bug in hibernate or if we do something we should not do?

Happy about any suggestions.
Thanks,
Oliver

Can you post your mappings, the persistence logic, and the actual stack trace?

Hello Vlad,
thank you for your time.
I altered the test MappedSuperclassWithAttributesTest a little bit to demonstrate my problem.

https://github.com/hibernate/hibernate-orm/commit/03fbf2c4e2fa309ebcc45bacb5fa354905001a05

In line 50 of MappedSuperclassWithAttributesTest Product_.overridenName is null.

Best regards,
Oliver

As far as I know, properties cannot be overridden with different a mapping, so I'm not sure why you are overriding the base class property. What is your use case?

I donot change the mapping. I add an additional bean validation annotation.
My usecase is to add a @NotEmpty annotation.

The test case simplifies a little bit, the real class structure is more complex.

In the base class the property is not required, but it is in the extending class. So the metamodel for both classes contains the same property.
With hibernate 4.3.11, both were initialized, with 5.x that is not the case for the extending class.
So I bumped into this because of upgrading our wildfly to version 10.1.

So if I am doing something forbidden should not hibernate fail some where earlier with an appropriate message?

I asked Gunnar and he explained to me that the BV rules are cumulative from base class to the extended one, so your use case is valid.

I think you should open a Jira ticket and add a replicated test case for your issue.