On Tue, 21 Sep 2004 01:44:00 -0600, "Bill Winspur" <[EMAIL PROTECTED]> said: > Julien Mercay wrote: > > > Hi Bill, > > > > If I understand you correctly, your page-flow.xml only contains the > > two declarations for hello4, taken from tutorial/hello4/page- > > flow.xml. Can you also make sure that the xforms, model and view > > attributes of the page elements correctly point to the XForms, XPL > > and XSL files, by using the absolute URLs if necessary > > (oxf:/path/to/file.xpl for example). > > > > The page not found message typically happens when the Page Flow > > Controller can't find a match between the browser's request and the > > declared pages, via the path-info attribute. Please also make sure > > that you also prepend the servlet context. For example, let's say > > that you deploy orbeon.war into the /orbeon servlet context. A page > > entry with a path-info value of "/tutorial/hello4" is accessed with > > the following URL: > > > > http://localhost:8080/orbeon/tutorial/hello4 > > Julien, > > Thanks for your reply, it clarified my understanding of what is > supposed to happen in OXF. > > a. As you suggested, I made sure that 'the xforms model and view > attributes of the page elements (in the hello4 page-flow.xml) > correctly pointed to the XForms, XPL and XSL files'. > > b. Re your point about matching the url to the OXF page mapping, I > tried several combinations of path-info and url, and none worked. > At this point I had two pageflow files, one in resources/ and the > hello4 pageflow in resources/pages/ > > c. Finally, assuming that > i) Resources/page-flow.xml has declarations which are generic > throughout the orbeon.war, and that > ii) The pageflows in the examples are example specific, and that > iii) OXF uses ONE page-flow (the resources/ one), and that > iv) My app-specific pageflow was not visible to OXF > > I copied the hello4 page elements into resources/page-flow.xml, > adjusted their path-info attributes, and the pages worked. > > Separating the generic declarations of pageflow from the app/example > specific declarations is a cool modularity. I'd like to automatically > combine them at runtime, rather than combine them manually during > development. > > Questions > --------- > 1. Does orbeon.war normally, dynamically aggregate page-flow files as > I did manually? I could not find a place where that is done.
Hmm, seems our packaging is causing some confusion. Orbeon.war contains the Presentation Server, the Demo App, and the samples. The Demo App just exists to present the documentation and the samples. It wasn't exactly written to be a good example itself. The 'aggregation' you are seeing is happening in the Demo App. The files examples-list.xml and dispatch.xpl are where the work is done. As the file name suggests, the model is more one of dispatch that aggregation. ( FWIW ) That said, this dispatch mechanism does rely on a particular feature of the Presentation Server. If you look at the end of dispatch.xpl you see that the Page Flow Controller is itself just another processor. ( Feel free to let your imagination run wild with possiblities here... ;) ) > > 2. If orbeon.war does not aggregate page-flows, how do the page > elements of example page-flows become visible to the controller? See above. -- Dan S ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ orbeon-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/orbeon-user
