On Aug 19, 2011, at 8/198:56 PM , Bob Harner wrote:
> Does anyone know why half of the built-in Tapestry 5 components that
> take an "encoder" parameter are NOT set up to be able to use a
> "contributed" ValueEncoder (that is, one configured with
> contributeValueEncoderSource() in AppModule class)?
>
> The following components nicely allow the "encoder" parameter to be optional:
>
> Grid, GridRows, Loop, Select, Upload:
>
> But the following make you provide the encoder parameter (even if you
> have a ValueEncoder configured in your AppModule for the appropriate
> type):
>
> AjaxFormLoop, Palette, Checklist, Hidden, RadioGroup
>
Not entirely following... at least in trunk:
From AjaxFormLoop:
ValueEncoder defaultEncoder()
{
return defaultProvider.defaultValueEncoder("value", resources);
}
Hidden:
ValueEncoder defaultEncoder()
{
return defaultProvider.defaultValueEncoder("value", resources);
}
RadioGroup:
final ValueEncoder defaultEncoder()
{
return defaultProvider.defaultValueEncoder("value", resources);
}
And, for the record, Grid (to demonstrate the fact that Grid is default the
same way):
ValueEncoder defaultEncoder()
{
return defaultsProvider.defaultValueEncoder("row", resources);
}
But it does appear that Palette and Checklist are not proving a default
encoder, and the why behind that I don't know.
Robert
> Maybe there's some subtle reason for this?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: dev-h...@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org
