[
https://issues.apache.org/jira/browse/TAP5-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15512837#comment-15512837
]
ASF subversion and git services commented on TAP5-2496:
-------------------------------------------------------
Commit 7368fdc536d5ddc6c050b05bdbe45fea4d9517e1 in tapestry-5's branch
refs/heads/master from [~jkemnade]
[ https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;h=7368fdc ]
TAP5-2565, TAP5-2496: always use name() when coercing enum values to String
> Inconsistent behavior of EnumValueEncoder
> ------------------------------------------
>
> Key: TAP5-2496
> URL: https://issues.apache.org/jira/browse/TAP5-2496
> Project: Tapestry 5
> Issue Type: Bug
> Affects Versions: 5.4
> Reporter: Jochen Kemnade
> Assignee: Jochen Kemnade
> Fix For: 5.4
>
>
> EnumValueEncoder uses {{java.lang.Enum.name()}} in {{toClient(E)}} but uses
> {{typeCoercer.coerce(clientValue, enumType)}} in {{toValue(String
> clientValue)}}.
> I have a custom coercer in my project and this causes the value encoder to be
> unable to decode the client-side value back to a server-side value.
> I think we should remove {{EnumValueEncoderFactory}} altogether because
> {{TypeCoercedValueEncoderFactory}} should do its job just fine.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
