[TAP5-2496] Inconsistent behavior of EnumValueEncoder

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.4
• Fix Version/s: 5.4
• Assignee: Jochen Kemnade
• Reporter: Jochen Kemnade
• Created: 01/Sep/15 10:01
• Updated: 22/Sep/16 13:11
• Resolved: 07/Sep/15 08:51

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.

Issue Links

• breaks: TAP5-2565 Enum <-> String coercion is not symmetric if enum class overrides toString()
• is broken by: TAP5-1331 EnumValueEncoder should identify legal values when a non-matching string is passed to it for conversion