We have also implemented a multiple submit button system; but in our
case we wrote a custom tag that generates javascript that sets a property
to a specified value and submits the form when you hit the button.
The tags look something like:
my_submit property=formAction value=delete
Most of us would not rely *solely* on Javascript for validation, since
it can be turned off, and therefor endanger your application. But
requiring it to handle multiple buttons is a different matter, so long
as the default formAction did nothing harmful if Javascript were turned
off.
The
Hi Joe,
I would certainly be interested in your code for this tag, as I have decided
to make javascript a prerequisite for my project.
Regards
Andy
- Original Message -
From: Joe Faith [EMAIL PROTECTED]
To: Struts Developers List [EMAIL PROTECTED]
Sent: Thursday, November 15, 2001
Yet another approach would be to use an image tag:
html:image page=/images/lock.gif property=lock /
html:image page=/images/unlock.gif property=unlock /
html:image page=/images/delete.gif property=delete /
and check parameter in action:
if (request.getParameter(lock.x) != null) {
Of course, I fully expect to see responses saying both. ;-) I guess my
question is, what is the real problem people need to solve?
+ Team development
+ General manageablitity
+ Distribution of plug-and-play Struts application-lets
What this amounts to, I think, is that we need the ability to
Not acked..
-- Forwarded Message
From: emmanuel.boudrant [EMAIL PROTECTED]
Date: Thu, 15 Nov 2001 17:23:13 +0100 (CET)
To: [EMAIL PROTECTED]
Subject: deadlink
Here somes dead link on jakarta web site:
On page http://jakarta.apache.org/struts/userGuide/resources.html
- Struts .. in Rose
A few more questions then...
Access control to servlets is well understood. Can access to particular
actions be controlled in similar fashion?
Isn't it possible that extensions to the programming model from Sun that
extends to servlets would be of no use to a struts application?
I just have this
Many bug fixes and documentation updates have been made since the Struts 1.0
release. Therefore, I propose that we release the tip of the
STRUTS_1_0_BRANCH branch as Struts 1.0.1, to make these changes available as
part of an official distribution of Struts. I have checked in a proposed
release
