From: "OCsite" <webobjects-dev@wocommunity.org>
Received-SPF: none
 receiver=post.selbstdenker.com; client-ip=217.198.120.62; envelope-from=ocs@ocs.cz
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.100.0.2.22\))
Subject: Re: [WO-DEV] localinstance for not-yet-saved EOs? 
Date: Fri, 15 Oct 2021 15:30:22 +0200
References: <list-26609967@post.selbstdenker.com>
To: WebObjects & WOnder Development <webobjects-dev@wocommunity.org>
In-Reply-To: <list-26609967@post.selbstdenker.com>
Message-Id: <4C071BED-7D77-4DB2-BBC4-2776CB8185B5@ocs.cz>

Markus,

does this approach properly work for you with saved EOs? Weird; I was =
pretty sure localinstance would not copy down to the new EO the local =
changes, IIRC, the new EO in the new EC is simply a GID-based fault, to =
be, upon using, just re-constructed from the snapshot (which is the =
reason you can't do that with a new EO which does not have one), and =
that's that.

Thus, unless I'm much mistaken,

// presumed the saved eo.foo=3D=3D'old'
eo.foo=3D'new'
assert eo.localInstanceIn(anotherEC).foo=3D=3D'old'

All the best,
OC

> On 15. 10. 2021, at 14:48, Markus Ruggiero (rucotec) =
<webobjects-dev@wocommunity.org> wrote:
>=20
> LocalInstance is only allowed for EOs that have already been saved. If =
isNewObject() return true then any form of localinstance call returns an =
exception. Why? And how can I overcome this?
>=20
> I have the following scenario:=20
>=20
> The user picks existing EOs to be worked on at a later point in time. =
They can also create on-the-fly new EOs for picking. All EOs as well as =
the new ones are associated with the current editing context. The whole =
list of picked objects (NSArray containing existing and new EOs) is then =
passed to the next page and on to the next. In each step some of the EOs =
are modified in various ways until about 3 steps down the line a final =
saveChanges() is done. All fine so far.=20
>=20
> But on each step the user can go back up one step (either browser back =
button or with a dedicated navigation button on the page). The page =
cache takes care of this but the EOs themselves are not in the page =
cache and remain modified in their EC. Coming back the previous / first =
page does not show the initial state anymore. Ok, easy to solve =
(methinks): map the EOs into a new editing context right before going to =
the next step. Coming back then automatically throws away that EC. Going =
forward again will create a brand new EC. But! localInstancing into the =
new EC only works for saved EOs. How do I get these new EOs into the =
nextPhaseEC? The new EOs are fairly complex and already have =
relationships to other EOs. How can I re-wire the new EOs?
>=20
> Thanks for any help
> ---markus---
>=20