> Actually I am doing the clear, once I got rid of it the exception
> disappeared.
> SO IMHO no bug
No, you're clearing a list. Craig is referring to the pcClearFields
call.
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its
, 2007 5:08 PM
To: open-jpa-dev@incubator.apache.org
Subject: Re: How to debug object retrieveal in JPA?
IMHO, this is a bug in the generated code for pcNewInstance.
I don't understand why the pcNewInstance should ever call pcClearFields. It just
got finished creating a new instance, and i
debug object retrieveal in JPA?
IMHO, this is a bug in the generated code for pcNewInstance.
I don't understand why the pcNewInstance should ever call pcClearFields. It just
got finished creating a new instance, and it knows that all fields have been set
to their Java default values.
[That
IMHO, this is a bug in the generated code for pcNewInstance.
I don't understand why the pcNewInstance should ever call
pcClearFields. It just got finished creating a new instance, and it
knows that all fields have been set to their Java default values.
[That's why we require the user to specify a
: 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
e 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
> Sub
AIL 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 th
>> 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
nal Message-
> From: Abe White [mailto:[EMAIL PROTECTED]
> Sent: Monday, April 30, 2007 12:22 PM
> To: open-jpa-dev@incubator.apache.org
> Subject: Re: How to debug object retrieveal in JPA?
>
>
> > Caused by: java.lang.NullPointerException
> > at java.util.ArrayL
> Caused by: java.lang.NullPointerException
> at java.util.ArrayList.addAll(ArrayList.java:472)
> at ca.BidSpec.emall.user.Person.pcsetPhoneNumbers(Person.java:727)
> at ca.BidSpec.emall.user.Person.pcClearFields(Person.java)
> at ca.BidSpec.emall.user.Person.pcNewInstance(
ubator.apache.org
> Subject: RE: How to debug object retrieveal in JPA?
>
> This is all I get:
>
> <0.9.7-incubating nonfatal general error>
> org.apache.openjpa.persistence.PersistenceException: null
> at
> org.apache.openj
-Original Message-
> From: Phill Moran [mailto:[EMAIL PROTECTED]
> Sent: Monday, April 30, 2007 11:13 AM
> To: open-jpa-dev@incubator.apache.org
> Subject: RE: How to debug object retrieveal in JPA?
>
> Sure here it is and the sql it generates. BTW the SQL works as I can
> exe
mailto:[EMAIL PROTECTED]
> Sent: Monday, April 30, 2007 11:13 AM
> To: open-jpa-dev@incubator.apache.org
> Subject: RE: How to debug object retrieveal in JPA?
>
> Sure here it is and the sql it generates. BTW the SQL works
> as I can execute it in MySQL query browser and get the r
om: Patrick Linskey [mailto:[EMAIL PROTECTED]
Sent: April 30, 2007 2:01 PM
To: open-jpa-dev@incubator.apache.org
Subject: RE: How to debug object retrieveal in JPA?
Odd indeed. Can you post your named query definition?
-Patrick
--
Patrick Linskey
BEA Systems, Inc.
__
return this
by email and then delete it.
> -Original Message-
> From: Phill Moran [mailto:[EMAIL PROTECTED]
> Sent: Monday, April 30, 2007 10:55 AM
> To: open-jpa-dev@incubator.apache.org
> Subject: RE: How to debug object retrieveal in JPA?
>
> Hard to pull this li
clears. IF not I
will have to package and send along
Phill
-Original Message-
From: Patrick Linskey [mailto:[EMAIL PROTECTED]
Sent: April 30, 2007 1:45 PM
To: open-jpa-dev@incubator.apache.org
Subject: RE: How to debug object retrieveal in JPA?
Odd. Any chance of packaging it up and
immediately return this
by email and then delete it.
> -Original Message-
> From: Phill Moran [mailto:[EMAIL PROTECTED]
> Sent: Monday, April 30, 2007 10:37 AM
> To: open-jpa-dev@incubator.apache.org
> Subject: RE: How to debug object retrieveal in JPA?
>
> I upgra
ll Moran [mailto:[EMAIL PROTECTED]
> Sent: Monday, April 30, 2007 7:28 AM
> To: open-jpa-dev@incubator.apache.org
> Subject: RE: How to debug object retrieveal in JPA?
>
> Anyone have any more suggestions on how to debug this?
>
> -Original Message-
> From: Phil
[EMAIL PROTECTED]
> Sent: Monday, April 30, 2007 7:28 AM
> To: open-jpa-dev@incubator.apache.org
> Subject: RE: How to debug object retrieveal in JPA?
>
> Anyone have any more suggestions on how to debug this?
>
> -Original Message-
> From: Phill Moran [mailto:[EMAIL
Anyone have any more suggestions on how to debug this?
-Original Message-
From: Phill Moran [mailto:[EMAIL PROTECTED]
Sent: April 26, 2007 11:20 PM
To: open-jpa-dev@incubator.apache.org
Subject: RE: How to debug object retrieveal in JPA?
I don't close it in anyway dir
I don't close it in anyway directly
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: April 26, 2007 11:16 PM
To: open-jpa-dev@incubator.apache.org
Subject: Re: How to debug object retrieveal in JPA?
Can it be that there is a glue code that closes EM in be
Message-
From: Patrick Linskey [mailto:[EMAIL PROTECTED]
Sent: April 26, 2007 9:59 PM
To: open-jpa-dev@incubator.apache.org
Subject: RE: How to debug object retrieveal in JPA?
Caused by: java.lang.NullPointerException
at java.util.Locale.toLowerCase(Locale.java:1060)
at
@incubator.apache.org
Subject: RE: How to debug object retrieveal in JPA?
> Caused by: java.lang.NullPointerException
> at java.util.Locale.toLowerCase(Locale.java:1060)
> at java.util.Locale.convertOldISOCodes(Locale.java:1083)
> at java.util.Locale.(Locale.java:272
in error, please immediately return this
by email and then delete it.
> -Original Message-
> From: Phill Moran [mailto:[EMAIL PROTECTED]
> Sent: Thursday, April 26, 2007 6:32 PM
> To: open-jpa-dev@incubator.apache.org
> Subject: RE: How to debug object retrieveal in JPA?
va:828)
... 64 more
-Original Message-
From: Patrick Linskey [mailto:[EMAIL PROTECTED]
Sent: April 26, 2007 5:40 PM
To: open-jpa-dev@incubator.apache.org
Subject: RE: How to debug object retrieveal in JPA?
> Can you post what you get if you do '((Exception)
> results.get(0)
il and then delete it.
> -Original Message-
> From: Phill Moran [mailto:[EMAIL PROTECTED]
> Sent: Thursday, April 26, 2007 2:36 PM
> To: open-jpa-dev@incubator.apache.org
> Subject: RE: How to debug object retrieveal in JPA?
>
> Can't cast List to Exception
>
> -
Can't cast List to Exception
-Original Message-
From: Patrick Linskey [mailto:[EMAIL PROTECTED]
Sent: April 26, 2007 5:00 PM
To: open-jpa-dev@incubator.apache.org
Subject: RE: How to debug object retrieveal in JPA?
So you're saying that the ResultList contains an Exceptio
ubator.apache.org
> Subject: RE: How to debug object retrieveal in JPA?
>
> Some more information on this exception
>
> Right after the execution the exception held inside the
> result is "com.sun.jdi.InvocationException occurred invoking
> method..." Can'
en-jpa-dev@incubator.apache.org
Subject: RE: How to debug object retrieveal in JPA?
> What is interesting is the line with a "1" (from
> System.out.println(results.size())). What this represents is the
> message that the "result list is closed" nothing else in the trace.
&g
list has
been closed"
-Original Message-
From: Phill Moran [mailto:[EMAIL PROTECTED]
Sent: April 26, 2007 4:18 PM
To: open-jpa-dev@incubator.apache.org
Subject: RE: How to debug object retrieveal in JPA?
I did not mean it threw an NPE but I was left with a null result list.
I have
after test execution
>
> What is interesting is the line with a "1" (from
> System.out.println(results.size())). What this represents is
> the message that the "result list is closed" nothing else in
> the trace.
>
> So what causes the result list to be c
hommeaux
Sent: April 26, 2007 3:54 PM
To: open-jpa-dev@incubator.apache.org
Subject: Re: How to debug object retrieveal in JPA?
Phill-
The maximum verbosity of logging is obtained by specifying the "openjpa.Log"
property to "DefaultLevel=TRACE".
What is the full exception s
Phill-
The maximum verbosity of logging is obtained by specifying the
"openjpa.Log" property to "DefaultLevel=TRACE".
What is the full exception stack trace? We might be able to help
identify the problem. In any case OpenJPA should never be throwing an
NPE, so we should at least probably
Could you post the full NPE? Is results null, or is the NPE coming from
within OpenJPA somewhere? OpenJPA shouldn't be returning a null
collection in any situation, I don't think.
One way to fish for causes of suspicious problems is to set the default
log level to TRACE:
This will generate tons
34 matches
Mail list logo
