Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Received-SPF: pass (athena.apache.org: domain of kwsutter@gmail.com designates
 209.85.128.189 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:mime-version:content-type;
        b=CEHkq7AvZZZOYYisiV55TGpto/FJGzscx5v170t/CE83FbAhHDxhJfaOVI4D6mAoALHLaCvlAdQN9/HtragvOGWUlxYXlF0u/QHK+lUbvrcUDljaEVvlmFVeb0A7WRIbknTIpH+AjdoRNRgSOEJFsUEJEarinobJAS/LPNzc+j0=
Message-ID: <89c0c52c0709251220x7a5b475fv79d5e6fcb0e46756@mail.gmail.com>
Date: Tue, 25 Sep 2007 14:20:24 -0500
From: "Kevin Sutter" <kwsutter@gmail.com>
To: dev@openjpa.apache.org
Subject: Object Locking and Application Server (container-managed) environment
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_2429_21990646.1190748024319"

------=_Part_2429_21990646.1190748024319
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi,
I'm trying to figure out the ins and outs of Section 3 Object Locking as
they relate to running OpenJPA within an application server
(container-managed) environment such as WebSphere.  It seems that several of
these properties and/or API's are assuming an application-managed
environment outside of a container.  Either that, or there are implied
behaviors of the container environment that WebSphere is not providing.

For example, the ReadLockLevel property allows for none, read, or write
values.  What does it mean for "none" in an application server environment?
If the Container has already initiated a global (JTA) transaction, when
OpenJPA requests a Connection (via the <jta-data-source> element), this
Connection is automatically enlisted in the Transaction.  Thus, when the
"Select..." statement is issued, we will get a Read Lock on the row with the
default isolation level setting (supposed to be Read Committed).  So, how is
OpenJPA supposed to honor the "none" ReadLockLevel request?

Several places in this section of the document, there are references to
optimistic and non-optimistic (pessimistic) transactions.  Not lock
managers, but transactions.  The OpenJPA manual indicates that it can
support optimistic transactions by not issuing the database transaction
until flush or commit time.  But, I don't see how we are can configure for
the use of optimistic vs pessimistic transactions.  It looks like the
EntityTransaction interface is optimistic by default.  But, is there anyway
to control the optimisticity (new word) of a global transaction?  The answer
to these questions actually help with the first example outlined above.

Many other similar questions are in my mind, but let's start with these
since I think these will give a basis for the rest of the discussion.

Thanks,
Kevin

------=_Part_2429_21990646.1190748024319--