Had a client who was confused: they had contributed a String->TheirEnum type coercion but it wasn't working in their activation contexts. Turns out the EnumValueEncoderFactory contribution to ValueEncoderSource was being used instead, ignoring their coercion.
I'm wondering if there's a way that ValueEncoderSource and/or EnumValueEncoderFactory could be smarter about seeing if there is a specific String->Enum coercion and making use of it instead of EnumValueEncoder (which uses Enum.valueOf() ).
|Field||Original Value||New Value|
|Status||Open [ 1 ]||Closed [ 6 ]|
|Assignee||Howard M. Lewis Ship [ hlship ]|
|Fix Version/s||5.3 [ 12316024 ]|
|Resolution||Fixed [ 1 ]|
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|670d 6h 31m||1||Howard M. Lewis Ship||23/Sep/11 21:12|