[
https://issues.apache.org/jira/browse/OPENJPA-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602263#action_12602263
]
Tim Kaltenbrunner commented on OPENJPA-602:
-------------------------------------------
Hi,
I have the same problem at my current project. I have an existing database
structure created with Kodo JDO. Now I want to use OpenJPA but keep the old
database structure. Will someone fix this problem or will you only throw an
exception. I am also not sure if the specification specifies that this case
should be possible but JDO implementation do support it and therefore it would
be nice to have it in OpenJPA .
Cheers Tim
> NullPointerException at
> org.apache.openjpa.jdbc.meta.strats.RelationToManyInverseKeyFieldStrategy.map
> -----------------------------------------------------------------------------------------------------
>
> Key: OPENJPA-602
> URL: https://issues.apache.org/jira/browse/OPENJPA-602
> Project: OpenJPA
> Issue Type: Bug
> Components: jdbc
> Affects Versions: 1.1.0
> Reporter: Michael Vorburger
> Priority: Minor
> Attachments: FullStackTrace-OPENJPA-602.txt, OneToMany-test.zip
>
>
> The example I'll attach crashes with an NPE when running the mappingtool.
> Caused by: java.lang.NullPointerException
> at
> org.apache.openjpa.jdbc.meta.strats.RelationToManyInverseKeyFieldStrategy.map(RelationToManyInverseKeyFieldStrategy.java:136)
> at
> org.apache.openjpa.jdbc.meta.strats.RelationCollectionInverseKeyFieldStrategy.map(RelationCollectionInverseKeyFieldStrategy.java:95)
> at
> org.apache.openjpa.jdbc.meta.FieldMapping.setStrategy(FieldMapping.java:120)
> at
> org.apache.openjpa.jdbc.meta.RuntimeStrategyInstaller.installStrategy(RuntimeStrategyInstaller.java:80)
> at
> org.apache.openjpa.jdbc.meta.FieldMapping.resolveMapping(FieldMapping.java:438)
> at
> org.apache.openjpa.jdbc.meta.FieldMapping.resolve(FieldMapping.java:403)
> at
> org.apache.openjpa.jdbc.meta.ClassMapping.resolveMapping(ClassMapping.java:812)
> The goal of this JIRA is not (neccessarily) to support the kind of mapping
> that would be required for this (which may be hard), but to at least print a
> clear error and not an NPE...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.