This looks to be the problem (thanks Abe) It has caused another exception to come up but let me look into it and see the cause. You were right though I was issuing a .clear() on a null pointer in the set method.
-----Original Message----- From: Patrick Linskey [mailto:[EMAIL PROTECTED] Sent: April 30, 2007 3:52 PM To: open-jpa-dev@incubator.apache.org Subject: RE: How to debug object retrieveal in JPA? > That is the original method with a new name. As the documentation > states, the getters and setters used in property access may appear > with a "pc" prefix in stack traces under OpenJPA. What's the rationale behind this? It seems like this will inevitably make debugging of problems more of a challenge, since the user's own method names will no longer match up. -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: Abe White [mailto:[EMAIL PROTECTED] > Sent: Monday, April 30, 2007 12:29 PM > To: open-jpa-dev@incubator.apache.org > Subject: Re: How to debug object retrieveal in JPA? > > >> ca.BidSpec.emall.user.Person.pcsetPhoneNumbers(Person.java:727) > > > > I had read this and assumed that it was an > OpenJPA-generated method, > > but if so, there shouldn't be a line number. Did you > reverse-compile > > your classes at some point and change the synthetic interception > > methods? > > That is the original method with a new name. As the documentation > states, the getters and setters used in property access may appear > with a "pc" prefix in stack traces under OpenJPA. > > 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. > 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.
