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.
Perhaps - but note that PropertyEditors are stateful, not
stateless (consequently never could have been shared, as
"binding" allows in JSF 1.2), have a huge load of APIs
that are completely irrelevant and painful for JSF -
getJavaInitializationString()? paintValue()? -
have no direct concept of localization, and have no
concept of reporting errors (other than IllegalArgumentException).
I can't really see anything the PropertyEditor API has that
Converter don't that would have been beneficial to Converters.
So, I ain't crying over our decision. Similar isn't good
enough.
-- Adam