Bear Bibeault wrote:Are you using the name 'submit' for any element in the form? I assume that's what the property="submit" does? (I wouldn't know, I'm not a Struts fan.)
If so, you have essentially wiped out the submit function.
My only elements in this form that might wipe out the submit function are:
Ill change em up and give that a try.
posted 11 years ago
<html:submit property="foo"> just renders and html <input> element with type=submit. Having two of them could be problematic i guess.
The property attribute is the name of the request parameter that will be included with this submission, set to the specified value.
These definitions are from the struts framework page and its kind of confusing to me but the two <html:submit...>'s i have a functional at present doing their own functions and changing their property from submit breaks them.
Is there anyway to call these from outside the form?
If Struts forces you to name form elements "submit" then Struts is seriously broken as "submit" is a reserved name. Using it replaces the submit() function with the named element, rendering it impossible to call the function.
You should check into that enforced naming as I'm having a hard time believing that, much as I loathe Struts, it could be so short-sighted.
Just to clairify, my struts-config.xml file does allow for multiple submits in a form. Each one's value is what determines the next mapping. It's really more of how i can achieve that same functionality but just outside of the form.
It has nothing to do with having multiple submit elements, and everything to do with the fact that any (one, two, or seventeen) elements have a name attribute of "submit".
Have you looked at the HTML being generated by Struts? Does any element have a name="submit" attribute? If so, you need to figure out how to have that not happen, or resort to the completely disgusting and ridiculous work-around that I posted.