Return-Path: Delivered-To: apmail-jakarta-struts-dev-archive@apache.org Received: (qmail 59826 invoked from network); 3 Jul 2002 22:46:37 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 3 Jul 2002 22:46:37 -0000 Received: (qmail 24062 invoked by uid 97); 3 Jul 2002 22:46:46 -0000 Delivered-To: qmlist-jakarta-archive-struts-dev@jakarta.apache.org Received: (qmail 24039 invoked by uid 97); 3 Jul 2002 22:46:46 -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 24011 invoked by uid 98); 3 Jul 2002 22:46:45 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Mime-Version: 1.0 X-Sender: jgermusk@mail.jgsullivan.com Message-Id: In-Reply-To: <20020703221022.19428.qmail@nagoya.betaversion.org> References: <20020703221022.19428.qmail@nagoya.betaversion.org> Date: Wed, 3 Jul 2002 17:38:12 -0500 To: "Struts Developers List" From: Joe Germuska Subject: Re: DO NOT REPLY [Bug 7202] - Add forward attribute to FormTag to allow submision to a global forward Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N >------- Additional Comments From husted@apache.org 2002-07-03 22:10 ------- >Maybe, I should take a look at the patch =:0). What I had in mind wouldn't >bypass the controller. It would look up the path specified by the >ActionForward >and use that for the action="" path. This wouldn't be any different >that using a >RTE to do the equivalent of "action='<%= forward.getPath() %>'. So the idea is >that instead just being able to say "action=${actionMapping.path()}" we'd be >able to say "forward=${actionForward.name()}". In the latter case, >the tag would >use ${actionForward.path} as the target of the form. It's like the difference >between page= and forward= in the html:link tag, except here its action= and >forward=. I think Craig's point is that it's possible to specify a forward which bypasses the controller. It's also possible, as you note, to specify a forward which uses the controller. Perhaps the question is wether the system should be more protective vs. more permissive. I thought Ted's use cases were pretty spot-on, and I very much like the flexibility of having a forward attribute to the form tag. But it would also be easy to mark this bug as "LATER" if the focus for now should stay on pushing out 1.1b2. Joe -- -- * Joe Germuska { joe@germuska.com } "It's pitiful, sometimes, if they've got it bad. Their eyes get glazed, they go white, their hands tremble.... As I watch them I often feel that a dope peddler is a gentleman compared with the man who sells records." --Sam Goody, 1956 tune in posse radio: -- To unsubscribe, e-mail: For additional commands, e-mail: