Today I noticed I could in fact have a single implementation of
IChoiceRenderer which would work for most of my different persistent
classes, which all implement INamedPersistentObject exposing primary key
and human-friendly name - so I defined an
IChoiceRenderer<INamedPersistentObject> as a singleton and attempted to
use it.


I was immediately confronted with the problem that Wicket's choice
components want to receive an IChoiceRenderer<T>. I think all these
should be changed to IChoiceRenderer<? super T> to avoid imposing an
arbitrary unnecessary limitation.


Max.

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to