|
|
|
|
Re: Ordered collections: ordered-column causes NPE [message #1269578 is a reply to message #1266572] |
Tue, 11 March 2014 22:04  |
Eclipse User |
|
|
|
2.5.1 not work either. The same exception is thrown.
The line that throws exceptions:
org.eclipse.persistence.internal.jpa.metadata.columns.OrderColumnMetadata.process(OrderColumnMetadata.java:98)
if (((MetadataAnnotatedElement) getAccessibleObject()).getRawClass(descriptor).isList()) {
I debug it and found '((MetadataAnnotatedElement) getAccessibleObject()).getRawClass(descriptor)' return null.
The following is the flow of getRawClass(). I mark the flow with comments.
org.eclipse.persistence.internal.jpa.metadata.accessors.objects.MetadataAnnotatedElement.getRawClass(MetadataDescriptor)
public MetadataClass getRawClass(MetadataDescriptor descriptor) {
if (m_rawClass == null) { // Yuan: here
if (isGenericType()) { // Yuan: here, false
// ...
}
return getMetadataClass(getType()); // Yuan: here, getType() return null!
}
return m_rawClass;
}
1. I feel that the key is 'generic type'. My entities are virtul and not generic typed. So some type info could not be inferred?
2. I use the file orm.xml, not annotations. But why codes run into MetadataAnnotatedElement?
Hope that these fact useful to you.
|
|
|
Powered by
FUDForum. Page generated in 0.04415 seconds