Mailing-List: contact user-help@cayenne.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cayenne.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Peer Context Synchronization
From: Andrus Adamchik <andrus@objectstyle.org>
In-Reply-To: 
 <CALAw18yydt+PvEBJb+66RCS92wgMaSe_LWe4Xn8JW47Cha0o_w@mail.gmail.com>
Date: Wed, 24 Apr 2013 14:26:27 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <523B0521-6A9B-48E2-AD1D-EAAE2F14A825@objectstyle.org>
References: 
 <CALAw18yydt+PvEBJb+66RCS92wgMaSe_LWe4Xn8JW47Cha0o_w@mail.gmail.com>
To: user@cayenne.apache.org

Hi Lon,

Context update is immediate, but asynchronous, so this likely explains =
the observed behavior.=20

Andrus

On Apr 24, 2013, at 2:14 PM, Lon Varscsak <lon.varscsak@gmail.com> =
wrote:
> Hey all, I'm having some trouble with something that I _think_ should =
work.
> :)
>=20
> It's a very common pattern for me to create a new context, do work, =
save,
> and expect those changes to make it back into peer contexts that share
> object ids.
>=20
> However, there are times where this isn't happening=85and it's =
intermittent.
>=20
> My model in this situation is pretty simple, there's EntityA with a =
to-many
> to EntityB.  In a peer context, I'm creating an EntityB and adding it =
to
> the relationship of EntityA (a local instance), and generally =
speaking, in
> my other peer context the matching instance of EntityA is updated and =
has
> the proper EntityB in it's relationship (after commitChanges).
>=20
> However, occasionally=85maybe 1 in 10, the peer context doesn't get
> immediately updated (although will, I believe, at a later time).
>=20
> So the question is, does commitChanges immediately/synchronously push =
all
> changes into peer contexts?  Or does it happen in another way?
>=20
> Thanks for any insight.
>=20
> -Lon