AXIOM (AXIs Object Model) Diagrams
The proposed model converts the incoming stream into objectswhen it is dispatching the incoming request to the soap service. Intermediate representation (OM) will only be created when a handler requests the processing of the SOAP body (e.g. Security handler). The OM only keeps the parts that are read so far in the memory. The rest is served direclty from the stream.
Features of the Object Model (OM)
- Emulates DOM.
- Emulate pull parser.
- Light weight.
- Stores only the portions read. Rest is in the original stream.
Accepts an object and generates push (e.g. SAX) events that will be transformed into either
A genetrated code that deserializes the stream to an object(s) by using the pull model.
Message inflow (At server or client)
The following diagram explains the typical conversions that happen during processing inside the axis engine. This can take place either is the server, receiving the request or the client, receiving the response.
Message outflow (At server or client)
The following diagram explains the typical conversions that happen during the processing inside the axis engine. This can take place either at the server, sending the response or at the client, sending the request.
Proposed OM Architecture
The following will explain what is in AXIOM and what is out of the AXIOM.