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 mkienenb@gmail.com designates
 74.125.82.47 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        b=GjgX2VAmCFJ3uGuQdv5bmFZuHwLkKg+WS8SFVaRAm8YpKLcSJI9GUO7qZqc4IEUgYE
         h1D8EAJWfa5ddE8qscZyxKZtp79iVSbo3ywWIEO76RGS/GXEsLOPjHtOjppMVCsM1jzU
         zUvlC2q+zVac+KCa+edFWAqN+lN7pW9VcdMVk=
MIME-Version: 1.0
In-Reply-To: <1303916064507-2870619.post@n3.nabble.com>
References: <1303907767164-2870230.post@n3.nabble.com>
 <BANLkTikoFnzqKA7uZJZ39dS2GvdD8Fmk3Q@mail.gmail.com>
 <1303916064507-2870619.post@n3.nabble.com>
From: Mike Kienenberger <mkienenb@gmail.com>
Date: Wed, 27 Apr 2011 11:16:24 -0400
Message-ID: <BANLkTink3PKzbwQSnvS3zGgfpWpKhiUJew@mail.gmail.com>
Subject: Re: commit all objects, temporary objects, POJO's, DTO
To: user@cayenne.apache.org
Content-Type: text/plain; charset=ISO-8859-1

You're going to have to give us more information before we can
speculate on what's the best choice.   It may be that a combination of
several approaches make sense for your current project.

I've used a number of approaches in the past.   For example.....

On one struts project, I created a per-session data context but only
made changes to it per request.  At the end of every request, the data
context contained committed "read-only" objects.   The changes were
either committed or rolled back by the end of the request.   Similar
to your DTO approach , except that the persisted-between-request
values were persisted as separate items.

For a JSF project, I used a per-request data context, but serialized
all modified-but-uncommitted data objects and unserialized them to the
next per-request data context.   No DTO here -- the Cayenne Objects
were used at every layer.

What you do depends on how long you need to keep modified or cached
objects around (only one request (requeest scope), between requests
("page" scope), the lifetime of the session (session scope), the
lifetime of the application (application scope).

There's nothing stopping you from using a combination of choices.  For
some things, create a data context on demand.   For other things, use
a session-scoped data context.


On Wed, Apr 27, 2011 at 10:54 AM, felix
<felix.serrano@technicalnorms.com> wrote:
> Thanks for your quick response.
>
> It seems like we have two options:
> - Create a context per writeable action (otherwise we could not retrieve an
> object, updated and save exactly when we want, in other words, when the obj
> is in a consistent state)
> - Create a DTO layer and have for instance one context per session. The most
> flexible option so far.
>
> I have heard there is something related to POJOs in Cayenne, Could I have
> more information regarding this point (I've tried but no much info on this)?
>
> Thanks a lot
>
>
> --
> View this message in context: http://cayenne.195.n3.nabble.com/commit-all-objects-temporary-objects-POJO-s-DTO-tp2870230p2870619.html
> Sent from the Cayenne - User mailing list archive at Nabble.com.
>