Don,

page-flow.xpl is there just so that the main page flow can delegate to
sub-page flows. For example, the main page flow contains:

<page path-info="/forms*" model="/examples/forms/page-flow.xpl"/>

This tells the main page flow, then finding anything starting with
"/forms", to just call the specified page-flow.xpl. That pipeline just
calls up a "child" page flow processor, which runs the child page flow
configuration file (/examples/forms/page-flow.xml).

The bottom line is that this is a little trick to create sub-page flow
without having an actual sub-page flow functionality built into the Page
Flow Controller.

-Erik

Smith, Donald wrote:
> I’m studying the DMV example. What is the purpose of having a
> page-flow.xpl that does nothing but call page-flow.xml? Why not just
> have page-flow.xml?
>
>  
>
> What initiates the call to page-flow.xpl anyway? If both files are
> present, is the pipeline chosen over the other by default?
>
>  
>
> Thanks,
>
>  
>
> Don