Bug in faces-config.xml parser?

Question

According to the spec, the FactoryFinder is supposed to call the one-arg constructor taking the Abstract factory. For instance, I have this factory class:
public class ExtendedLifecycleFactory extends LifecycleFactory {
  public ExtendedLifecycleFactory(LifecycleFactory base) {
    // this is supposed to be called by the FactoryFinder
  public ExtendedLifecycleFactory() {
    // this is not
}And I have the following definition in my faces-config.xml:
<faces-config>
  <factory>
    <lifecycle-factory>com.foo.ExtendedLifecycleFactory</lifecycle-factory>
  </factory>
</faces-config>For some reason, my one-arg constructor isn't being called.
According to the FactoryFinder source, it appears that it maintains an internal list of all of the factories of a given type passed to it via the setFactory() method. Then, it starts at the last entry in the list (which should be the default implementation) and iterates through to the first one passing the previous implementation to each one in the iteration. Here is pseudo-code:
Factory prev = list.get(list.size() - 1);
for (int i = list.size() - 2; i >= 0; i--) {
  prev = callOneArgFirstAndNoArgSecond(list.get(i), prev);
return prev;When I debugged the FactoryFinder, it appears that the parser for the faces-config.xml file never calls FactoryFinder.setFactory() with the default implementation. It seems that this is a bug since the JSF 1.0 spec lists this as the last step in finding a factory for the faces application.
Am I correct in this assumption?
I'm hoping Craig will answer this one as I've thoroughly done my homework! :-)

Answer 1

Hello,
Yes, you are correct, this was a problem with the 1.0 RI and has been corrected.
This fix will be made available with the next release.