[jira] [Commented] (TAP5-2496) Inconsistent behavior of EnumValueEncoder

["Jochen Kemnade (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TAP5-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725213#comment-14725213 ] 

Jochen Kemnade commented on TAP5-2496:
--------------------------------------

If I completely remove {{EnumValueEncoderFactory}} and the respective contribution in {{TapestryModule}}, the test suite runs fine.

> 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
>
> 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)