[
https://issues.apache.org/jira/browse/TAP5-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Kemnade updated TAP5-2496:
---------------------------------
Description:
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.
was:
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 {{EnumValueEncoder}} altogether because
{{TypeCoercedValueEncoderFactory}} should do its job just 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)
