kXML 3 Architecture

For kXML 3, it is planned to change the architecture of kXML without significant impact on users. Motivations for the changes are:

• kXML3 shall support both, XmlPull and StAX.
• Including namespace handling in the parser makes the code less readable, hindering progress such as better charset support in WBXML.
• The redundancy of the namespace handling code in the XML and WBXML parsers does not seem very elegant.
• For limited environments, it should be possible to use kXML without namespace handling overhead. Currently, the kobjects.org parser can be used for that purpose, but again the code redundancy leads to unneccessary maintenance overhead.

Planned kXML 3 architecture

To improve the situation, it is planned to shift the namespace handling to StAX and XmlPull specific parts, which use a common basic parser interface for both, XML and WBXML, as depicted in figure 1.

Implementation Status

Currently, the left part of figure is implemented and accessible via CVS (module kXML3). Of course, Any kind of support is welcome!