[
https://issues.apache.org/jira/browse/TAPESTRY-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship reassigned TAPESTRY-1476:
----------------------------------------------
Assignee: Howard M. Lewis Ship
> Component events for input translation and validation
> -----------------------------------------------------
>
> Key: TAPESTRY-1476
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1476
> Project: Tapestry
> Issue Type: New Feature
> Affects Versions: 5.0
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
>
> It seems to me we could leverage the existing component event hierarchy to
> allow for tightly customized input translation and parsing.
> I would propose three component events:
> "toclient" : corresponds to Translator.toClient(). Passed an object as the
> context (possibly null), result must be a String.
> "parseclient": corresponds to Translator.parseClient(). Passed a string as
> the context, returns an object or throws ValidationException.
> "validate": corresponds to Validator.validateInput(). Passed an object
> (provided by the translator). No return value. May throw
> ValidationException.
> We'll have to come up with a better mechanism for allowing event handler
> methods to throw an exception. Currently, I suspect, that you would get
> Javassist compile errors if you try!
--
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]
