Return-Path: X-Original-To: apmail-cayenne-dev-archive@www.apache.org Delivered-To: apmail-cayenne-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 10449D1EF for ; Mon, 10 Dec 2012 14:41:50 +0000 (UTC) Received: (qmail 40789 invoked by uid 500); 10 Dec 2012 13:41:50 -0000 Delivered-To: apmail-cayenne-dev-archive@cayenne.apache.org Received: (qmail 40765 invoked by uid 500); 10 Dec 2012 13:41:50 -0000 Mailing-List: contact dev-help@cayenne.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cayenne.apache.org Delivered-To: mailing list dev@cayenne.apache.org Received: (qmail 40745 invoked by uid 99); 10 Dec 2012 13:41:50 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Dec 2012 13:41:50 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [208.78.103.231] (HELO vorsha.objectstyle.org) (208.78.103.231) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 10 Dec 2012 13:41:42 +0000 Received: (qmail 29175 invoked from network); 10 Dec 2012 13:45:56 -0000 Received: from unknown (HELO ?192.168.1.22?) (194.158.197.10) by vorsha.objectstyle.org with SMTP; 10 Dec 2012 13:45:56 -0000 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: Stateless RequestHandler From: Andrus Adamchik In-Reply-To: Date: Mon, 10 Dec 2012 16:41:25 +0300 Content-Transfer-Encoding: quoted-printable Message-Id: <4C3778FA-1A9F-4A49-B9DE-03B1E4366353@objectstyle.org> References: To: dev@cayenne.apache.org X-Mailer: Apple Mail (2.1499) X-Virus-Checked: Checked by ClamAV on apache.org On Dec 7, 2012, at 11:35 PM, Mike Kienenberger = wrote: > My recollection is that the Session version is in there as an example. Yep. Though many people use that in real apps (maybe those who are using = CDI or the good old web.xml for services integration), but since there's = so many ways service integration can be done in Java webapps, we don't = promote it as *the* way/ > As you've pointed out, it's easy to create Request version. One > flavor would create a new Context each request. Another way would be > to reuse requests between threads (Really, a "Thread" version). >=20 > I suspect that this is why we've not added them in the past -- very > simple, plus it's really two more versions rather than one. Yep. But I guess this will be a good demonstration that session-scoped = context is not the only way to do things. So I certainly do not object = the original proposal, as long as we keep making it clear that this is = one of the many possible integration scenarios. Andrus=