Hi,
When I step through the pages in my application, I always (except for the first page) see the page URI of the *previous* page in my browser's location field. This looks very strange...
This is when I use <config instance-passing="forward"> in my page-flow.xml, to get rid of the long URI's (see a previous thread). When I omit this attribute, the base URI's are correct and not one page behind, except that the long URI's (containing the whole form) are back then... :-(
Yes, because in order to allow the page flow to make a dynamic decision as to what the next page is, forms are submitted with the URL of the current page. This works well from a URI perspective when you do redirects, but with server-side forwards you get that lag (because page A submitted the form, and the result is the content of page B).
One "solution" to end the confusion would be to use meaningless page names. Other frameworks exhibit a similar behavior, like the JSF RI, last time I checked.
-Erik
------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ orbeon-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/orbeon-user
