jmsnell 2002/11/04 23:43:26
Modified: java/docs reading.html architecture-guide.html
user-guide.html index.html reference.html
integration-guide.html developers-guide.html
Added: java/docs/images typemappingclasses.jpg SAXhandlers.jpg
clientinteraction.jpg axis.jpg serclasses.jpg
typemappingregistryclasses.jpg subsystems.jpg
clientobjects.jpg stcengine.jpg messagecontext.jpg
pivots2.jpg messagemodelclasses.jpg
targetedchainclasses.jpg ClientMessagePath.jpg
engineconfig.jpg tcpmon2.jpg pivots.jpg
SAXHandlerClasses.jpg serfactoryclasses.jpg
chainclasses.jpg messagetree.jpg wsddclasses.jpg
ServerMessagePath.jpg soapmessagemodel.jpg
engineclasses.jpg tcpmon1.jpg
Removed: java/docs messagemodelclasses.jpg serclasses.jpg
typemappingregistryclasses.jpg
typemappingclasses.jpg tcpmon2.jpg engineconfig.jpg
subsystems.jpg ClientMessagePath.jpg
chainclasses.jpg stcengine.jpg messagecontext.jpg
tcpmon1.jpg SAXHandlerClasses.jpg
soapmessagemodel.jpg axis.jpg clientobjects.jpg
serfactoryclasses.jpg ServerMessagePath.jpg
targetedchainclasses.jpg pivots.jpg
clientinteraction.jpg messagetree.jpg
wsddclasses.jpg pivots2.jpg engineclasses.jpg
SAXhandlers.jpg
Log:
Minor reorg. Moving all jpegs under the images directory
Revision Changes Path
1.1 xml-axis/java/docs/images/typemappingclasses.jpg
<<Binary file>>
1.1 xml-axis/java/docs/images/SAXhandlers.jpg
<<Binary file>>
1.1 xml-axis/java/docs/images/clientinteraction.jpg
<<Binary file>>
1.1 xml-axis/java/docs/images/axis.jpg
<<Binary file>>
1.1 xml-axis/java/docs/images/serclasses.jpg
<<Binary file>>
1.1 xml-axis/java/docs/images/typemappingregistryclasses.jpg
<<Binary file>>
1.1 xml-axis/java/docs/images/subsystems.jpg
<<Binary file>>
1.1 xml-axis/java/docs/images/clientobjects.jpg
<<Binary file>>
1.1 xml-axis/java/docs/images/stcengine.jpg
<<Binary file>>
1.1 xml-axis/java/docs/images/messagecontext.jpg
<<Binary file>>
1.1 xml-axis/java/docs/images/pivots2.jpg
<<Binary file>>
1.1 xml-axis/java/docs/images/messagemodelclasses.jpg
<<Binary file>>
1.1 xml-axis/java/docs/images/targetedchainclasses.jpg
<<Binary file>>
1.1 xml-axis/java/docs/images/ClientMessagePath.jpg
<<Binary file>>
1.1 xml-axis/java/docs/images/engineconfig.jpg
<<Binary file>>
1.1 xml-axis/java/docs/images/tcpmon2.jpg
<<Binary file>>
1.1 xml-axis/java/docs/images/pivots.jpg
<<Binary file>>
1.1 xml-axis/java/docs/images/SAXHandlerClasses.jpg
<<Binary file>>
1.1 xml-axis/java/docs/images/serfactoryclasses.jpg
<<Binary file>>
1.1 xml-axis/java/docs/images/chainclasses.jpg
<<Binary file>>
1.1 xml-axis/java/docs/images/messagetree.jpg
<<Binary file>>
1.1 xml-axis/java/docs/images/wsddclasses.jpg
<<Binary file>>
1.1 xml-axis/java/docs/images/ServerMessagePath.jpg
<<Binary file>>
1.1 xml-axis/java/docs/images/soapmessagemodel.jpg
<<Binary file>>
1.1 xml-axis/java/docs/images/engineclasses.jpg
<<Binary file>>
1.1 xml-axis/java/docs/images/tcpmon1.jpg
<<Binary file>>
1.9 +1 -1 xml-axis/java/docs/reading.html
Index: reading.html
===================================================================
RCS file: /home/cvs/xml-axis/java/docs/reading.html,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- reading.html 1 Nov 2002 19:21:31 -0000 1.8
+++ reading.html 5 Nov 2002 07:43:24 -0000 1.9
@@ -19,7 +19,7 @@
<center>
<h1>
-<img SRC="axis.jpg" height=96 width=176></h1></center>
+<img SRC="images/axis.jpg" height=96 width=176></h1></center>
<h1>Recommended Reading</h1>
1.18 +24 -24 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.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- architecture-guide.html 26 Sep 2002 14:02:22 -0000 1.17
+++ architecture-guide.html 5 Nov 2002 07:43:25 -0000 1.18
@@ -18,7 +18,7 @@
<center>
<h1>
-<img SRC="axis.jpg" height=96 width=176></h1></center>
+<img SRC="images/axis.jpg" height=96 width=176></h1></center>
<h1>
Axis Architecture Guide</h1>
@@ -86,7 +86,7 @@
cylinders represent Handlers and the larger, enclosing cylinders represent
<b>Chains</b> (ordered collections of Handlers which will be described
shortly).
-<br><img SRC="ServerMessagePath.jpg" VSPACE=30 height=282 width=602>
+<br><img SRC="images/ServerMessagePath.jpg" VSPACE=30 height=282 width=602>
<br>A message arrives (in some protocol-specific manner) at a Transport
Listener. In this case, let's assume the Listener is a HTTP servlet. It's
the Listener's job to package the protocol-specific data into a <b>Message</b>
@@ -128,7 +128,7 @@
The Message Path on the Client</h3>
The Message Path on the client side is similar to that on the server side,
except the order of scoping is reversed, as shown below.
-<br><img SRC="ClientMessagePath.jpg" VSPACE=30 height=281 width=592>
+<br><img SRC="images/ClientMessagePath.jpg" VSPACE=30 height=281 width=592>
<br>The <b>service</b> Handler, if any, is called first - on the client
side, there is no "provider" since the service is being provided by a remote
node, but there is still the possibility of request and response Chains.
@@ -154,7 +154,7 @@
independent, although not necessary mutually exclusive, alternatives. For
example, the HTTP, SMTP, and JMS transports are independent of each other but
may be used together.
-<p><img SRC="subsystems.jpg">
+<p><img SRC="images/subsystems.jpg">
<p>
In fact, the Axis source code is not as cleanly separated into subsystems
as the above diagram might imply. Some subsystems are spread over
@@ -177,7 +177,7 @@
comprises three Chains: transport, global, and service. The following diagram
shows two sequences of handlers: the client-side sequence on the left and
the server-side sequence on the right.
-<br><img SRC="pivots.jpg" height=240 width=403>
+<br><img SRC="images/pivots.jpg" height=240 width=403>
<p>A web service does not necessarily send a response message to each request
message, although many do. However, response Handlers are still useful
in the message path even when there isn't a response message, e.g. to stop
@@ -185,7 +185,7 @@
<p>A Chain is a composite Handler, i.e. it aggregates a collection of Handlers
as well as implementing the Handler interface as shown in the following
UML diagram:
-<br><img SRC="chainclasses.jpg">
+<br><img SRC="images/chainclasses.jpg">
<p>A Chain also has similarities to the Chain of Responsibility design pattern
in which a request flows along a sequence of Handlers until it is processed.
Although an Axis Chain may process a request in stages over a succession of
@@ -218,7 +218,7 @@
following class diagram shows how Targeted Chains relate to Chains. Note
that a Targeted Chain is an aggregation of Handlers by virtue of extending
the Chain interface which is an aggregation of Handlers.
-<p><img SRC="targetedchainclasses.jpg">
+<p><img SRC="images/targetedchainclasses.jpg">
<p>A service is a special kind of Targeted Chain in which the pivot Handler
is known as a "provider".
<h4>
@@ -236,7 +236,7 @@
context may be associated with a request Message and/or a response Message.
Each Message has a SOAPPart and an Attachments object, both of which implement
the Part interface.
-<br><img SRC="messagecontext.jpg">
+<br><img SRC="images/messagecontext.jpg">
<br>The typing of Message Contexts needs to be carefully considered in
relation to the Axis architecture. Since a Message Context appears on the
Handler interface, it should not be tied to or biassed in favour of
@@ -249,7 +249,7 @@
drives the client side handler chains and AxisServer drives the server
side handler chains. The relationships between these classes is fairly
simple:
-<br><img SRC="engineclasses.jpg">
+<br><img SRC="images/engineclasses.jpg">
<h4>Engine Configuration</h3>
The EngineConfiguration interface is the means of configuring the Handler
factories and global options of an engine instance. An instance of a
@@ -274,7 +274,7 @@
deployment descriptor which is understood by the WSDDDeployment class.
SimpleProvider, on the other hand, enables an engine to be configured
dynamically.
-<br><img SRC="engineconfig.jpg">
+<br><img SRC="images/engineconfig.jpg">
<h3>
WSDD-Based Administration</h3>
WSDD is an XML grammer for deployment descriptors which are used to
@@ -288,7 +288,7 @@
for runtime artefacts.
The following diagram shows the classes and the types of runtime
artefacts they produce (a dotted arrow means "instantiates").
-<br><img SRC="wsddclasses.jpg">
+<br><img SRC="images/wsddclasses.jpg">
<h2><a NAME="Message Model Subsystem"></a>Message Model Subsystem</h2>
<h3><a name="SOAP message model"></a>SOAP Message Model</h3>
The XML syntax of a SOAP message is fairly simple.
@@ -316,18 +316,18 @@
</ul>
<p>
So the SOAP message model looks like this:
-<br><img SRC="soapmessagemodel.jpg">
+<br><img SRC="images/soapmessagemodel.jpg">
<h3><a name="Message elements"></a>Message Elements</h3>
The classes which represent SOAP messages form a class hierarchy based on
the MessageElement class which takes care of namespaces and encodings.
The SOAPHeaderElement class looks after the actor and mustUnderstand
attributes.
-<br><img SRC="messagemodelclasses.jpg">
+<br><img SRC="images/messagemodelclasses.jpg">
During deserialization, a parse tree is constructed consisting of instances
of the above classes in parent-child relationships as shown below.
-<br><img SRC="messagetree.jpg">
+<br><img SRC="images/messagetree.jpg">
<h3><a name="D13n"></a>Deserialization</h3>
The class mainly responsible for XML parsing, i.e. deserialization, is
DeserializationContextImpl ('DCI') which inherits most of its methods from the
@@ -345,9 +345,9 @@
MessageElements all have an output() method which lets them write out their
contents.
<p>The SAX handlers form a class hierarchy:
-<br><img SRC="SAXHandlerClasses.jpg">
+<br><img SRC="images/SAXHandlerClasses.jpg">
<p>and stack up as shown in the following diagram:
-<br><img SRC="SAXhandlers.jpg">
+<br><img SRC="images/SAXhandlers.jpg">
<p>Initially, the SAX handler stack just contains an instance of
EnvelopeHandler which represents the fact that parsing of the SOAP envelope
has not yet started.
@@ -379,7 +379,7 @@
and decoding (or 'deserializing') XML into Java objects and primitives.
The basic classes that implement these steps are <i>serializers</i>
and <i>deserializers</i>.
-<br><img SRC="serclasses.jpg">
+<br><img SRC="images/serclasses.jpg">
<p>
Particular serializers and deserializers are written to support
a specific XML processing mechanism such as DOM or SAX.
@@ -387,7 +387,7 @@
are introduced to construct serializers and deserializers
for a XML processing mechanism which is specified
as a parameter.
-<br><img SRC="serfactoryclasses.jpg">
+<br><img SRC="images/serfactoryclasses.jpg">
<p>
As is apparent from the above class diagrams, each pair of Java
type and XML data type which needs encoding
@@ -400,7 +400,7 @@
The type mapping class hierarchy is shown below. Notice how
the default type mapping instantiates the various serializer and
deserialiser factories.
-<br><img SRC="typemappingclasses.jpg">
+<br><img SRC="images/typemappingclasses.jpg">
<p>
There is one final level of indirection. How do we know
which type mapping to use for a particular message?
@@ -408,7 +408,7 @@
the message. A <i>type mapping registry</i> maintains
a map from encoding name (URI) to type mapping.
Note that the XML data type QNames are defined by the encoding.
-<br><img SRC="typemappingclasses.jpg">
+<br><img SRC="images/typemappingclasses.jpg">
<p>
So, in summary, to encode a Java object or primitive data value
to a XML datatype or to decode the latter to the former,
@@ -451,7 +451,7 @@
The client side Axis processing constructs a Call object with associated
Service, MessageContext, and request Message as shown below before invoking
the AxisClient engine.
-<p><img SRC="clientobjects.jpg" height=120 width=349>
+<p><img SRC="images/clientobjects.jpg" height=120 width=349>
<br>An instance of Service and its related AxisClient instance are
created before the Call object. The Call object is then created by invoking
the Service.createCall <i>factory method</i>. Call.setOperation creates
@@ -460,7 +460,7 @@
request Message, drives AxisClient.invoke, and processes the resultant
MessageContext. This significant method calls in this sequence are shown
in the following interaction diagram.
-<br><img SRC="clientinteraction.jpg" height=503 width=731>
+<br><img SRC="images/clientinteraction.jpg" height=503 width=731>
<h2>
<a NAME="Pluggable-Component Discovery"></a>Pluggable-Component Discovery</h2>
@@ -513,7 +513,7 @@
service pivot Handler (which is itself a Targeted Chain as we have just
described). Such an Axis Engine architecture is shown in the diagram below.</li>
-<br><img SRC="stcengine.jpg" height=312 width=667>
+<br><img SRC="images/stcengine.jpg" height=312 width=667>
<li>
WSDDService.faultFlows is initialised to an empty Vector and there is no
way of adding a fault flow to it. Is this dead code or is something else
@@ -538,7 +538,7 @@
Handler sequence invoking a server-side Handler sequence. We need to consider
how the semantics of this combined sequence compares with the sequence
formed by omitting the transport-related Handlers.
-<br><img SRC="pivots2.jpg" height=413 width=658>
+<br><img SRC="images/pivots2.jpg" height=413 width=658>
</ol>
</body>
1.77 +3 -3 xml-axis/java/docs/user-guide.html
Index: user-guide.html
===================================================================
RCS file: /home/cvs/xml-axis/java/docs/user-guide.html,v
retrieving revision 1.76
retrieving revision 1.77
diff -u -r1.76 -r1.77
--- user-guide.html 28 Oct 2002 14:42:17 -0000 1.76
+++ user-guide.html 5 Nov 2002 07:43:25 -0000 1.77
@@ -18,7 +18,7 @@
<center>
<h1>
-<img SRC="axis.jpg" height=96 width=176></h1></center>
+<img SRC="images/axis.jpg" height=96 width=176></h1></center>
<h1>
Axis User's Guide</h1>
@@ -1572,7 +1572,7 @@
Without any of the optional arguments, you will get a gui which looks like
this:
<center>
-<p><img SRC="tcpmon1.jpg" height=599 width=599></center>
+<p><img SRC="images/tcpmon1.jpg" height=599 width=599></center>
<p>To use the program, you should select a local port which tcpmon will
monitor for incoming connections, a target host where it will forward such
@@ -1581,7 +1581,7 @@
in the window for your new tunneled connection. Looking at that panel,
you'll see something like this:
<center>
-<p><img SRC="tcpmon2.jpg" height=600 width=599></center>
+<p><img SRC="images/tcpmon2.jpg" height=600 width=599></center>
<p>Now each time a SOAP connection is made to the local port, you will
see the request appear in the "Request" panel, and the response from the
1.7 +1 -1 xml-axis/java/docs/index.html
Index: index.html
===================================================================
RCS file: /home/cvs/xml-axis/java/docs/index.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- index.html 27 Aug 2002 22:47:21 -0000 1.6
+++ index.html 5 Nov 2002 07:43:25 -0000 1.7
@@ -17,7 +17,7 @@
<center>
<h1>
-<img SRC="axis.jpg" height=96 width=176></h1></center>
+<img SRC="images/axis.jpg" height=96 width=176></h1></center>
<h1>
Documentation</h1>
1.14 +1 -1 xml-axis/java/docs/reference.html
Index: reference.html
===================================================================
RCS file: /home/cvs/xml-axis/java/docs/reference.html,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- reference.html 17 Oct 2002 20:41:08 -0000 1.13
+++ reference.html 5 Nov 2002 07:43:25 -0000 1.14
@@ -16,7 +16,7 @@
</head>
<body bgcolor="#ffffff" text="#000000">
-<h1 align="center"><IMG height=96 src="axis.jpg" width=176></h1>
+<h1 align="center"><IMG height=96 src="images/axis.jpg" width=176></h1>
<h1>Axis Reference Guide</h1>
<p><i>1.0 Version</i></p>
<h3>Table of Contents</h3>
1.18 +1 -1 xml-axis/java/docs/integration-guide.html
Index: integration-guide.html
===================================================================
RCS file: /home/cvs/xml-axis/java/docs/integration-guide.html,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- integration-guide.html 10 Oct 2002 20:47:00 -0000 1.17
+++ integration-guide.html 5 Nov 2002 07:43:25 -0000 1.18
@@ -20,7 +20,7 @@
<center>
<h1>
-<img SRC="axis.jpg" height=96 width=176></h1></center>
+<img SRC="images/axis.jpg" height=96 width=176></h1></center>
<h1>
Axis System Integration Guide</h1>
1.30 +1 -1 xml-axis/java/docs/developers-guide.html
Index: developers-guide.html
===================================================================
RCS file: /home/cvs/xml-axis/java/docs/developers-guide.html,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -r1.29 -r1.30
--- developers-guide.html 29 Sep 2002 02:48:16 -0000 1.29
+++ developers-guide.html 5 Nov 2002 07:43:25 -0000 1.30
@@ -20,7 +20,7 @@
<center>
<h1>
-<img SRC="axis.jpg" height=96 width=176></h1></center>
+<img SRC="images/axis.jpg" height=96 width=176></h1></center>
<h1>
Axis Developer's Guide</h1>
