You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-dev@ws.apache.org by Yuhichi Nakamura <NA...@jp.ibm.com> on 2000/12/30 16:54:49 UTC
[Axis Doc] Basic Notions
Folks,
I also described an architecture design at an abstract level in the
attached file.
This document basically corresponds to Steve's Section 3, but I also
illustrated
architecture design relating defined components. Usecase is not completed,
but
you may find some difference among Steve's, James's and mine.
The following is an excerpt from the document:
When designing the architecture, we pay particular attention to the
following aspects:
1. Should be compliant with SOAP 1.1 specification, not allowing
programmers to develop SOAP-incompliant applications (as much as
possible).
2. Should provide API, which explicitly reflects SOAP semantics.
3. Should have a kernel portion, which only concerns the SOAP
specification, and provide extensions on top of the kernel.
In comparison to Steve and James, I pay particular attention to SOAP
semantics. As a result, instead of generic Chainable class/interface, I
define SOAP-specific API reflecting SOAP constructs. (The API is based on
the discussion with Ryo, but he has not reviewed this document. He may
have a different proposal.)
Best regards,
(See attached file: AXIS Arch.pdf)
Yuhichi Nakamura
IBM Research, Tokyo Research Laboratory
Tel: +81-46-215-4668
FAX: +81-46-215-7413