Return-Path: Delivered-To: apmail-struts-user-archive@www.apache.org Received: (qmail 89445 invoked from network); 2 Mar 2006 23:33:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 2 Mar 2006 23:33:10 -0000 Received: (qmail 16856 invoked by uid 500); 2 Mar 2006 23:33:46 -0000 Delivered-To: apmail-struts-user-archive@struts.apache.org Received: (qmail 16843 invoked by uid 500); 2 Mar 2006 23:33:46 -0000 Mailing-List: contact user-help@struts.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Struts Users Mailing List" Reply-To: "Struts Users Mailing List" Delivered-To: mailing list user@struts.apache.org Received: (qmail 16832 invoked by uid 99); 2 Mar 2006 23:33:46 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Mar 2006 15:33:46 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of brian.papa@gmail.com designates 64.233.182.192 as permitted sender) Received: from [64.233.182.192] (HELO nproxy.gmail.com) (64.233.182.192) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Mar 2006 15:33:45 -0800 Received: by nproxy.gmail.com with SMTP id b2so374199nfe for ; Thu, 02 Mar 2006 15:33:24 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=EUuCnxQHMX9Xg5wmFXlcm3Qa24HZLRF1V8T8sbXCnWZC0rccCV9Q92QP/dpOG1Ek5AD914ZIcBixzvlWE5CBhx6ar/2RjqM2BLgS/5eMZKC7/Lkkili6OQn9FpOE6oQ1UcOSE5fOTo8CrJykjlGoqFGbdt3WS3MWDwlu0eib+e8= Received: by 10.49.18.14 with SMTP id v14mr890411nfi; Thu, 02 Mar 2006 15:33:24 -0800 (PST) Received: by 10.48.213.1 with HTTP; Thu, 2 Mar 2006 15:33:24 -0800 (PST) Message-ID: <366551fb0603021533p4c7b2a8o3292ff3d1c1ebea4@mail.gmail.com> Date: Thu, 2 Mar 2006 18:33:24 -0500 From: "brian papa" To: user@struts.apache.org Subject: best practice suggestion when using tiles MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N I'm using tiles in an application and so far have liked the modularity and reusablity. I have a thin web layer with the business logic all called from classes that extend the Tiles Controller, so that each class is attached to a single tile. I ran into a problem recently though where I wanted to change a response header after conducting some business logic - problem though was that this was in a controller, and the response had already been submitted. So now I'm second-guessing all of the business logic being called from Controller classes. I use Struts Actions in my application as well, but only thus far for things like form submission. Is this a poor practice? Or should I move all of the business logic calls out from my Controller classes and into Struts Actions? Thanks for your input. --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@struts.apache.org For additional commands, e-mail: user-help@struts.apache.org