Type: New Feature
Affects Version/s: 5.0
Fix Version/s: 5.0.7
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!
|Workflow||Default workflow, editable Closed status [ 12569162 ]||jira [ 12592112 ]|
|Workflow||jira [ 12404253 ]||Default workflow, editable Closed status [ 12569162 ]|
|Status||In Progress [ 3 ]||Closed [ 6 ]|
|Resolution||Fixed [ 1 ]|
|Fix Version/s||5.0.7 [ 12312802 ]|
|Status||Open [ 1 ]||In Progress [ 3 ]|
|Assignee||Howard M. Lewis Ship [ hlship ]|
|Field||Original Value||New Value|
|Fix Version/s||5.0 [ 12312018 ]|