Return-Path: Delivered-To: apmail-jakarta-struts-dev-archive@apache.org Received: (qmail 77049 invoked from network); 29 May 2003 02:22:11 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 29 May 2003 02:22:11 -0000 Received: (qmail 623 invoked by uid 97); 29 May 2003 02:24:31 -0000 Delivered-To: qmlist-jakarta-archive-struts-dev@nagoya.betaversion.org Received: (qmail 616 invoked from network); 29 May 2003 02:24:30 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 29 May 2003 02:24:30 -0000 Received: (qmail 76467 invoked by uid 500); 29 May 2003 02:22:04 -0000 Mailing-List: contact struts-dev-help@jakarta.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 struts-dev@jakarta.apache.org Received: (qmail 76456 invoked from network); 29 May 2003 02:22:03 -0000 Received: from f80.law15.hotmail.com (HELO hotmail.com) (64.4.23.80) by daedalus.apache.org with SMTP; 29 May 2003 02:22:03 -0000 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 28 May 2003 19:22:13 -0700 Received: from 12.252.55.153 by lw15fd.law15.hotmail.msn.com with HTTP; Thu, 29 May 2003 02:22:12 GMT X-Originating-IP: [12.252.55.153] X-Originating-Email: [dgraham1980@hotmail.com] From: "David Graham" To: struts-dev@jakarta.apache.org Bcc: Subject: Re: composable RequestProcessor Date: Wed, 28 May 2003 20:22:12 -0600 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 29 May 2003 02:22:13.0188 (UTC) FILETIME=[1D7B6840:01C32589] X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N >If you're really composing, would it make more sense to have the >composition happen in a config file? Unless I misunderstand you, there's >still a fair bit of work required to implement a RequestProcessor interface >by writing an implementation class that calls on delegates. There's no >reason you couldn't do both, though. > Either way, you're still "really" composing. IDEs greatly limit the work involved in writing a class that delegates behavior to another class. >I was thinking something like this: > > > > > type="org.apache.struts.tiles.TilesForwardConfigProcessor" /> > > Most apps will use the RequestProcessor that comes with Struts. Others will simply subclass and modify a few methods. The composition use case should be supported but I think it's an edge case that the interface idea supports nicely without messing with the config file. David > >Of course, this is a substantial change to the DTD, but it might still fit >into Struts 1.2.... > >Joe > >-- >-- >Joe Germuska Joe@Germuska.com http://blog.germuska.com "If >nature worked that way, the universe would crash all the time." --Jaron >Lanier > >--------------------------------------------------------------------- >To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org >For additional commands, e-mail: struts-dev-help@jakarta.apache.org > _________________________________________________________________ Protect your PC - get McAfee.com VirusScan Online http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 --------------------------------------------------------------------- To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: struts-dev-help@jakarta.apache.org