Following the rules described in this document will facilitate the task of porting Adelia Web applications for AJAX mode.
Rule no. 1
Check that your XHTML template is compatible with the standard published by the World Wide Web Consortium.
Non-compliance with this standard may result in Javascript errors when the page is updated.
For example, placing a <FORM> tag in a <TABLE> tag but outside a <TD> is not permitted.
The Dreamweaver® layout designer does not check compliance with this standard, but you can do so using the World Wide Web Consortium's validator at http://validator.w3.org/.
Rule no. 2
Check that all <ADELIA :TABLELIST> tags contain a <TBODY> tag if they are to be refreshed in AJAX mode.
If they do not, selecting the tag in the Dreamweaver® layout designer will automatically add the <TBODY> tag.
Rule no. 3
Check that the event processing blocks for the ONLOAD and ONUNLOAD Javascript events are present.
These events are no longer triggered when an Adelia AJAX event that loops on the same page is executed.
Rule no. 4
Check that the Javascript libraries that are used do not execute document.write or document.writeln instructions. These instructions are not compatible with AJAX mode. Replace any such calls with calls to DOM Javascript APIs.
Rule no. 5
Check whether any Javascript processes are run when the page is loaded. Any such processes that must be run for each Adelia event should be placed in a Refresh Area object.
We recommend grouping all the processes together in the same Refresh Area object.
Rule no. 6
Check that switching an Adelia event from standard mode to AJAX mode is really justified. We advise against converting to AJAX mode any event processing blocks that systematically display a page other than the current page when executed.
Rule no. 7
Use the :COMP parameter to adjust an AJAX event's behavior based on functional requirements, to determine the response if the user triggers an event that is already being processed on the web application server.