EnumValueEncoder will create a ValueEncoder even when there's a specific
String->Enum type coercion
---------------------------------------------------------------------------------------------------
Key: TAP5-933
URL: https://issues.apache.org/jira/browse/TAP5-933
Project: Tapestry 5
Issue Type: Improvement
Components: tapestry-core
Affects Versions: 5.2.0.0
Reporter: Howard M. Lewis Ship
Priority: Minor
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() ).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
