I ultimately just created a LabeledRadio component that did the trick. It's not
very flexible; the label ALWAYS immediately follows the radio button in the
source, which may not always be desirable, but it does the job that we need it
to do.
If it makes you feel any better the Radio component has driven me
crazy ever since early tacos days...The clash of concepts between a
group with the same name + individual component identifiers that works
cross browser has yet to produce a happy result.
If anyone figures anything out let us know.
For the clientId binding prefix as well as the correct generation of ids
you need 4.1.1 or (preferably) a 4.1.2-SNAPSHOT
Robert J. Walker wrote:
andyhot wrote:
if you use
then
Nice idea, but it didn't recognize the clientId: prefix for some reason. When I
cha
andyhot wrote:
> if you use
>
> then
> value="ognl:curChoice.label" raw="true"/>
Nice idea, but it didn't recognize the clientId: prefix for some reason. When I
changed it to its ognl equivalent (ognl:components.curRadio.clientId), this is
what rendered for the first radio button:
Yes
Th
if you use
then
Robert J. Walker wrote:
I'm having trouble rendering tags for individual radio buttons in
Tapestry 4.1. Simplified example:
This works fine, except that I'd like for each radio button to have a
tag rendered for it so that the labels are actually c
