Hmm,
Opening up the get*fix methods doesn't seem risky, but I'm not sure
what we are going to do with the change recording. That is the only
thing I can tell why the methods are final.
Your usecase is interesting though. In this case opening the get*fix
methods doesn't seem to open a can of worms, other than limiting the
backbutton versioning. But in your case the set*fix method wouldn't be
called in the first place.
I'm +1 on removing final from the get*fix methods on the RadioChoice
component. Anyone else reading along and objecting?
Martijn
On 10/5/07, Clay Lehman <[EMAIL PROTECTED]> wrote:
> I am trying to customize RadioChoice so that it puts the options into a
> nice table. I found setPrefix and setSuffix, but I cant just do
> setSuffix(" ") because I want to have a differenct prefix & suffix
> based on the index (for example create a new row in a table for every
> 4th option).
>
>
>
> getPrefix and getSuffix are final methods, so I can't override them.
> Does anyone know of a way that I can accomplish this task using
> RadioChoice? Or will I have to go with a RadioGroup ...I'd rather have
> the list of options generated dynamically than from the HTML, if
> possible.
>
>
>
> Thanks for any help!
>
> -Clay
>
>
>
>
--
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.0-beta3 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta3/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
