Have you tried naming your components different then submit1 and submit2? How does Tapestry behave
if you use the OnEvent annotation on your methods?
Uli
Stéphane Decleire (JIRA) schrieb:
"Selected" event of Submit component is not correctly triggered when the form
submission is handled as an Ajax request
----------------------------------------------------------------------------------------------------------------------
Key: TAPESTRY-2505
URL: https://issues.apache.org/jira/browse/TAPESTRY-2505
Project: Tapestry
Issue Type: Bug
Components: XHR/dhtml/Ajax
Affects Versions: 5.0.14
Reporter: Stéphane Decleire
When a form submission is handled as an Ajax Request and this form includes several
submit components, all the "selected" events of those components are the same.
For example :
<t:form t:id="testForm" t:zone="testZone">
<t:textfield t:id="field1" t:value="field1"/>
<t:submit t:id="submit1" t:value="1"/>
<t:submit t:id="submit2" t:value="2"/>
</t:form>
void onSelectedFromSubmit1() {
log.info("submit1");
}
void onSelectedFromSubmit2() {
log.info("submit2");
}
Every form submited by both submit1 and submit2 components will trigger the
onSelectedFromSubmit1 function and the onSelectedFromSubmit2 will never be
triggered.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
