Address: 5/F DeShi Building, No. 9 ShangDi Dong Lu (East Road) Haidian
>> District Beijing, 100094 P.R. China
>>
>> Hong Jin Lu---10/17/2008 09:51:06 AM---Dear Dinkar: I filed an issue record,
>> plz refer to
>>
>>
>> From:
>> Hong Jin Lu/China/IBM
>
>
>
> "Dinkar Rao" ---10/17/2008 04:16:28 AM---Thanks for the pointer Jeremy. I'm
> using the latest, greatest 1.3 build and am still hitting the peo
>
>
> From:
> "Dinkar Rao" <[EMAIL PROTECTED]>
> To:
> dev@openjpa.apache.org
> Date:
>
--|
|>
| Subject: |
|>
>------------------|
--|
|>
| Subject: |
|>
>----------------
Thanks for the pointer Jeremy. I'm using the latest, greatest 1.3
build and am still hitting the peoblem. I've not been able to repro my
test in a JSE environment. I'll try Xiaoqin's test to force
ObjectExistsException if possible for my scenario.
Hongjin, there is no JIRA issue yet for your parti
Dinkar,
Take a look at the recent commit for OPENJPA-722. It may be the
reason for the behavior difference you are seeing.
-Jeremy
Hi Hongjin,
We encountered a similar problem in another scenario, the only
difference being that in our case, after merge, OpenJPA incorrectly
concludes that a preexisting entity is new, at the time of commit, and
errors out early. So instead of the PersistenceException you got, we
get an ObjectEx