Eclipse Community Forums: EclipseLink » Ordered collections: ordered-column causes NPE

Help

Home

Home » Eclipse Projects » EclipseLink » Ordered collections: ordered-column causes NPE

Show: Today's Messages :: Show Polls :: Message Navigator

Ordered collections: ordered-column causes NPE [message #1248347]

Mon, 17 February 2014 06:47

yuan yao

Messages: 6
Registered: February 2014

Junior Member

Any one who use <order-column> with many-to-many or one-to-many associations?

I came with a NPE when I used <order-column>.

<many-to-many name="games" target-entity="GiftGame" attribute-type="java.util.List">
    <order-column name="idx" correction-type="READ_WRITE"></order-column>
    <join-table name="gift_games">
        <join-column name="gift_id" table="gift_games" />
        <inverse-join-column name="game_id" table="gift_games" />
    </join-table>
</many-to-many>

Caused by: Exception [EclipseLink-28018] (Eclipse Persistence Services - 2.5.0.v20130507-3faac2b): org.eclipse.persistence.exceptions.EntityManagerSetupException
Exception Description: Predeployment of PersistenceUnit [cms] failed.
Internal Exception: java.lang.NullPointerException
	at org.eclipse.persistence.exceptions.EntityManagerSetupException.predeployFailed(EntityManagerSetupException.java:230)
	... 62 more
Caused by: java.lang.NullPointerException
	at org.eclipse.persistence.internal.jpa.metadata.columns.OrderColumnMetadata.process(OrderColumnMetadata.java:98)
	at org.eclipse.persistence.internal.jpa.metadata.accessors.mappings.CollectionAccessor.process(CollectionAccessor.java:670)
	at org.eclipse.persistence.internal.jpa.metadata.accessors.mappings.ManyToManyAccessor.process(ManyToManyAccessor.java:143)
	at org.eclipse.persistence.internal.jpa.metadata.MetadataProject.processOwningRelationshipAccessors(MetadataProject.java:1578)
	at org.eclipse.persistence.internal.jpa.metadata.MetadataProject.processStage3(MetadataProject.java:1831)
	at org.eclipse.persistence.internal.jpa.metadata.MetadataProcessor.processORMMetadata(MetadataProcessor.java:580)
	at org.eclipse.persistence.internal.jpa.deployment.PersistenceUnitProcessor.processORMetadata(PersistenceUnitProcessor.java:585)
	at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.predeploy(EntityManagerSetupImpl.java:1865)
	... 60 more

I found @OrderedColumn annotation could work. But the cosponding XML element will cause the NPE.

EclipseLink version: 2.5

[Updated on: Mon, 17 February 2014 06:48]

Report message to a moderator

Re: Ordered collections: ordered-column causes NPE [message #1249770 is a reply to message #1248347]

Tue, 18 February 2014 15:55

Chris Delahunt

Messages: 1236
Registered: July 2009

Senior Member

The JPA specification defines an @OrderColumn if that is what you are refering to:
http://docs.oracle.com/javaee/6/api/javax/persistence/OrderColumn.html
The XML equivalent would be <order-column name="idx"/> as shown here:
https://wiki.eclipse.org/EclipseLink/Examples/JPA/2.0/OrderColumns

Try removing the correction-type which isn't defined in JPA.

Report message to a moderator

Re: Ordered collections: ordered-column causes NPE [message #1252204 is a reply to message #1249770]

Fri, 21 February 2014 02:09

yuan yao

Messages: 6
Registered: February 2014

Junior Member

Thanks for your reply.

@OrderColumn works well.

NPE still occurs after removing the 'correction-type'.
Changing many-to-many to one-to-many doesn't solve the problem.

The wiki' demo doesn't use the join table. But here I must use it for many-to-many.

No one ever uses many-to-many && join table && order-column successfully?

Report message to a moderator

Re: Ordered collections: ordered-column causes NPE [message #1266572 is a reply to message #1252204]

Fri, 07 March 2014 17:00

Clovis Wichoski

Messages: 7
Registered: March 2012

Junior Member

Hi Yuan,

Have you tried that with version 2.5.1? Can you download the sources of your EclipseLink version and check what are the nearby instrucions of code that causes the NPE? I post a issue here where I found some problem with multi-threads environment, maybe your problem can occurs with multi-threads too.

best regards

Clóvis

Report message to a moderator

Re: Ordered collections: ordered-column causes NPE [message #1269578 is a reply to message #1266572]

Wed, 12 March 2014 02:04

yuan yao

Messages: 6
Registered: February 2014

Junior Member

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.

Report message to a moderator

Previous Topic:	[SOLVED] For each call a new connection? Need only one when using RCP with Gemini or Swing
Next Topic:	JDBC bind parameters only for one of them

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sat Jun 24 20:58:48 GMT 2017

.:: Contact :: Home ::.