Differences between revisions 25 and 26
Revision 25 as of 2004-12-02 17:05:26
Size: 2088
Editor: 12-223-244-34
Revision 26 as of 2009-09-20 22:48:45
Size: 2084
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
List of requirements for [wiki:FrontPage/Architecture/OM AXIOM] List of requirements for [[FrontPage/Architecture/OM|AXIOM]]
Line 7: Line 7:
See also: OM Use Cases Discussed in [wiki:FrontPage/Architecture/OMUseCases] See also: OM Use Cases Discussed in [[FrontPage/Architecture/OMUseCases]]
Line 9: Line 9:
See also: OM Use Cases Discussed in [http://wiki.apache.org/ws/FrontPage/Architecture/OMHistory] See also: OM Use Cases Discussed in [[http://wiki.apache.org/ws/FrontPage/Architecture/OMHistory]]

List of requirements for AXIOM

Use Cases

See also: OM Use Cases Discussed in FrontPage/Architecture/OMUseCases

See also: OM Use Cases Discussed in http://wiki.apache.org/ws/FrontPage/Architecture/OMHistory

OM according to the December 2004 .. refer to todays chat

Only thing we are not decided on OM is does it contains the SAAJ like API or is it just XML representation.

Building OM

OM can be build by two ways

  1. Using a StaX pull events, there is a builder that accepts a pull parser and do the differed building
  2. Using SAX push events, there is a builder that accept a Objects or Push event generator and build the OM.
  3. OM can be build just like DOM tree is build inserting child elements

Using OM

  1. OM exposed a XML infoset representation that is easy to use by the java developers. That interface is based on iterators.
  2. OM expose the Stax event and is capable of shifting to the stream in the middle if the OM is half build.
  3. OM support writing itself in to the Output stream. We like OM to fed information to a Push interface so the PushEvent handler may write them to stream. This leave room for binary serialization in future.


  • OM support DOM by wrapping it
  • OM support the StAX interface
  • OM support turning on -off caching
  • Serializing and Deserializing is pull out of OM, we will provide the the utilities to used by the developers so that they can programming like getObjectValue(), setObjectValue(...) but that is encoding and out of scope for M1. (see the chat)

OM Support following

The MTOM support

The binary information in the OM element can be taken from the OM element. There are few proposals the Glen's MTOM toy, Alek's includes, Ajith's Binary node. We differ this for the M1.

Href support

But it is differed

XML Security Support

Make sure XMLSecurity works over that DOM for encryption, decryption, signing and verification. This is at the XML level

FrontPage/Architecture/OMRequirements (last edited 2009-09-20 22:48:45 by localhost)