Return-Path: Delivered-To: apmail-struts-user-archive@www.apache.org Received: (qmail 43129 invoked from network); 28 Sep 2010 08:03:24 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 28 Sep 2010 08:03:24 -0000 Received: (qmail 56418 invoked by uid 500); 28 Sep 2010 08:03:21 -0000 Delivered-To: apmail-struts-user-archive@struts.apache.org Received: (qmail 56153 invoked by uid 500); 28 Sep 2010 08:03:18 -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 56140 invoked by uid 99); 28 Sep 2010 08:03:17 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Sep 2010 08:03:17 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of darrenkarstens@gmail.com designates 209.85.216.169 as permitted sender) Received: from [209.85.216.169] (HELO mail-qy0-f169.google.com) (209.85.216.169) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Sep 2010 08:03:09 +0000 Received: by qyk7 with SMTP id 7so7727556qyk.14 for ; Tue, 28 Sep 2010 01:02:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=kc4RuqGgTmIkI3S7fHt6K3VSbAq8depb0e4aAGJUTjc=; b=WhHZnhd1sCM8wyx5HmaT8u+tSAaBRN0uolwPaDVEY9eGYiDYnxHNyJyhyFYVWdJdHF Ww88FqkKMienr2QL2gZ3ByRv5hg0nOQmgI5qZxNOOOiFNHO4LJmCRCrDs3ns5U5xBNjX mPIOIeR6zhpXqM7yLlZTttZpux1RKFH8aUfjs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=I4ipZ3AmGZ2uyu+zQ1nk0/uwW/+MaB0UB3L0iOy7wY3/eYnQJsOrE3nfQgxKXgI/AH tTCLataMuaoqgq0UHEShlXs257RpCPJ2NlnRIlh67Avem3wX25M+wcLdtQXyqJPT8Dc5 ljDYUihUbRTHxHQGpWPlrRMTdVJqCfDIyDqIQ= MIME-Version: 1.0 Received: by 10.224.122.203 with SMTP id m11mr6432604qar.191.1285660968315; Tue, 28 Sep 2010 01:02:48 -0700 (PDT) Received: by 10.229.42.75 with HTTP; Tue, 28 Sep 2010 01:02:46 -0700 (PDT) In-Reply-To: References: Date: Tue, 28 Sep 2010 09:02:46 +0100 Message-ID: Subject: Re: How to structure a struts2 application From: Darren Karstens To: Struts Users Mailing List Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Thanks for the responses. The validation interceptor seems to be exactly what I was looking for. Regards Darren > You don't need multiple classes. The validate interceptor, as the prepare > one, is very flexible in this sense. You can define multiple validate > methods inside a single action class. Particularly, you could define a > validate (prepare) method =A0for every entry point (for instance: update, > delete, etc.). =A0You must only follow the convention: use updateValidate= for > validate method update, deleteValidate from delete entry point, and so on= . > Remember that validate/prepare method is always invoked (so you can put h= ere > common validation rule). > Furthermore, you can encapsulate validation logic inside an xml file, alw= ay > following the conventions: > --validation.xml > > > Maurizio Cucchiara --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@struts.apache.org For additional commands, e-mail: user-help@struts.apache.org