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 grobmeier@gmail.com designates
 209.85.214.171 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:from:date:message-id:subject:to:content-type;
        b=XrfAEmG7FakAAztWUNGRKl12DSt3EviBvsL3jHDHWTOhHwLL6bXA+DPUGL6l3mSaBk
         /FiV6vNnBIWbMD9r+0gRxhRwl5AyGawRYr4LrS9P56WHg2khMBhk8rrc2nX7IuRVtTqq
         e8IDYGSxaNyNdeBp3gvvIluuQO+acQ9M2Jrts=
MIME-Version: 1.0
From: Christian Grobmeier <grobmeier@gmail.com>
Date: Wed, 16 Feb 2011 10:50:16 +0100
Message-ID: <AANLkTimt+9ken1NwsvPvmaiki920dANhE7xsDgRo=tUi@mail.gmail.com>
Subject: ObjectContext per thread or per app?
To: user@cayenne.apache.org
Content-Type: text/plain; charset=UTF-8

Hello,

sorry, a dumb question:

do I need a ObjectContext per thread or per app?

In fact I wrote a spring bean (its a singleton) which creates one
single ObjectContext for all my app. In other terms, multiple threads
will use it to insert, read, commit etc.
Since ObjectContext offers the commit method, I am now doubting if
this was correct. I feel it might be good to have an ObjectContext for
each thread/user. Or does the ObjectContext know what happened as one
transaction?

Can you advise?

Thanks
Christian

-- 
http://www.grobmeier.de