page-flow.xmlstored at the root of your Orbeon Forms resources. This XML file has a root element called
<controller>, which has to be within the
http://www.orbeon.com/oxf/controllernamespace. All the XML elements in a page flow have to be in that namespace unless stated otherwise. You start a page flow document as follows:
web.xmlfile. See Packaging and Deployment for more information. In most cases, it is not necessary to change the default name and location.
http://www.orbeon.org/identifies the web or application server hosting the application.
/myappmay optionally identify the particular web application running on that server. Whils this part of the URL path is not mandatory, its use is encouraged on Java application servers, where it is called the context path.
/report/detailidentifies the particular page within the web application. Such a path may be "flat", or hierarchical, separated with "/" (slashes).
?first=12&count=10specifies an optional query string which identifies zero or more parameters passed to that page. Each parameter has a value. This example has two parameters: the first one is called
12, and the second one is called
#middleis an optional fragment identifier identifying a section of the resulting page. Usually, this part of the URL is not handled by the web application, instead the web browser uses it to scroll to a section of the resulting page identified by this identifier (here
/report/detail. Therefore, in an Orbeon Forms page flow, each page is identified with a unique path information. You declare a minimal page like this:
<service>element denotes a service:
viewattribute on a
<page>element which points to an XHTML file:
<page>element is contained. Here is an example of the content of
http://www.w3.org/1999/xhtml. This can be done by using default namespace declaration on the root element (
xmlns="http://www.w3.org/1999/xhtml) or by mapping the namespace to a prefix such as
xhtmland to use that prefix throughout the document, as shown above. The file must contain well-formed XML: just using a legacy HTML file won't work without some adjustments, usually minor.
<page>element therefore supports attributes defining what page model and page view must be used:
<name>element as follows: