For Select, a default encoder can be generated from the type of property bound to the value parameter of the Select.
For Palette, what's bound is a List ... due to type erasure, even List<Foo> looks like List, and there is no effective way to determine the underying element type, so you are forced to provide that information to Tapestry. On 7/27/07, Thiago H de Paula Figueiredo <[EMAIL PROTECTED]> wrote: > > Hi! > > Why is encoder a required parameter for the Palette component and isn't > for Select? Looking ate the Select source code, we can see that it uses de > ValueEncoderSource service to find a default ValueEncoder when the encoder > parameter is not set. > > And has anyone implemented a Select-like component for multiple option > selection? It would be very nice to have both multiselect and palette, as > T4 has. > > Thiago > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com
