Return-Path: Delivered-To: apmail-struts-dev-archive@www.apache.org Received: (qmail 63444 invoked from network); 4 Jan 2005 18:08:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 4 Jan 2005 18:08:16 -0000 Received: (qmail 54439 invoked by uid 500); 4 Jan 2005 18:07:43 -0000 Delivered-To: apmail-struts-dev-archive@struts.apache.org Received: (qmail 54304 invoked by uid 500); 4 Jan 2005 18:07:39 -0000 Mailing-List: contact dev-help@struts.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Struts Developers List" Reply-To: "Struts Developers List" Delivered-To: mailing list dev@struts.apache.org Received: (qmail 54273 invoked by uid 99); 4 Jan 2005 18:07:38 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=RCVD_BY_IP,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of craigmcc@gmail.com designates 64.233.170.196 as permitted sender) Received: from rproxy.gmail.com (HELO rproxy.gmail.com) (64.233.170.196) by apache.org (qpsmtpd/0.28) with ESMTP; Tue, 04 Jan 2005 10:07:33 -0800 Received: by rproxy.gmail.com with SMTP id j1so15045rnf for ; Tue, 04 Jan 2005 10:07:30 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=ET1frB5MMtpMRGS50Ef/BRRNnLLLTfo68NQ1rTXGIvs/FXA1rkhZHoxcuVmSdHacM0IeIhqndJk+yBrrWExY9eT7XTXhh9rv9MlxtbxIutCWBtLmQpaPlMdK3ek8FpFWk6y2LmO0beyjAk2sgAvtLkpZiZfzio//AlruGJr6rwM= Received: by 10.39.2.11 with SMTP id e11mr176158rni; Tue, 04 Jan 2005 10:07:30 -0800 (PST) Received: by 10.39.3.22 with HTTP; Tue, 4 Jan 2005 10:07:30 -0800 (PST) Message-ID: Date: Tue, 4 Jan 2005 10:07:30 -0800 From: Craig McClanahan Reply-To: craigmcc@apache.org To: Struts Developers List Subject: Re: "Use Cases" Example Webapp for the Shale proposal In-Reply-To: <41DAC8E0.1000608@dbgroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <41DAC8E0.1000608@dbgroups.com> X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N On Tue, 04 Jan 2005 09:48:32 -0700, BaTien Duong wrote: > Hello Craig: > > Good work. Thanks for your effort. We always wish to have more than 24 > hours a day. I wish to have some spare time to get back to this. > > One quick question about the framework: What is the appropriate tool to > use for configuration in different tiers? I thought Jsf is appropriate > in the presentation tier. The business tier and integration tier can > live in different servers separate from the server of the presentation > tier. (I currently use Spring IoC for the configuration of these tiers). > From a glance at your javadoc, you make Jsf as *the* configuration tool > for DAO layer. Should it be appropriate to use chain of request/response > framework to connect the tiers? As with the original design of Struts, I tried not to impose these decisions on the application developer -- you can choose your favorite techniques. However, it's instructive to note that, for its own purposes, this particular example app uses the IoC-ish configuration support that JSF already provides (via managed beans) to wire together the business logic and DAO instances. If the logic were any more complicated than the current example (and other use cases certainly will be), using a chain to assemble your tier-crossing (or even the processing within a tier) seems to make a lot of sense. > > Thanks > > BaTien > DBGROUPS > Craig --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org For additional commands, e-mail: dev-help@struts.apache.org