[T5] ValueEncoder <=> TypeCoercer?

[Ognen Ivanovski <og...@netcetera.com.mk>]

Hello again,

I'm trying to write a CheckboxGroup / Checkbox pair of components for  
my project based on the RadioGroup / Radio components in the corelib.

While doing so I stumbled upon the ValueEncoder / ValueEncoderSource  
and I keep wondering why are they introduced and why isn't the type  
coercion used instead (objectType -> string, string -> objectType)?

Also in this direction, it would be good if one can contribute more  
dynamic type coercion configuration. E.g. if one uses Hibernate, one  
could contribute just one coercion handler that can turn any @Entity  
into a string and back (using the entity's declared @Id properties).

This would greatly simplify Radio's, Checkboxes, Selects and the like.

Cheers,
Ognen

--
Ognen Ivanovski | ognen.ivanovski@netcetera.com.mk
phone +389 -2- 30 64 532 | fax +389 -2- 30 79 495
Netcetera | 1000 Skopje | Macedonia | http://netcetera.com.mk




---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org