[
https://issues.apache.org/jira/browse/TAPESTRY-1929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship closed TAPESTRY-1929.
------------------------------------------
Resolution: Won't Fix
On further reflection, I think these two interfaces really are different,
despite the similarity of the methods defined. ValueEncoder is about
behind-the-scenes values (such as primary keys of entity objects) whereas
Translator is about user presentable values. The semantics are different,
especially in respect to what happens when a client value can't be converted to
a server-side object.
> Replace ValueEncoder usage with Translator
> ------------------------------------------
>
> Key: TAPESTRY-1929
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1929
> Project: Tapestry
> Issue Type: Improvement
> Components: Framework
> Affects Versions: 5.0.6
> Reporter: Kevin Menard
> Assignee: Howard M. Lewis Ship
> Priority: Minor
>
> The Translator and ValueEncode interfaces are very similar in definition and
> usage. Having to know which to use when can be a bit of a pain for an end
> user.
> Per a discussion on the user list, Howard recommended removing ValueEncoder
> and using Translator in its stead.
--
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]
