Mailing-List: contact user-help@cayenne.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cayenne.apache.org
Received-SPF: pass (nike.apache.org: domain of yk77770@gmail.com designates
 209.85.214.43 as permitted sender)
Received-SPF: pass (google.com: domain of yk77770@gmail.com designates
 10.204.149.209 as permitted sender) client-ip=10.204.149.209;
MIME-Version: 1.0
In-Reply-To: <0A1740BF-44E2-4506-B8B4-05CD4E68BD40@objectstyle.org>
References: 
 <CANFER0jyh4OQH3eLKLFihtoC3eNB8accvQ98TmDg01Q8LtcjmQ@mail.gmail.com>
	<0A1740BF-44E2-4506-B8B4-05CD4E68BD40@objectstyle.org>
Date: Mon, 20 Feb 2012 21:42:49 +0100
Message-ID: 
 <CANFER0jBmPhnzB0haQ9-0pNw5jUEg-Mi2ANkdpnFRFVahG1xwQ@mail.gmail.com>
Subject: Re: Cayenne external transaction
From: YK 7 <yk77770@gmail.com>
To: user@cayenne.apache.org
Content-Type: multipart/alternative; boundary=0015175cd03a736c7e04b96b56aa

--0015175cd03a736c7e04b96b56aa
Content-Type: text/plain; charset=ISO-8859-1

Thanks for this brilliant answer Andrus!

However, I still have a question.
Suppose that we have two databases and that we commit to the second one
only if the commit to the first db succeeds.
If I well understood, here I have to use external tx because it offers more
granularity.

Is it better to have an ObjectContext per DataNode (and not per DataDomain)
so that we can handle all cases?

Thanks

On Sun, Feb 19, 2012 at 1:51 PM, Andrus Adamchik <andrus@objectstyle.org>wrote:

> External transactions allow you to use container-managed DataSource and
> tie Cayenne in to container-managed JDBC transactions. So essentially if a
> container does a commit or rollback on a Connection, this will
> commit/rollback everything that was flushed via Cayenne or other JDBC
> clients since the start of the transaction.
>
> DataNode by itself is stateless. It is just a driver on top of JDBC driver
> if you may. So no problems there.
>
> ObjectContext state is not tied directly to the transaction. Its commit
> within an external tx is a flush to DB that will be committed or rolled
> back at some later point at tx end. You can do multiple ObjectContext
> commits within the same tx to update data incrementally, etc. ObjectContext
> rollback is even less related to tx. It just reverts objects in memory back
> to their previously known committed state. In many cases you probably do
> not want to reuse the context between external transactions.
>
> And finally, consider whether you really need those external transactions.
> 90% of Cayenne apps don't. A common reason to use external tx is when you
> want atomic behavior across multiple sources of DB modification (say
> Cayenne and raw JDBC) or mixing Cayenne with other non-JDBC transactional
> resources (JMS for instance). If you only modify the DB via Cayenne, then
> you don't need external tx. This is what makes Cayenne unique in the ORM
> space, and so much easier to use. It was compared to a version control
> system by other users - you check out a local copy of your objects, you
> modify them, and then commit. Only the last step involves a transaction and
> Cayenne can handle starting and ending it internally with no user
> involvement.
>
> Cheers,
> Andrus
>
>
>
> On Feb 18, 2012, at 5:48 PM, YK 7 wrote:
> > In Cayenne Modeler, when I disable Cayenne managed transactions, a
> message
> > saying that the external transaction was used instead during a commit.
> >
> > How am I supposed to tell my external container to handle transaction if
> > cayenne manages DB objects(Node, ObjectContext...) ?
> >
> > Do you have any working example that shows how to use cayenne with the
> same
> > circumstances?
> >
> > thx
>
>

--0015175cd03a736c7e04b96b56aa--