XAP Executive Summary
This page provides an executive summary of the Apache XAP project from the perspective of OpenAjax.
Links to Apache and other Information Sources on XAP
Description copied/pasted from XAP web site
Key component technologies
The XAP proposal at Apache has some major components, each of which is potentially a separable module.
There isn't an official name at this point, but for the purposes of this discussion the term "Core XAP" represents the low-level features in the XAP proposal that deals with mapping custom XML markup to Ajax toolkit libraries that handle that markup. Thus, Core XAP is very much relevant to topics discussed in the Tibco/Dojo proposal: Tibco Dojo Proposal Toolkit Loading, Markup Mixing.
"Core XAP" enables XAP to support different Ajax toolkits as well as different markup languages. Anybody can plugin any XML compliant markup languages, or any Ajax toolkit, or both.
XAL (Extensible Application Language) is an application markup language that includes data providers, data binding, iterators, formatters, layout managers, and of course widgets. Regarding widgets, XAP wants to leverage widget libraries from other Ajax initiatives. The first delivery of XAP leveraged Kabuki widgets and Dojo support is on the way.
XAL's design center is as a top-level markup language.
Early examples have separate .xal files. Thus, you have an HTML file which refers to the appropriate .xal file(s) and has an empty html:body element. The XAP engine then populates the html:body with the "view" from the "model" that was included in the .xal file.
Managed Client Objects (MCOs)
XAP includes its own XML parser and DOM engine