SAX for WAP binary XML

Stefan Haustein stefan.haustein at
Tue Dec 14 21:40:04 GMT 1999


I have implemented a SAX based JAVA parser for WAP binary encoded
XML. ( However, there are some problems
with SAX for WBXML:

- WBXML adds some properitary extensions. For that reason, I added an
  interface "WapExtensionHandler". Can that interface or a similar one
  be included in org.xml.sax.wap? Who cares about extensions of
  org.xml.sax? Unfortunally, the ugly extensions cannot be ignored
  since they are alread used in the WML definintions.
- The handler for the WAP extensions needs to be registered at the
  parser. WML depends on fixed "tag and attribute tables", other WBXML
  languages also may use similar tables. A mechanism to register the
  tables with the parser is needed. Thus, an extended Parser interface
  is needed (e.g. org.xml.sax.wap.WbxmlParser)

- WBXML is designed for small devices like a Palm Pilot. Deriving the
  WbxmlParser from org.sax.xml.Parser includes a lot of unneeded
  overhead. It could be a better solution to start a new hierarchy
  (WbxmlParser -> WapParser). A Wrapper could implements the full
  org.sax.xml.Parser interface for compatibility.

Most issued are solved "somehow" in my parser. However, extending the
standard (e.g. by adding a org.xml.sax.wap package) would be better
solution since WBXML parsers then could be exchanged without changing
the application.

Best regards


xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at
Archived as: and on CD-ROM/ISBN 981-02-3594-1
To unsubscribe, mailto:majordomo at the following message;
unsubscribe xml-dev
To subscribe to the digests, mailto:majordomo at the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at

More information about the Xml-dev mailing list