[
https://issues.apache.org/jira/browse/TAPESTRY-2515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship closed TAPESTRY-2515.
------------------------------------------
Resolution: Invalid
Assignee: Howard M. Lewis Ship
The correct approach would be to record, into the Form (via an @Environmental
FormSupport) a command that triggers the desired validation behavior after the
individual fields of the component have rendered. This is a powerful technique
that allows any kind of desired callback to occur when rendering, when
processing the submission, or both.
> onValidateComponent required for Component level perform cross-form(cross
> component) validation
> -------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-2515
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2515
> Project: Tapestry
> Issue Type: Improvement
> Affects Versions: 5.0.13
> Reporter: Fritz Pröbstle
> Assignee: Howard M. Lewis Ship
>
> onValidateComponent required for Component level perform cross-form(cross
> component) validation
> Assume I have a address-fragment component ADDCOMP for entering addresses.
> This component has no form and shoud be used inside a form.
> Means I have no onValidateForm event inside the component.
> *BUT* this component should do cross-component validation (i.e is ZIP code
> correct for city field) but there is no event
> to trigger it.
> I know that i could use (as a workaround) the onValidateForm of the using
> form component -
> but this delegates logic out of the component which should not be seen
> outside.
> Solution:
> A new event onValidateComponent should be triggered after all onValidateXX
> events of a component.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
