: Thursday, May 27, 2010 11:08:40 AM GMT -07:00 US/Canada Mountain
> Subject: Re: openjpa-1.2.1 partial commit problem
>
> Oh, I didn't do it on all of the objects though, just the main one,
> but I don't think it will make a difference. I'll try though.
>
> - &q
t; , [email protected]
> Sent: Thursday, May 27, 2010 10:54:27 AM GMT -07:00 US/Canada Mountain
> Subject: Re: openjpa-1.2.1 partial commit problem
>
> Yes, I did, but it revealed nothing more than I already knew, which is
> why I didn't mention it. One of my entries th
erEntries=[
[entryID = 130, entryType = CREDIT, description = debit bank account, amount =
342, dateTime = 2010-05-27T03:53:14]]}
- "C N Davies" wrote:
> From: "C N Davies"
> To: "Trenton D. Adams" , [email protected]
> Sent: Thursday, Ma
[email protected]
Subject: Re: openjpa-1.2.1 partial commit problem
Okay, now that I have build time enhancement working, I have still not
identified anything that should cause a problem.
All I do is remove a single entityManager.flush() call from my EJB, and voila,
the problem is gone. But, I put
#x27;t know what.
>
> - "C N Davies" wrote:
>
> > From: "C N Davies"
> > To: [email protected]
> > Sent: Thursday, May 27, 2010 12:25:14 AM GMT -07:00 US/Canada
> Mountain
> > Subject: RE: openjpa-1.2.1 partial commit problem
> &
m: "C N Davies"
> To: [email protected]
> Sent: Thursday, May 27, 2010 12:25:14 AM GMT -07:00 US/Canada Mountain
> Subject: RE: openjpa-1.2.1 partial commit problem
>
> Use prepersist / preupate listeners, you can check the content of your
> objects inside there.
>
>
ursday, 27 May 2010 2:41 PM
To: openjpa-users
Subject: openjpa-1.2.1 partial commit problem
Hi Guys,
I am not yet using the build time enhancer, as it currently blows up on one of
my objects, as noted in another message to the list. So, it's sticking to
runtime subclassing.
I'm havin
Hi Guys,
I am not yet using the build time enhancer, as it currently blows up on one of
my objects, as noted in another message to the list. So, it's sticking to
runtime subclassing.
I'm having the oddest problem. I am using EJB3, and have a method that
REQUIRES_NEW for the transaction. It
