--- Don Smith <[EMAIL PROTECTED]> wrote: > 1. Use two <page> elements in the page-flow.xml, using XUpdate to update > the model for the second page with the values gathered from the first, > and running the transform off the second page's values? > > 2. Use one <page> element with a pipeline that passes the values entered > by the user to the transform and then runs it?
Both approaches make sense. You should choose the most appropriate one based on your specific case: 1) You would use the first approach (2 pages in the page flow) when you are dealing with two distinct "logical pages", the second one using data captured by the first one. For instance if you have a page displaying a search form and another page displaying the search result based on values entered by the user in the form. 2) You would use the second approach (1 page in the page flow) when data entered by the user in the form changes the way the page is displayed. For instance if you are displaying a list of employees in a table (e.g. with first name, last name, and department columns) and your provide checkboxes allowing the end-user to specify by which column the data must be sorted. Alex ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ orbeon-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/orbeon-user
