>>>>> On Fri, 11 Aug 2006 10:29:15 -0700, Adam Winer <adam.winer_at_oracle.com> said:
AW> Ed Burns wrote:
>> It turns out the JavaBeans PropertyEditors are strikingly similar to JSF
>> Converters, but offer more flexibility. Perhaps the JSF EG should have
>> just use those instead of inventing something new? Ah well, it's
>> (troubled) water underneath the bridge.
AW> Perhaps - but note that PropertyEditors are stateful, not
AW> stateless (consequently never could have been shared, as
AW> "binding" allows in JSF 1.2), have a huge load of APIs
AW> that are completely irrelevant and painful for JSF -
AW> getJavaInitializationString()? paintValue()? -
AW> have no direct concept of localization, and have no
AW> concept of reporting errors (other than IllegalArgumentException).
AW> I can't really see anything the PropertyEditor API has that
AW> Converter don't that would have been beneficial to Converters.
AW> So, I ain't crying over our decision. Similar isn't good
AW> enough.
Yes, that is true. Plus, PropertyEditors don't have any notion of the
component.
Ed
--
| ed.burns_at_sun.com | {home: 407 869 9587, office: 408 884 9519 OR x31640}
| homepage: | http://purl.oclc.org/NET/edburns/
| aim: edburns0sunw | iim: ed.burns_at_sun.com