Mailing-List: contact users-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@openjpa.apache.org
Received-SPF: pass (nike.apache.org: domain of kwsutter@gmail.com designates
 209.85.212.46 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=UK4c7NfVOyBrt8+RgtpnzNVdsF1D9cnfRREMWSjkzkifj5tdKNlg9sR/C4eSHpOACo
         cKrhWJQR6Z4g3T7x0WJQEOEoNPwBm0s5BdYTo9W1zdV5rwXg/XO1J/2+NHBqJVrYfvtv
         5rnHsafcSKiWtkFfgS9B7KD3rpaGdz1JUIaPc=
MIME-Version: 1.0
In-Reply-To: <1271185721959-4897872.post@n2.nabble.com>
References: <1271094970810-4891679.post@n2.nabble.com>
	 <w2p89c0c52c1004121218n2e4f66b9nd812ae413e8de328@mail.gmail.com>
	 <1271185721959-4897872.post@n2.nabble.com>
Date: Wed, 14 Apr 2010 08:48:46 -0500
Message-ID: <y2j89c0c52c1004140648l632bf5f8y3bcb7985f42f169e@mail.gmail.com>
Subject: Re: Problem of partial commit in OpenJPA
From: Kevin Sutter <kwsutter@gmail.com>
To: users@openjpa.apache.org
Content-Type: multipart/alternative; boundary=00c09f8de4f0224246048432a3ff

--00c09f8de4f0224246048432a3ff
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Apr 13, 2010 at 2:08 PM, Ravi P Palacherla <
ravi.palacherla@oracle.com> wrote:

>
> Kevin,
>
> In sudhir's code snippet, aDepartment is persisted and
> aDepartment.getName()
> is used in the find.
> I guess  aDepartment will be managed after the persist statement and the
> find will always return a non-null object. So, I think that newDept should
> never be null.
>
> Is my understanding incorrect ?
>

Ravi,
Right.  I couldn't quite figure out under what conditions a non-null
department would be returned.  But, since the Department entity wasn't
provided, maybe the key generation had some anomaly that caused a problem
with the find operation.  Not sure.  I decided to just focus on the partial
commit problem rather than the app itself...  :-)

Related to that though is the final persist() call in the sample app.  If
newDept was found, then it is already managed by the persistence context.
And, since it was already an existing entity, it doesn't make any sense to
be performing a persist() operation.  This should actually result in an
EntityExistsException.  Even a merge() in this case would not be necessary
since the entity is already merged.

So, maybe there are more issues with the app that need to resolved...

Kevin


>
> Regards,
> Ravi.
> --
> View this message in context:
> http://n2.nabble.com/Problem-of-partial-commit-in-OpenJPA-tp4891679p4897872.html
> Sent from the OpenJPA Users mailing list archive at Nabble.com.
>

--00c09f8de4f0224246048432a3ff--