around with the code every time a
new version comes out.
Cheers ;-)
Tony
From: Niall Pemberton [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: RE: Posting Collections
Date: Thu, 10 May 2001 20:23:31 +0100
This issue applies to all form field tags, not just checkboxes
wondering whether I
should just jack it in and use something else.
Cheers
Tony
From: Niall Pemberton [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: RE: Posting Collections
Date: Wed, 9 May 2001 20:51:00 +0100
The problem is the CheckBox tag currently sets the HTML
[mailto:[EMAIL PROTECTED]]
Sent: 10 May 2001 10:34
To: [EMAIL PROTECTED]
Subject: RE: Posting Collections
Many thanks Niall, that clears things up for me. Do you know if
there is a
reason why this is the behaviour for checkboxes? Is this just with
checkboxes or other tags as well?
I
The problem is the CheckBox tag currently sets the HTML name attribute to
the property, so your JSP will produced something like this:
input type=checkbox name=delete
So all the checkbox fields will have the same name.
In order for Struts to populate your Retailer bean with the delete
The problem is the CheckBox tag currently sets the HTML name attribute to
the property, so your JSP will produced something like this:
input type=checkbox name=delete
So all the checkbox fields will have the same name.
In order for Struts to populate your Retailer bean with the delete
I think I am doing the same thing that you want to do using the
html:multibox. When the form is submitted you get an array of the ids that
are checked and then you can go delete them.
in the jsp form (where restaurant id is a key for the item being deleted):
logic:iterate id=restaurant
6 matches
Mail list logo
