|
Dynamic pages are displayed by the MoreMotion AF.
Remember that when we want to link to a page we just give the name of the page in the Application Studio without any extension. We don't care whether the page we are linking to is static or dynamic since MoreMotion AF will handle it.
Here is a typical request to the MoreMotion AF to display a page.
display.doms?pg=Page1
When MoreMotion AF receives a Display Page request i.e. "Page1";
| 1. | It checks whether "Page1.html" is existing; If yes it displays it. |
| 2. | It checks whether "Page1.xsl" is existing; If yes then it starts with the following procedure applied for dynamic pages. |
| 3. | It access the configuration file of the page that is located under /WEB-INF/MM-INF/config/pages directory. The page configuration files are created by the Application Studio during build. |
| 4. | Depending on the type of the data sources used in a page, MoreMotion AF calls the data service classes associated with the data sources to let them populate data. |
| 5. | Once the responsible service class populates data in ADOMs, MoreMotion AF converts them into XML and builds the Page XML Data. This XML contains all the data required by the Page XSL. |
| 6. | MoreMotion AF resolves resource definitions nested in XML data nodes according to the language of the page using provided resource files. |
| 7. | MoreMotion AF checks whether the requester browser can do XSLT; if yes it just sends the generated Page XML Data as the response to the requester. |
| 8. | If the browser has no XSLT capability, then it utilizes the configured XSLT processor to generate a HTML by transforming the Page XML Data with the instructions in the Page XSL; and it sends it as the response to the requester. |
| 
