Aside from the decision if it's relevant enough/possible in the timeframe,
what made you prefer a Set over a more general Collection?
I know, in another EG, either JSF or JPA we have a CR to move away from a
Set or List to the more general Collection. Maybe it isn't required here,
but I would hope we could get that right from the start ;-)
Werner
On Tue, Feb 28, 2012 at 6:21 PM, Lincoln Baxter, III <
lincolnbaxter_at_gmail.com> wrote:
> Jason Porter recently brought this idea to my attention, and I think that
> he is right.
>
> http://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-1078
>
> If we are going to be adding a new DataModel implementation for Sets, I
> think it makes a *lot* of sense to expose an API for adding custom
> DataModel registrations.
>
> Thoughts? Enough time to include this?
>
> --
> Lincoln Baxter, III
> http://ocpsoft.com
> http://scrumshark.com
> "Keep it Simple"
>
--
Werner Keil | JCP Executive Committee Member (ME) | Eclipse UOMo Lead
Twitter @wernerkeil | #Java_Social | #EclipseUOMo | #OpenDDR
Skype werner.keil | Google+ gplus.to/wernerkeil
* geecon: May 16 2012, Poznań, Poland. Werner Keil, JCP EC Member, Social
JSR Co-Spec Lead will present "Java EE 7"
* JustJava: May 19-20 2012, Sao Paulo, Brazil. Werner Keil, JCP EC
Member, Social
JSR Co-Spec Lead will present "Social Java"
* Dutch Mobile Conference: June 7-9 2012, Amsterdam, Netherlands. Werner
Keil, JCP EC (ME) Member, OpenDDR Evangelist will present "OpenDDR"