Re: composite ID based on one side of a bidirectional one-many relationship

2007-04-01 Thread Craig L Russell
it. -Original Message- From: jeff [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 28, 2007 10:31 AM To: open-jpa-dev@incubator.apache.org Subject: RE: composite ID based on one side of a bidirectional one-many relationship yes, i see the problem w/ the attached classes, and with a completely

RE: composite ID based on one side of a bidirectional one-many relationship

2007-03-28 Thread jeff
it. -Original Message- From: jeff [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 27, 2007 1:42 PM To: open-jpa-dev@incubator.apache.org Subject: RE: composite ID based on one side of a bidirectional one-many relationship Patrick Linskey wrote: my ID class has a book field

RE: composite ID based on one side of a bidirectional one-many relationship

2007-03-28 Thread Patrick Linskey
return this by email and then delete it. -Original Message- From: jeff [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 28, 2007 10:31 AM To: open-jpa-dev@incubator.apache.org Subject: RE: composite ID based on one side of a bidirectional one-many relationship yes, i see

RE: composite ID based on one side of a bidirectional one-many relationship

2007-03-28 Thread jeff
] Sent: Wednesday, March 28, 2007 10:31 AM To: open-jpa-dev@incubator.apache.org Subject: RE: composite ID based on one side of a bidirectional one-many relationship yes, i see the problem w/ the attached classes, and with a completely different model where i am trying to accomplish

Re: composite ID based on one side of a bidirectional one-many relationship

2007-03-28 Thread Abe White
the book field in the PageId class must be of type String to match the primary key field type of Book was i mistaken when i understood you to say that Page could have a PK field of type Book? No, you weren't mistaken. But as I said, the book field in the Page*Id* class must match the

RE: composite ID based on one side of a bidirectional one-many relationship

2007-03-28 Thread Pinaki Poddar
, March 28, 2007 4:35 PM To: open-jpa-dev@incubator.apache.org Subject: RE: composite ID based on one side of a bidirectional one-many relationship hi, abe closed this with the reasoning ... the book field in the PageId class must be of type String to match the primary key field type of Book

RE: composite ID based on one side of a bidirectional one-many relationship

2007-03-27 Thread Patrick Linskey
received this message in error, please immediately return this by email and then delete it. -Original Message- From: jeff [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 27, 2007 1:06 PM To: open-jpa-dev@incubator.apache.org Subject: RE: composite ID based on one side of a bidirectional

RE: composite ID based on one side of a bidirectional one-many relationship

2007-03-27 Thread jeff
Patrick Linskey [EMAIL PROTECTED] wrote: my ID class has a book field, and getters and setters for it to match Page's book field. i wonder about the last line where it says java.lang.String. that seems odd. Can you post your Book and Page classes and the Page's IdClass? attached. i keep

RE: composite ID based on one side of a bidirectional one-many relationship

2007-03-27 Thread Patrick Linskey
, please immediately return this by email and then delete it. -Original Message- From: jeff [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 27, 2007 1:42 PM To: open-jpa-dev@incubator.apache.org Subject: RE: composite ID based on one side of a bidirectional one-many relationship