Mailing-List: contact dev-help@cayenne.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@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.5 \(1508\))
Subject: Re: REST framework on to of Cayenne [Was [jira] [Commented]
 (CAY-1847) Make ConverterFactory extensible and injected via DI]
From: Andrus Adamchik <andrus@objectstyle.org>
In-Reply-To: 
 <CAOUwSGu0gUGRv9yTB0u4HM6nPTJca-HfAd7xD2gPSGf47yCd3A@mail.gmail.com>
Date: Fri, 12 Jul 2013 09:13:29 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <93C3900E-227C-4848-A014-78C499079BAB@objectstyle.org>
References: <JIRA.12657287.1373561129872@arcas>
 <JIRA.12657287.1373561129872.34759.1373570508764@arcas>
 <7CF47ED9-5675-40CB-8F78-D50793809AC8@objectstyle.org>
 <CAOUwSGu0gUGRv9yTB0u4HM6nPTJca-HfAd7xD2gPSGf47yCd3A@mail.gmail.com>
To: dev@cayenne.apache.org


On Jul 11, 2013, at 11:16 PM, John Huss <johnthuss@gmail.com> wrote:

> The trickiest thing we found to deal with was avoiding infinite loops =
in
> serialization due to reverse relationships.  If your model allows you =
to
> choose one side of the relationship in every case then you can avoid =
it,
> but if you need it to be dynamic it becomes more painful.

In my implementation I don't serialize based on the DataMap alone. There =
has to be a path tree describing the result associated with a given =
request (either inferred from request parameters, or created server-side =
for a given REST method). It solves this problem completely by providing =
constraints on the subgraph returned to the caller.=20

FWIW this is not unlike serialization Cayenne is doing for ROP, that is =
also explicitly bound by a similar tree inferred from the query =
prefetches.

Andrus=