[TAP5-933] EnumValueEncoder will create a ValueEncoder even when there's a specific String->Enum type coercion

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 5.2.0
• Fix Version/s: 5.3
• Component/s: tapestry-core
• Assignee: Howard Lewis Ship
• Reporter: Howard Lewis Ship
• Created: 22/Nov/09 13:40
• Updated: 23/Sep/11 20:12
• Resolved: 23/Sep/11 20:12

Description

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