Hi, Is there anywhere a detailed scheme (preferably a picture) that shows *exactly* how the various documents used in the pipelines and XSL steps of page-flow.xml relate to each other?
I thought I understood it, after writing a kind of trace system that showed which steps were done in what order, but now I came across somnething new I didn't know of yet, so I'm afraid that I'm maybe missing more information. In the ATM example, the enter-pin-action.xsl returns a document with a <valid> node (only). That document is used for the <when> checks. Still all as I expect. But I also see that the document with the <valid> node seems to be used as a model for the page when it is displayed again: enter-pin-view.xsl checks "/valid". But I thought a model (XSL input for the view) could only be generetad by a "model=" attribute for a page, and here the output of an action seems to act as a model too. Confused... Thanks, -- -- Jos Vos <[EMAIL PROTECTED]> -- X/OS Experts in Open Systems BV | Phone: +31 20 6938364 -- Amsterdam, The Netherlands | Fax: +31 20 6948204 ------------------------------------------------------- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 _______________________________________________ orbeon-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/orbeon-user
