Sounds like an over-cautious validation message originating in OpenJPA's heritage -- the JDO spec (which Kodo implements on top of OpenJPA) places those requirements on the object IDs.
If you could post the full stack trace and the relevant snippets from your domain model, it'd help the debugging process considerably. Thanks, -Patrick -- Patrick Linskey BEA Systems, Inc. _______________________________________________________________________ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. > -----Original Message----- > From: jeff [mailto:[EMAIL PROTECTED] > Sent: Monday, March 26, 2007 4:35 PM > To: open-jpa-dev@incubator.apache.org > Subject: ID class: no public string or class + string constructor? > > getting this error: > > The id type "class com.sun.portal.pom.FooId" specfied by > persistent type "class com.sun.portal.pom.Foo" does not have > a public string or class + string constructor. > > this error doesn't seem to correspond to any of the > requirements of an ID class as defined in the spec. > > my first guess is that it wants me to add an constructor that > takes the result of toString() and constructs the ID class > based on that, but adding a constructor that takes a string > arg didn't change the error. i don't understand what it would > want for the "class + string" constructor, so i was not sure > what to try there. > > can someone help interpret this error? > thanks! > > > > > --------------------------------- > Never miss an email again! > Yahoo! Toolbar alerts you the instant new Mail arrives. Check it out. > Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.
