RE: Named query created in error

2007-04-19 Thread Phill Moran
Will do and thanks again -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jacek Laskowski Sent: April 19, 2007 10:57 AM To: open-jpa-dev@incubator.apache.org Subject: Re: Named query created in error On 4/19/07, Phill Moran <[EMAIL PROTECTED]>

Re: Named query created in error

2007-04-19 Thread Jacek Laskowski
On 4/19/07, Phill Moran <[EMAIL PROTECTED]> wrote: Thanks Jacek, Store is annotated with @Entity: That might imply an incorrect behaviour of OpenJPA. I doubt if I can help more than just a spec guidance ;-) I'll have to set up the environment to reproduce the issue as OpenJPA doesn't seem to f

RE: Named query created in error

2007-04-19 Thread Phill Moran
the full purpose of this file Thanks for all this support Phill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jacek Laskowski Sent: April 19, 2007 10:15 AM To: open-jpa-dev@incubator.apache.org Subject: Re: Named query created in error On 4/19/07, Phill

Re: Named query created in error

2007-04-19 Thread Jacek Laskowski
On 4/19/07, Phill Moran <[EMAIL PROTECTED]> wrote: I am using MySQL version 5 The stack trace only shows because have wrapped this in a try/catch. The exception becomes NPE due to OpenJPA trying to make a Person object form more than just Person Object data, it fails to do this (silently) and t

RE: Named query created in error

2007-04-19 Thread Phill Moran
at org.apache.openjpa.kernel.BrokerImpl.find(BrokerImpl.java:828) ... 69 more This is all I get -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jacek Laskowski Sent: April 19, 2007 2:18 AM To: open-jpa-dev@incubator.apache.org Subject: Re: Named query created in error O

Re: Named query created in error

2007-04-18 Thread Jacek Laskowski
On 4/19/07, Phill Moran <[EMAIL PROTECTED]> wrote: Here it is: [2007-04-18 18:37:07,937] INFO ca.BidSpec.testing.emall.UserFactoryTest Began transaction (1): transaction manager [EMAIL PROTECTED]; default rollback = true 25547 WARN [main] openjpa.MetaData - Found duplicate query "PersonFXLas

RE: Named query created in error

2007-04-18 Thread Phill Moran
Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jacek Laskowski Sent: April 18, 2007 5:34 PM To: open-jpa-dev@incubator.apache.org Subject: Re: Named query created in error On 4/18/07, Phill Moran <[EMAIL PROTECTED]> wrote: > The exception I get is nu

Re: Named query created in error

2007-04-18 Thread Jacek Laskowski
On 4/18/07, Phill Moran <[EMAIL PROTECTED]> wrote: The exception I get is null pointer from this line: List results = (List) q.getResultList(); Could you show the query creation and the stack trace you're getting? Jacek -- Jacek Laskowski http://www.JacekLaskowski.pl

RE: Named query created in error

2007-04-18 Thread Phill Moran
e- From: Patrick Linskey [mailto:[EMAIL PROTECTED] Sent: April 18, 2007 3:56 PM To: open-jpa-dev@incubator.apache.org Subject: RE: Named query created in error What error do you get? I expect that it's joining extra data because your one-to-ones and many-to-ones are marked up to use eager

RE: Named query created in error

2007-04-18 Thread Patrick Linskey
What error do you get? I expect that it's joining extra data because your one-to-ones and many-to-ones are marked up to use eager fetching. Note that eager fetching is the default for one-to-one and many-to-one relations, so if you have not marked up these relations as lazy, then they're implicitl