Fox Calling FOX Module

Example

http://edu-app1/engdev8/fox/dev8/MODLAUNCH/new?A=1&B=2

http://server/engine/fox/app/module/entry-theme?parameters

server - The Web Server Host (e.g. edu-app1) or Virtual Host (og.berr.gov.uk). A single web server can support multiple Fox engines (at different Fox versions).
engine - The Fox Engine deployment / OC4J instance.
fox - Key word always required to call Fox Module.
app - Fox Application reference used to select which database and module table to use. Fox applications are configured by your administrator - defines database and module table.
module - Fox module to invoke, as defined in module table. Fox modules are defined in the Fox Module table - usually FOX_COMPONENTS_ENV.
entry-theme - Entry theme name, as defined in fox module. Entry themes are defined in the Fox Module. This part of URL is optional – if no entry theme is supplied, “new” is used by default.
parameters - Module call parameters.

These are optional and any number of parameters can be provided.
These are application specific, i.e. the module determines if required and their names.
When parameters are passed using the URL, parameter types are all xs:string.
Fox automatically translates parameter names to element names under the :{params} DOM. The parameter value is stored as text content inside the parameter element.
The :{params} DOM is retained for the duration of the Fox Module call. It can therefore be used with query bind variables (fm:using) or in XPath conditions.

There are two special parameters that are essentially workarounds: (these are just here so you know about them):

P_PORTAL_MENU_PAGE - used to specify a return URL when Fox call stack is empty.
foxopen - value is appended to URL tail before parameters - useful for JDEV developers.

Call XX_ORDERMODULE.xml by typing out its URL in the web browser, passing the instruction to use entry theme “new” and the following parameters:

Check the Params DOM to make sure they exist.