Posted by edburns
on September 9, 2008 at 8:51 AM PDT
I poll the community about whether to break backwards compatibility in one small interface in JSF 2.0.
One of the worst things about Java is the lack of a language level
solution to the
base class problem. In the absence of a solution, the JSF EG has
resorted to creating subclasses of interfaces, appending a digit to the
interface name, and adding the methods there. For example, we created
as an extension of
just so we could support
for the Unified EL in JSF 1.2.
The fragile base class problem is one we commonly face when evolving
an API and JSF is no exception.
Spec Issue 327, filed by Trinidatd stalwart Matthias Weï¬‚endorf,
requests the addition of
resetValue directly to
which would clearly break existing implementations of this interface.
2008 last week I spoke with Herr Weï¬‚endorf and he asserted that most
of the implementations of this interface will have a
method, ore one very similar to it, in general.
Therefore the pain of adding it to
directly outweighs the nonsense of creating
just for adding this method. It's a
compelling argument, but I want to poll the community before doing
Please comment if you have an opinion about this minutia of JSF 2.0
Technorati Tags: edburns