Hm. So, now we have /three/ systems of translating values?
1) TypeCoercer
2) Translator
3) ValueEncoder
This has been a source of irritation for me. In fact, I contributed
coercers for my app to translate to and from database entities and
strings. Works great! Except... I also had to specify/contribute
value encoders... and translators...
I understand the difference in semantics that you're referring to, but
I'm with Kevin that it's really confusing and really annoying to have
what amounts to three type conversion systems.
Robert
On Jan 17, 2008, at 1/1712:46 PM , Howard M. Lewis Ship (JIRA) wrote:
[ 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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
