axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject cvs commit: xml-axis/java/docs messagemodelclasses.jpg soapmessagemodel.jpg architecture-guide.html
Date Thu, 31 Jan 2002 12:04:14 GMT
glyn        02/01/31 04:04:14

  Modified:    java/docs architecture-guide.html
  Added:       java/docs messagemodelclasses.jpg soapmessagemodel.jpg
  Describe (SOAP) message model subsystem.
  Revision  Changes    Path
  1.3       +41 -2     xml-axis/java/docs/architecture-guide.html
  Index: architecture-guide.html
  RCS file: /home/cvs/xml-axis/java/docs/architecture-guide.html,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- architecture-guide.html	28 Jan 2002 18:22:59 -0000	1.2
  +++ architecture-guide.html	31 Jan 2002 12:04:13 -0000	1.3
  @@ -38,6 +38,9 @@
   <br>&nbsp;&nbsp;&nbsp; <a href="#Message Contexts">Message Contexts</a>
   <br>&nbsp;&nbsp;&nbsp; <a href="#Engine">Engine</a>
   <br><a href="#Administration Subsystem">Administration Subsystem</a>
  +<br><a href="#Message Model Subsystem">Message Model Subsystem</a>
  +<br>&nbsp;&nbsp;&nbsp; <a href="#SOAP message model">SOAP Message
  +<br>&nbsp;&nbsp;&nbsp; <a href="#Message elements">Message Elements</a>
   <br><a href="#Sequence Diagrams">Interaction Diagrams</a>
   <br>&nbsp;&nbsp;&nbsp; <a href="#Client Interaction">Client Side
   <br><a href="#Open Issues">Open Issues</a>
  @@ -276,6 +279,42 @@
   artefacts they produce (a dotted arrow means "instantiates").
   <br><img SRC="wsddclasses.jpg">
  +<a NAME="Message Model Subsystem"></a>Message Model Subsystem</h2>
  +<a name="SOAP message model"></a><h3>SOAP Message Model</h3>
  +The XML syntax of a SOAP message is fairly simple.
  +A SOAP message consists of an <i>envelope</i> containing:
  +<li>an optional <i>header</i> containing zero or more <i>header
  +(sometimes ambiguously referred to as <i>headers</i>),</li>
  +<li>a <i>body</i> containing zero or more <i>body entries</i>,
  +<li>zero or more additional, non-standard elements.</li>
  +The only body entry defined by SOAP is a <i>SOAP fault</i> which is
  +used for reporting errors.
  +Some of the XML elements of a SOAP message define namespaces, each in terms
  +of a URI and a local name, and encoding styles, a standard one of which
  +is defined by SOAP.
  +Header entries may be tagged with the following optional SOAP attributes:
  +<li><i>actor</i> which specifies the intended recipient of the header
  +entry in terms of a URI, and</li>
  +<li><i>mustUnderstand</i> which specifies whether or not the intended
  +recipient of the header entry is required to process the header
  +So the SOAP message model looks like this:
  +<br><img SRC="soapmessagemodel.jpg">
  +<a name="Message elements"></a><h3>Message Elements</h3>
  +The classes which represent SOAP messages form a hierarchy based on
  +the MessageElement class which takes care of namespaces and encodings.
  +The SOAPHeader class looks after the actor and mustUnderstand attributes.
  +<br><img SRC="messagemodelclasses.jpg">
   <a NAME="Sequence Diagrams"></a>Interaction Diagrams</h2>
  @@ -305,8 +344,8 @@
   type and associated classes.</li>
  -What classes are included in the "encoding" and "message model" subsystems?
  -Are these subsystems independent of the other subsystems which depend on
  +What classes are included in the "encoding" subsystem?
  +Are the encoding and message model subsystems independent of the other subsystems which
depend on
   "message flow"?</li>
  1.1                  xml-axis/java/docs/messagemodelclasses.jpg
  	<<Binary file>>
  1.1                  xml-axis/java/docs/soapmessagemodel.jpg
  	<<Binary file>>

View raw message