]
Steve Ebersole commented on HHH-5024:
-------------------------------------
So this bug report is about misleading log message? Or does something really fail here?
MetadataContext#registerAttribute does not recognize inherited
fields
---------------------------------------------------------------------
Key: HHH-5024
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5024
Project: Hibernate Core
Issue Type: Bug
Components: entity-manager, metamodel
Affects Versions: 3.5.0-CR-2, 3.5.1, 4.0.0.Final
Environment: Hibernate 3.5.0-CR-2, JPA Modelgen 1.0.0-CR-1
Reporter: Adrian Hummel
Assignee: Steve Ebersole
Attachments: bugreport.zip, hhh-5024.zip
Time Spent: 3.5h
The embeddable class {{CustomerId}} (see attached ZIP) inherits from the base class
{{AbstractIdentity}} (annotated with {{@MappedSuperclass}}). The metamodel classes for
these two classes are correctly generated:
{code:title=AbstractIdentity_.java|borderStyle=solid}
import javax.persistence.metamodel.SingularAttribute;
import javax.persistence.metamodel.StaticMetamodel;
@StaticMetamodel(AbstractIdentity.class)
public abstract class AbstractIdentity_ {
public static volatile SingularAttribute<AbstractIdentity, String> id;
}
{code}
and
{code:title=CustomerId_.java|borderStyle=solid}
import javax.persistence.metamodel.StaticMetamodel;
@StaticMetamodel(CustomerId.class)
public abstract class CustomerId_ extends AbstractIdentity_ {
}
{code}
When building the entity manager factory, {{MetadataContext#registerAttribute}} (line
378) tries to resolve the field {{CustomerId_.id}} using {{Class#getDeclaredField}}. This
results in a {{NoSuchFieldException}} because the field is declared in the super class
{{AbstractIdentity_}}.
Proposed solution: Since all field declarations in the metamodel are public, the
{{Class#getField}} method should be used instead.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: