Excellent...great enhancement...sorry for my tardy +1!
Thanks Bauke
Josh Juneau
juneau001_at_gmail.com
http://jj-blogger.blogspot.com
https://www.apress.com/index.php/author/author/view/id/1866
On Tue, Jun 14, 2016 at 6:56 AM, Bauke Scholtz <balusc_at_gmail.com> wrote:
> It has been implemented
> https://java.net/projects/mojarra/sources/git/revision/8f102043307e371056f4cbb983a2b5caf620ef1f
>
> On Mon, Jun 13, 2016 at 9:09 PM, Neil Griffin <
> neil.griffin_at_portletfaces.org> wrote:
>
>> +1
>>
>> This restriction probably dates back to the days of JSF 1.0/1.1 and Java
>> SE 1.4 before java.util.Collection had type enforcement via generics.
>>
>> > On Jun 13, 2016, at 3:04 AM, arjan tijms <arjan.tijms_at_gmail.com> wrote:
>> >
>> > Hi,
>> >
>> > +1
>> >
>> > No objection, sounds like a good idea. Especially since MyFaces
>> implemented it already I almost assume a default +1 by them (but would be
>> good to see it explicitly here ;)).
>> >
>> > Kind regards,
>> > Arjan Tijms
>> >
>> >
>> > On Sat, Jun 11, 2016 at 9:56 AM, Bauke Scholtz <balusc_at_gmail.com>
>> wrote:
>> > Hi,
>> >
>> > See https://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-1422.
>> >
>> > Currently,
>> http://docs.oracle.com/javaee/7/api/javax/faces/component/UISelectMany.html
>> states that it won't make any attempt to obtain the converter when the
>> value is of type java.util.Collection.
>> > It is technically however possible to obtain it anyway by inspecting
>> the first non-null select item. MyFaces has this already implemented and I
>> find it's a good idea to improve the spec accordingly.
>> > This should save the effort of explicitly declaring the converter by
>> name and rely on forClass.
>> > If there are no objections, I will take care of it for 2.3.
>> > Cheers, B
>> >
>>
>>
>