[
https://issues.apache.org/jira/browse/TAPESTRY-2177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570419#action_12570419
]
Howard M. Lewis Ship commented on TAPESTRY-2177:
------------------------------------------------
Ah, generally, when a component triggers and event, it is correct to use
TypeCoercer and not ValueEncoder. ValueEncoder is only intended for the case
where the values are starting as strings in the URL or form submission, not
when they start as arbitrary objects.
However, the point here is that the Form is triggering a new event with the
same values, and its still an array of Strings.
Let me see what I can do; I think the right option is to expose the
EventContext.
> Conversion of context parameters to server-side objects uses type coercer
> rather than value encoders.
> -----------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-2177
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2177
> Project: Tapestry
> Issue Type: Bug
> Affects Versions: 5.0.10, 5.0.11
> Reporter: Robert Zeigler
> Assignee: Howard M. Lewis Ship
>
> TAPESTRY-2112 resulted in ValueEncoders being used to convert context
> parameters into strings for client-side representation.
> However, for form contexts, the strings are converted back into values via
> type coercion, rather than via ValueEncoder.
--
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]
