I am doing some nips and tucks to the event stuff (mainly an example and
a testcase) and ran across this again - this was mentioned before, and
got no opposition - figured I would run it up the flagpole one more time
if anyone is interested :

We have two related event handler interfaces,

public interface  NullReferenceEventHandler extends EventHandler
{
    public Object nullReferenceRender( String reference );
}

and 

public interface  ReferenceInsertionEventHandler extends EventHandler
{
    public Object referenceInsert( String reference, Object value  );
}

They both are used when rendering a reference, the first is called only
when a reference is null, to give the app a chance to substitute a
value, and the second is called when a reference is NOT null, to give
the app a chance to substitute a value.

I feel that it is confusing and redundant to have both, and would like
to remove the first and just use the second one, because

  nullReferenceRender( foo ) == referenceInsert( foo, null )

So I don't get held up, and since we did discuss before, I am going to
go forward with this, and will back out immediately if there is any
reasonable opposition.

geir

-- 
Geir Magnusson Jr.                           [EMAIL PROTECTED]
System and Software Consulting
Developing for the web?  See http://jakarta.apache.org/velocity/
"still climbing up to the shoulders..."

Reply via email to