Multiple calls of action method after exception during update model phase

Question

using: Sun RI 1.1_01
Situation: have a view with
* a field that has a value binding to a setter that can throw an exception, with a message tag
* a command button bound to an action method
Enter a value in the field that will trigger the exception. You will get the same page again, with a message from the exception; the action method is not called.
Now change the value to something that will be accepted by the setter. The action method will now be called twice.
I presume this is a bug?
On code inspection of the RI 1.1_01, it turns out that an EvaluationException is thrown, which is translated by the ValueBindingImpl#setValue method into another EvaluationException, after posting the exception message as JSF message. This method is run inside UIInput updateModel, which essentially sets valid to false. This will result in interrupting the normal phase cycle, and makes us jump to render response, as expected.
Now all this happens during the update model phase, and earlier an event for the application phase was posted, to trigger execution of the action method. Since we did not reach the application phase, this event is never executed, but also it is never removed from the event List structure.
It is lurking inside the UIViewRoot, and is still there in the next request/response cycle. If in this next cycle, there is no more interruption, we will eventually reach the application phase, but there we now have 2 events waiting to be executed. As a result, the action method will be called twice.
If you trigger the exception in the setter more often, all action events will be saved for the next cycles. If you trigger the exception n times, the action method will be executed n+1 times the first time there is a submit with no exception.
This can not be intended behavior, can it?

Answer 1

BTW: MyFaces does this in UIViewRoot:
    public void processUpdates(FacesContext context) {
        if (context == null) throw new NullPointerException("context");
        super.processUpdates(context);
        _broadcastForPhase(PhaseId.UPDATE_MODEL_VALUES);
        if (context.getRenderResponse() || context.getResponseComplete())
            clearEvents();
    }Events are cleared. Guess we are switching, then.