I made this as a custom component from my group. Unfortunately, I
don't think I'll ever be able to contribute the code to MyFaces, but
I'll tell you how I implemented it.
Basically, I had a <selectOne /> and <selectMany /> tag that contained
the valuebinding, converter, id, etc. However, this was just a
placeholder tag. In order to render the actual options, I had
separate tags called <selectOption />. The placement of these tags
determined the placement of the actual radio buttons on the page.
Here is an example usage that solves your problem:
<hjb:selectOne value="#{myBean.myValue}" id="mySelectOne" />
<h:dataTable value="#{myBean.myAvailableOptions}" var="myOption">
<h:column>
<hjb:selectOption value="#{myOption}" for="mySelectOne" />
</h:column>
<h:column>
<h:outputText value="#{myOption.display}" />
</h:column>
<h:column>
<h:outputText value="#{myOption.description}" />
</h:column>
</h:dataTable>
I hope that helps in your implementation. Sorry that I can't
contribute the actual component. If its any consolation, this was an
easy component to make.
On Wed, 26 Jan 2005 17:59:16 -0500, Sean Schofield
<[EMAIL PROTECTED]> wrote:
> > Is this something that the new forceid property will
> > help with?
>
> Unfortunately not. You'll just get RadioButton[0], RadioButton[1],
> etc. That's much better than the JSF bastardized version (in my
> opinion) but that won't help you in this case.
>
> Why don't you submit a bug/enhancement report in JIRA?
> (http://issues.apache.org/jira). Just create an account for yourself
> and then create the bug in myfaces project. (If you have an existing
> bugzilla account you may be able to use that one.)
>
> Anyways, once we establish something is a bug (or would be a good
> feature) we should be encouraging users to report them officially
> through JIRA. Since I agree this would be a good feature, go ahead
> and add it. You'll automatically be notified once its fixed/closed.
>
> > Pat Young
>
> sean
>
--
-Heath Borders-Wing
[EMAIL PROTECTED]
