+1 on implementing a standard component that makes it easy for users to lay
out the h:selectOneRadio button in a more flexible manner. These trivial
issues with JSF have led to many arguments against using the framework.
The easier it is made for beginners, the better in my opinion.
Josh Juneau
juneau001_at_gmail.com
http://jj-blogger.blogspot.com
https://www.apress.com/index.php/author/author/view/id/1866
On Wed, Aug 19, 2015 at 1:08 PM, arjan tijms <arjan.tijms_at_gmail.com> wrote:
> I agree with Bauke, this has been asked for a lot of times by users. I
> had a bunch of personal messages in response to my JSF 2.3 wish list
> asking for exactly this.
>
> Such a component seems to be "basic" enough to be a good candidate for
> inclusion in the JSF standard component set.
>
> Kind regards,
> Arjan Tijms
>
> On Wed, Aug 19, 2015 at 7:27 PM, Bauke Scholtz <balusc_at_gmail.com> wrote:
> > I vote against. This is one of most common requirements from the
> community.
> > I'd like to see this to end up in standard component set too. A custom
> > renderer is not trivial to starters, for sure not if you'd like to use
> it in
> > an repeater component like <h:dataTable><h:column><h:selectOneRadio>
> and/or
> > if you want to have a separate <h:outputLabel> for each item.
> >
> > Cheers, B
> >
> >
> >
> >
> > On Wed, Aug 19, 2015 at 7:16 PM, manfred riem <manfred.riem_at_oracle.com>
> > wrote:
> >>
> >> Hi all,
> >>
> >> I like to close this one as "Won't fix" as well as it is fairly easy to
> >> register your own renderer.
> >>
> >> To introduce a new component for it seems overkill.
> >>
> >> Thoughts?
> >>
> >> Note I like to close the loop on this one before 8/26.
> >>
> >> Thanks!
> >>
> >> Kind regards,
> >> Manfred Riem
> >>
> >>
> >
>