Tomáš Vála

Resulting metamodel classes do not have correct types where expected. All parametrized types are translated to mere Object in superclass and subclasses.

Do we agree that in the super type Object needs to be used? We cannot have multiple versions of the class really. Which leaves the sub-class. I guess the solution mentioned above is the best I can think of, but then again, the spec says:

For every persistent non-collection-valued attribute y declared by class X, where the type of y
is Y, the metamodel class must contain a declaration as follows:

public static volatile SingularAttribute<X, Y> y;

And the sub-types do not declare the fields/properties in question.