H Bauke,
With those examples in mind this change would be a -0 for me (meaning I
am leaning towards -1, but I am letting the door open for Ed to weigh in).
Thanks!
Kind regards,
Manfred Riem
On 1/3/17, 11:44 AM, Bauke Scholtz wrote:
> Hi,
>
> There would be no UIForm when there's no <h:form>. In other words,
> that's the case when UIInput components are enclosed in a plain
> vanilla GET <form> (commonly known case: j_security_check), or when
> the UIInput instance comes from <f:viewParam>. The UIInput#getForm()
> could simply return null in such case.
>
> Cheers, B
>
> On Tue, Jan 3, 2017 at 7:41 PM, manfred riem <manfred.riem_at_oracle.com
> <mailto:manfred.riem_at_oracle.com>> wrote:
>
> Hi Bauke,
>
> An interesting thought.
>
> Be aware public review is rapidly approaching and this most
> certainly would require spec changes.
>
> Note you own words "... are usually placed in ... " merit more
> research and I am not sure we can do all the due diligence in time.
>
> Thanks!
>
> Kind regards,
> Manfred Riem
>
>
> On 12/27/16, 9:53 AM, Bauke Scholtz wrote:
>
> Hi all,
>
> Hopefully I'm not too late into the game for a new API method.
>
> While working on improving <h:selectOneRadio group> I wished
> there was an UIInput#getForm() which returns the enclosing
> UIForm of the UIInput component, so I could grab its client ID
> which I can then prepend to the group name.
>
> I personally don't see why there would be no UIInput#getForm()
> in the API as UIInput components are usually placed in an UIForm.
>
> Thoughts?
>
> Cheers, B
>
>