Jeffrey Blatttman commented on OPENJPA-191:

note, per patrick linkskey, vanilla JPA does not require this functionality. i 
believe it says that only simple types plus String, Date, and a few others may 
be used as the fields in a composite ID. but he states that this is expected to 
work with open jpa.

> cannot define composite ID that incorproates @ManyToOne field
> -------------------------------------------------------------
>                 Key: OPENJPA-191
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-191
>             Project: OpenJPA
>          Issue Type: Bug
>    Affects Versions: 0.9.6
>         Environment: java se 5
> derby
>            Reporter: Jeffrey Blatttman
>            Priority: Minor
>         Attachments: book.zip
> cannot define composite ID that incorproates @ManyToOne field. see sample 
> test case attached (book.zip). this is a maven2 project, and you can 
> reproduce the bug by starting derby on localhost and doing a "mvn install". 
> the resulting error message during enhancement is:
>     [java] Exception in thread "main" <4|true|0.9.6-incubating> 
> org.apache.openjpa.util.MetaDataException: The id class specified by type 
> "class com.mycompany.book.Page" does not match the primary key fields of the 
> class.  Make sure your identity class has the same primary keys as your 
> persistent type, that the access types are the same, and if you are getting 
> this error at runtime, that you have your persistent class since last 
> compiling your identity class.
>      [java] FailedObject: book [java.lang.String]

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

Reply via email to