Return-Path: Delivered-To: apmail-jakarta-struts-user-archive@www.apache.org Received: (qmail 75694 invoked from network); 1 Mar 2004 23:37:34 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 1 Mar 2004 23:37:34 -0000 Received: (qmail 3184 invoked by uid 500); 1 Mar 2004 23:37:02 -0000 Delivered-To: apmail-jakarta-struts-user-archive@jakarta.apache.org Received: (qmail 3159 invoked by uid 500); 1 Mar 2004 23:37:02 -0000 Mailing-List: contact struts-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Struts Users Mailing List" Reply-To: "Struts Users Mailing List" Delivered-To: mailing list struts-user@jakarta.apache.org Received: (qmail 3145 invoked from network); 1 Mar 2004 23:37:01 -0000 Received: from unknown (HELO moutng.kundenserver.de) (212.227.126.186) by daedalus.apache.org with SMTP; 1 Mar 2004 23:37:01 -0000 Received: from [212.227.126.179] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1AxwyC-0004ME-00 for struts-user@jakarta.apache.org; Tue, 02 Mar 2004 00:37:08 +0100 Received: from [217.88.250.113] (helo=cyberspaceroad.com) by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1) id 1AxwyC-00010a-00 for struts-user@jakarta.apache.org; Tue, 02 Mar 2004 00:37:08 +0100 Message-ID: <4043C8BF.9070405@cyberspaceroad.com> Date: Tue, 02 Mar 2004 00:35:27 +0100 From: Adam Hardy User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031021 X-Accept-Language: de MIME-Version: 1.0 To: Struts Users Mailing List Subject: Re: Semi-OT: Saving state when using EJB Session Beans and Struts References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:7be52423742ce504c1b541fa1f258887 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N On 03/01/2004 05:47 PM Smith, Darrin wrote: > In short, the Actions will be calling various Stateful Session Beans to do > the actual work. These are used for various reasons with the main one being > their built-in transaction support (online orders...need to be either > done...or not done). How should state be handled and at what level > (page...request...session...) in the upstream struts portion? Hmmm. Thought someone more knowledgeable would answer this, and was waiting with interest myself. Oh well. Without too much experience with EJBs myself, I can say a couple of things: the gurus say 'use the business delegate pattern with an EJB session facade'. Secondly, it depends heavily on what your stateful session beans are holding as state. Care to name something? Adam -- struts 1.1 + tomcat 5.0.16 + java 1.4.2 Linux 2.4.20 Debian --------------------------------------------------------------------- To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: struts-user-help@jakarta.apache.org