[Converter] Should custom rules/error handlers be applied in reverse order?

[bjhargrave]

Original bug ID: BZ#3106
From: @bosschaert
Reported version: R7

[bjhargrave]

Comment author: @bosschaert

This issue comes from https://issues.apache.org/jira/browse/FELIX-6008

It's possible to create derived custom converters from an initial custom converter.
If we want to override some of the behaviour of the initial custom converter in the second level custom converter, the rules need to be applied in reverse order, otherwise they never get called. The same is true for the errorHandlers.

The spec doesn't seem to be very specific about the order in which custom rules and error handlers are invoked, especially for 2nd-level custom converter.

We should tidy up the spec on this point and also consider whether reversing is needed.

[bjhargrave]

Comment author: @bjhargrave

CPEG call: For R8 consider adding methods to add rules at beginning of list to complement the existing methods which add at end of list.

[bjhargrave]

Comment author: @bosschaert

Berlin F2F: this is a bug in the implementation and should just be fixed.

First all normal rules of the child need to be run, then all catchall rules. If the rules can't handle the conversion it should be delegated back to the parent.