You are viewing a plain text version of this content. The canonical link for it is here.
Posted to axis-cvs@ws.apache.org by ch...@apache.org on 2006/01/19 17:25:06 UTC
svn commit: r370524 [3/11] - in /webservices/axis2/site: ./ 0_93/ 0_93/adb/
0_93/tools/idea-guide/ 0_94/ 0_94/adb/ 0_94/images/ 0_94/tools/idea/
modules/ modules/addressing/ modules/wss4j/ modules/wss4j/0_94/0.94/
multiproject/axis2-Samples/ multiproje...
Modified: webservices/axis2/site/0_94/Axis2ArchitectureGuide.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/site/0_94/Axis2ArchitectureGuide.html?rev=370524&r1=370523&r2=370524&view=diff
==============================================================================
--- webservices/axis2/site/0_94/Axis2ArchitectureGuide.html (original)
+++ webservices/axis2/site/0_94/Axis2ArchitectureGuide.html Thu Jan 19 08:22:01 2006
@@ -52,7 +52,7 @@
</li>
<li><a href="#bmDB">Data Binding</a>
<ul>
- <li><a href="#inegration">Integration with the code generation
+ <li><a href="#integration">Integration with the code generation
engine</a></li>
<li><p><a href="#serial">Serialization and De-Serialization</a></p>
</li>
@@ -63,24 +63,24 @@
</ul></div><div class="subsection"><a name="The_Big_Picture"></a><h3>The Big Picture</h3><p>Any architecture is a result of what that architecture should yield. The
success of an architecture should be evaluated based on the requirements
expected to be met by that architecture. Let us start our journey into Axis2
-by looking at the requirements.</p></div><div class="subsection"><a name="Requirement_of_Axis2"></a><h3>Requirement of Axis2</h3><p>In the SOAP terminology, a participant who is taking part in a Web Service
+by looking at the requirements.</p><p><a name="requirements"></a></p></div><div class="subsection"><a name="Requirement_of_Axis2"></a><h3>Requirement of Axis2</h3><p>In the SOAP terminology, a participant who is taking part in a Web Service
interaction is known as a SOAP Node. Delivery of a single SOAP Message is
defined based on two participants, SOAP Sender and SOAP Receiver. Each SOAP
Message is sent by SOAP Sender and received by SOAP Receiver. A single SOAP
delivery is the most basic unit that builds the Web Service interaction.</p><p>Each SOAP Node may be written in specific programming language, may it be
Java, C++, .NET or Perl, the Web Services allow them to inter operate. This
is possible because on the wire each Web Service interaction is done via
-SOAP, which is common to every SOAP Node.</p><p><img src="images/archi-guide/soap.gif" name="Graphic1" align="bottom" width="691" height="319" border="0" alt=""></img></p><p>Web Service middleware handles the complexity in SOAP messaging and lets
+SOAP, which is common to every SOAP Node.</p><p><img alt="" src="images/archi-guide/soap.gif" name="Graphic1" align="bottom" width="691" height="319" border="0"></img></p><p>Web Service middleware handles the complexity in SOAP messaging and lets
the users work with the programming language they are accustomed to. Axis2
allows java users to invoke Web Services using java representations, and
handles the SOAP messaging behind the curtain.</p><p>Axis2 handles SOAP processing along with numerous other tasks. This makes
the life of the Web Service developer a whole lot easier. Following are the
identified requirements:</p><ol>
- <li><style>Provide a framework to process the SOAP
- messages. The framework should be extensible and the users should be able
- to extend the SOAP processing per service or per operation basis.
- Furthermore it should be able to model different Message Exchange
- Patterns (MEPs) using the processing framework.</style></li>
+ <li>Provide a framework to process the SOAP messages. The framework should
+ be extensible and the users should be able to extend the SOAP processing
+ per service or per operation basis. Furthermore it should be able to
+ model different Message Exchange Patterns (MEPs) using the processing
+ framework.</li>
<li><p>Ability to deploy a Web Services (with or without WSDL)</p>
</li>
<li>Provide a Client API that can be used to invoke Web Services. This API
@@ -97,9 +97,9 @@
Axis2 architecture lays out some principals to preserve the uniformity. They
are as follows:
<ul>
- <li><p><style>Axis2 architecture separates the logic
- and the states. Code that does the processing is stateless inside Axis2.
- This allows code to be executed freely by parallel threads.</style></p>
+ <li><p>Axis2 architecture separates the logic and the states. Code that
+ does the processing is stateless inside Axis2. This allows code to be
+ executed freely by parallel threads.</p>
</li>
<li>All the information is kept in one information model allowing system to
be suspended and resumed.</li>
@@ -107,10 +107,10 @@
core modules which collectively make up the core architecture of Axis2, and
non-core modules that are layered on top of this core
modules/architecture.</p><p>Core Modules:</p><ul>
- <li><style><a href="#bmInfoMod">Information Model</a>-
- Axis2 defines a model to handle information and all states are kept in
- this model. The model has a hierarchy for the information. The system
- manages the life cycle of the objects in this hierarchy.</style></li>
+ <li><a href="#bmInfoMod">Information Model</a>- Axis2 defines a model to
+ handle information and all states are kept in this model. The model has a
+ hierarchy for the information. The system manages the life cycle of the
+ objects in this hierarchy.</li>
<li><p><a href="#bmXML">XML processing Model</a>- Handling the SOAP Message
is the most important and most complex task. The efficiency of this is
the single most important factor that decides the performance. It makes
@@ -149,16 +149,16 @@
it to make it more convenient to the users by encapsulating the infoset
layer and providing a programming language specific interface.</p>
</li>
-</ul><map name="Graphic2Map">
- <area shape="rect" coords="123,31,222,97" href="#bmInfoMod"></area>
- <area shape="rect" coords="239,62,319,134" href="#bmXML"></area>
- <area shape="rect" coords="127,112,218,177" href="#bmSOAPPM"></area>
- <area shape="rect" coords="12,39,89,95" href="#bmDeployment"></area>
- <area shape="rect" coords="0,108,94,156" href="#bmWSDL"></area>
- <area shape="rect" coords="350,31,426,86" href="#bmClientAPI"></area>
- <area shape="rect" coords="350,114,421,164" href="#bmTransports"></area>
-</map></p><p><img src="images/archi-guide/all.png" name="Graphic2" width="426" height="189" border="0" align="bottom" usemap="#Graphic2Map" alt=""></img></p></div><div class="subsection"><a name="Information_Model"></a><h3>Information Model</h3><p>Information Model has two main hierarchies-Contexts and Descriptions. This
-model is described in UML notations below.</p><p><img src="images/archi-guide/contexts.png" name="Graphic3" align="bottom" width="400" height="443" border="0" alt=""></img></p><p>( A ----<> B says, B has 1 or more objects of A. A------>B says,
+</ul><map name="Graphic2Map" id="g2m">
+ <area shape="rect" coords="123,31,222,97" href="#bmInfoMod" alt=""></area>
+ <area shape="rect" coords="239,62,319,134" href="#bmXML" alt=""></area>
+ <area shape="rect" coords="127,112,218,177" href="#bmSOAPPM" alt=""></area>
+ <area shape="rect" coords="12,39,89,95" href="#bmDeployment" alt=""></area>
+ <area shape="rect" coords="0,108,94,156" href="#bmWSDL" alt=""></area>
+ <area shape="rect" coords="350,31,426,86" href="#bmClientAPI" alt=""></area>
+ <area shape="rect" coords="350,114,421,164" href="#bmTransports" alt=""></area>
+</map></p><p><img src="images/archi-guide/all.png" name="Graphic2" width="426" alt="" height="189" border="0" align="bottom" usemap="#Graphic2Map"></img></p></div><div class="subsection"><a name="Information_Model"></a><h3>Information Model</h3><p>Information Model has two main hierarchies-Contexts and Descriptions. This
+model is described in UML notations below.</p><p><img src="images/archi-guide/contexts.png" name="Graphic3" align="bottom" alt="" width="400" height="443" border="0"></img></p><p>( A ----<> B says, B has 1 or more objects of A. A------>B says,
the given relationship holds between A and B.)</p><p>The two hierarchies are connected as shown in the above figure. The
Description hierarchy represents the static data. This data may be loaded
from a configuration file that exists throughout the lifetime of Axis2. For
@@ -177,8 +177,8 @@
does not exist. Yet in the final analysis developers believe that the
flexibility would serve better in this instant.</p><table class="bodyTable"><col width="112"></col><col width="371"></col><col width="103"></col><col width="336"></col><tbody>
<tr class="b"><td width="112"><p>Configuration Context</p>
- </td><td width="371"><p>Holds the run time status. A deep copy of
- this would essentially make a copy of Axis2.</p>
+ </td><td width="371"><p>Holds the run time status. A deep copy of this would
+ essentially make a copy of Axis2.</p>
</td><td width="103"><p>Axis Configuration</p>
</td><td width="336"><p>Holds all global configurations. Transports, global
modules, parameters and Services etc.</p>
@@ -207,14 +207,14 @@
</td><td width="103"><p>AxisOperation</p>
</td><td width="336"><p>Holds the operation level configurations</p>
</td></tr>
- <tr class="b"><td width="112"><p><a name="messageContext"></a>Message Context</p>
+ <tr class="b"><td width="112"><p>Message Context</p>
</td><td width="371"><p>Holds all the information about the Message
currently being executed.</p>
</td><td width="103"><p>AxisMessage</p>
</td><td width="336"><p>Do not hold any information as yet, but can be used
as a future extension point.</p>
</td></tr>
- </tbody></table></div><div class="subsection"><a name="XML_Processing_Model"></a><h3>XML Processing Model</h3><p>Please refer to the <a href="OMTutorial.html">OM Tutorial</a></p></div><div class="subsection"><a name="SOAP_Processing_Model"></a><h3>SOAP Processing Model</h3><p><img src="images/archi-guide/soap-processing.gif" name="Graphic4" align="bottom" width="755" height="348" border="0" alt=""></img></p><p>The architecture identified two basic actions a SOAP processor should
+ </tbody></table><p><a name="bmXML"></a></p></div><div class="subsection"><a name="XML_Processing_Model"></a><h3>XML Processing Model</h3><p>Please refer to the <a href="OMTutorial.html">OM Tutorial</a></p></div><div class="subsection"><a name="SOAP_Processing_Model"></a><h3>SOAP Processing Model</h3><p><img src="images/archi-guide/soap-processing.gif" name="Graphic4" alt="" align="bottom" width="755" height="348" border="0"></img></p><p>The architecture identified two basic actions a SOAP processor should
perform, sending and receiving SOAP messages. The architecture provides two
Pipes ('Flows'), to perform these two basic actions. Axis Engine or the
driver of Axis2 defines two methods send() and receive() to implement these
@@ -231,8 +231,9 @@
Transport Sender that sends the SOAP message to the target endpoint. The SOAP
message is received by a Transport Receiver at the target endpoint, which
reads the SOAP message and starts the <i>In Pipe</i>. The <em>In Pipe</em>
-consists of handlers and ends with the <a href="#mr">Message Receiver</a>,
-which consumes the SOAP message.</p><p>Above explained processing happens for each and every SOAP message
+consists of handlers and ends with the</p><p><a href="#mr">Message Receiver</a>, which consumes the SOAP message.
+
+</p><p>Above explained processing happens for each and every SOAP message
exchanged. After processing one message Axis2 may decide to create other SOAP
messages, in which case more complex message patterns emerge. However Axis2
always view the SOAP message in terms of processing a single message. The
@@ -243,75 +244,62 @@
always runs inside a phase, and the phase provides a mechanism to specify the
ordering of handlers. Both Pipes have built in phases, and both define the
areas for 'User Phases' which can be defined by the user.</p><p>Following figure shows the two pipes with their pre-defined phases &
-user-defined phases. User-defined phases fit in to the User Phases.</p><p><img src="images/archi-guide/phases.png" name="Graphic5" align="bottom" width="525" height="226" border="0" alt=""></img></p></div><div class="subsection"><a name="Axis2_Default_Processing_Model"></a><h3>Axis2 Default Processing Model</h3><p>Axis2 has some inbuilt handlers that run in inbuilt phases and they create
+user-defined phases. User-defined phases fit in to the User Phases.</p><p><img src="images/archi-guide/phases.png" name="Graphic5" align="bottom" alt="" width="525" height="226" border="0"></img></p></div><div class="subsection"><a name="Axis2_Default_Processing_Model"></a><h3>Axis2 Default Processing Model</h3><p>Axis2 has some inbuilt handlers that run in inbuilt phases and they create
the default configuration for the Axis2. We will be looking more in to how to
extend the default processing Model in the next section.</p><p>
There are four special handlers defined in Axis2.
<ol>
- <li><style>Dispatchers - Finds the service and the
- operation the SOAP message is directed to. Dispatchers always run on the
- <em>In-Pipe</em> and inside the Dispatch phase. The in-built dispatchers
- dispatch to a particular operation depending on various conditions like
- WS-Addressing information, URI information, SOAP action information,
- etc.,</style></li>
- <li><p style="margin-bottom: 0in"><a name="mr"></a>Message Receiver -
- Consume the SOAP Message and run on the Message Processing phase in the
- inflow</p>
- </li>
- <li><p>Transport Sender - Send the SOAP message to the SOAP endpoint the
- message is destined to. Always runs on the</p>
- </li>
+ <li>Dispatchers - Finds the service and the operation the SOAP message is
+ directed to. Dispatchers always run on the <em>In-Pipe</em> and inside
+ the Dispatch phase. The in-built dispatchers dispatch to a particular
+ operation depending on various conditions like WS-Addressing information,
+ URI information, SOAP action information, etc.,</li>
+ <ul>
+ <li><a name="mr">Message Receiver - Consume the SOAP Message and run on
+ the Message Processing phase in the inflow</a></li>
+ <li><p>Transport Sender - Send the SOAP message to the SOAP endpoint the
+ message is destined to. Always runs on the</p>
+ </li>
+ </ul>
</ol></p></div><div class="subsection"><a name="Processing_an_Incoming_SOAP_Message"></a><h3>Processing an Incoming SOAP Message</h3><p>Incoming SOAP Message is always received by a Transport Receiver waiting
for the SOAP Messages. Once the SOAP Message arrives the transport Headers
-are parsed and a <a href="#messageContext">Message Context</a> is created for
-the incoming SOAP Message. Then the <i>In Pipe</i> is executed with the
-Message Context.</p><p>Let us see what happens at each phase of the execution. This process may
+are parsed and a</p><p><a href="#messageContext">Message Context</a> is created for the incoming
+SOAP Message. Then the <i>In Pipe</i> is executed with the Message Context.
+
+</p><p>Let us see what happens at each phase of the execution. This process may
happen either in the server or in the Client. There is a special case of
using the Two-Way transport where the first four phases of the In-Phase most
likely does nothing.</p><ol>
- <li><p style="margin-bottom: 0in">Transport Phase - The handlers in the
- transport phase are taken from the transport configuration associated and
- executed according to the phase rules.</p>
- </li>
- <li><p style="margin-bottom: 0in">Pre-Dispatch Phase- handlers in this
- phase will be engaged globally since the service is not found yet.
- </p>
- </li>
- <li><p style="margin-bottom: 0in">Dispatch Phase - The Dispatchers run in
- this phase and find the Service if the service is not found already.
- <br></br> The post condition of the dispatch phase work as follows;
- That checks weather the service is found or not. If the service has not been found by
+ <li>Transport Phase - The handlers in the transport phase are taken from
+ the transport configuration associated and executed according to the
+ phase rules.</li>
+ <li>Pre-Dispatch Phase- handlers in this phase will be engaged globally
+ since the service is not found yet.</li>
+ <li>Dispatch Phase - The Dispatchers run in this phase and find the Service
+ if the service is not found already. <br></br>
+ The post condition of the dispatch phase work as follows; That checks
+ weather the service is found or not. If the service has not been found by
this point the execution will halt and send a "service not found
- error".</p>
-
- </li>
- <li><p style="margin-bottom: 0in">User Defined Phases - Users are allowed
- to engage their custom handlers here.</p>
- </li>
- <li><p style="margin-bottom: 0in">Message Validation Phase - Once the user
- level execution has taken place this phase validates whether SOAP Message
- Processing has taken place correctly.</p>
- </li>
+ error".</li>
+ <li>User Defined Phases - Users are allowed to engage their custom handlers
+ here.</li>
+ <li>Message Validation Phase - Once the user level execution has taken
+ place this phase validates whether SOAP Message Processing has taken
+ place correctly.</li>
<li><p>Message Processing Phase - The Business logic of the SOAP message is
executed here. A <a href="#mr">Message Receiver</a> is registered with
each Operation. This Message receiver (associated to the particular
operation) will executed as the last Handler of this phase.</p>
</li>
-</ol><p>There may be other handlers in any of these phases. Users may use
-custom handlers to override the mechanics in each of these phases.
-</p></div><div class="subsection"><a name="Processing_of_the_Outgoing_Message"></a><h3>Processing of the Outgoing Message</h3><p><em>Out Pipe</em> is simpler because the service and operation to dispatch
+</ol><p>There may be other handlers in any of these phases. Users may use custom
+handlers to override the mechanics in each of these phases.</p></div><div class="subsection"><a name="Processing_of_the_Outgoing_Message"></a><h3>Processing of the Outgoing Message</h3><p><em>Out Pipe</em> is simpler because the service and operation to dispatch
is known by the time the pipe is executed. The <em>Out Pipe</em> may be
-initiated by the <a href="#mr">Message Receiver</a> or the Client API
-implementation.</p><p>
-Phases of the <em>Out Pipe</em> are described below:
+initiated by the</p><p><a href="#mr">Message Receiver</a> or the Client API implementation.Phases of
+the <em>Out Pipe</em> are described below:
<ol>
- <li><p style="margin-bottom: 0in">Message Initialize Phase - Fist phase of
- the <em>Out Pipe</em>. Serves as the placeholder for the custom
- handlers</p>
- </li>
- <li><p style="margin-bottom: 0in">User Phases - This executes handlers in
- user defined phases</p>
- </li>
+ <li>Message Initialize Phase - Fist phase of the <em>Out Pipe</em>. Serves
+ as the placeholder for the custom handlers</li>
+ <li>User Phases - This executes handlers in user defined phases</li>
<li><p>Transports Phase - Execute any transport handlers taken from the
associated transport configuration. The last handler would be a transport
Sender which would send the SOAP message to the target end point.</p>
@@ -323,18 +311,15 @@
of handlers & phases is to allow easier modification of the processing
order. The notion of phases makes it easier to place handlers in between
other handlers enabling this modification on the default processing behavior.
-SOAP Processing Model can be extended with handler or Modules.</p></div><div class="subsection"><a name="Extending_the_SOAP_Processing_Model_with_Handlers"></a><h3>Extending the SOAP Processing Model with Handlers</h3><p>
+SOAP Processing Model can be extended with handler or Modules.</p><p><a name="extendingwithhandlers"></a></p></div><div class="subsection"><a name="Extending_the_SOAP_Processing_Model_with_Handlers"></a><h3>Extending the SOAP Processing Model with Handlers</h3><p>
The handlers can specify the phase they need to be placed in. Furthermore
they can specify their location inside a phase by providing phase rules.
Phase rules will place a handler
<ol>
- <li><style>as the first handler in a phase.</style></li>
- <li><p style="margin-bottom: 0in">or as the last handler in a phase.</p>
- </li>
- <li><p style="margin-bottom: 0in">or before a given handler</p>
- </li>
- <li><p style="margin-bottom: 0in">or after a given handler</p>
- </li>
+ <li>as the first handler in a phase.</li>
+ <li>or as the last handler in a phase.</li>
+ <li>or before a given handler</li>
+ <li>or after a given handler</li>
</ol></p></div><div class="subsection"><a name="Extending_the_SOAP_Processing_Model_with_Modules"></a><h3>Extending the SOAP Processing Model with Modules</h3><p>Axis2 defines an entity called a 'module' that can introduce handlers and
web service operations. A Module in terms of Axis2 usually acts as a
convenient packaging that include a set of handlers and an associated
@@ -354,28 +339,20 @@
that service.</p><p>A service, operations or the system may engage a module. Once the module
is engaged the handlers and the operations defined in the module are added to
the entity that engage them.</p><p>Modules can not be added while the Axis2 engine is running, but they will
-be available once the system is restarted.</p></div><div class="subsection"><a name="Deployment"></a><h3>Deployment</h3><p>The Deployment Model provides a concrete mechanism to configure Axis2.
+be available once the system is restarted.</p><p><a name="bmDeployment"></a></p></div><div class="subsection"><a name="Deployment"></a><h3>Deployment</h3><p>The Deployment Model provides a concrete mechanism to configure Axis2.
This model has three entities that provide the configuration.</p></div><div class="subsection"><a name="The__file"></a><h3>The file</h3><p>This file holds the global configuration for the client and server, and
provide following information:</p><ol>
- <li><p style="margin-bottom: 0in">The global parameters</p>
- </li>
- <li><p style="margin-bottom: 0in">Registered transports in and transport
- outs</p>
- </li>
- <li><p style="margin-bottom: 0in">User defined phase names</p>
- </li>
- <li><p style="margin-bottom: 0in">Modules that are engaged globally (to all
- services)</p>
- </li>
+ <li>The global parameters</li>
+ <li>Registered transports in and transport outs</li>
+ <li>User defined phase names</li>
+ <li>Modules that are engaged globally (to all services)</li>
<li><p>Globally defined <a href="#mr">Message Receivers</a></p>
</li>
-</ol></div><div class="subsection"><a name="Service_Archive"></a><h3>Service Archive</h3><p>Service archive must have a <em>META-INF/services.xml</em> file and may
+</ol><p><a name="servicearchive"></a></p></div><div class="subsection"><a name="Service_Archive"></a><h3>Service Archive</h3><p>Service archive must have a <em>META-INF/services.xml</em> file and may
contain the dependent classes. The <em>services.xml</em> file has following
information.</p><ol>
- <li><p style="margin-bottom: 0in">Service level parameters</p>
- </li>
- <li><p style="margin-bottom: 0in">Modules that are engaged Service level</p>
- </li>
+ <li>Service level parameters</li>
+ <li>Modules that are engaged Service level</li>
<li><p>Service Specific <a href="#mr">Message Receivers</a></p>
</li>
<li><p>Operations inside the Service</p>
@@ -390,38 +367,29 @@
top of the Axis Configurations and then Axis2 is ready to send or receive the
SOAP Message. Hot deployment is only allowed for the service, in which case a
thread will check the repository repeatedly, and then add the service
-corresponding to the new found service archives to the repository.</p></div><div class="subsection"><a name="Client_API"></a><h3>Client API</h3><p>There are three parameters that decide the nature of the Web Service
+corresponding to the new found service archives to the repository.</p><p><a name="bmClientAPI"></a></p></div><div class="subsection"><a name="Client_API"></a><h3>Client API</h3><p>There are three parameters that decide the nature of the Web Service
interaction.</p><ol>
- <li><p style="margin-bottom: 0in">Message Exchange Pattern (MEP)</p>
- </li>
- <li><p style="margin-bottom: 0in">The Behavior of the transport, whether
- it's One-Way or Two-Way</p>
- </li>
- <li><p style="margin-bottom: 0in">Synchronous/ Asynchronous behavior of the
- Client API</p>
- </li>
+ <li>Message Exchange Pattern (MEP)</li>
+ <li>The Behavior of the transport, whether it's One-Way or Two-Way</li>
+ <li>Synchronous/ Asynchronous behavior of the Client API</li>
</ol><p>Variations of the three parameters can result in indefinite number of
scenarios, even though Axis2 is built on a core that support any messaging
interaction, the developers were compelled to support only two most widely
used Message Exchange Patterns (MEPs).</p><p>Two supported transports are One-Way and the Request-Response scenarios in
the Client API. The implementation is based on a class called
<code>ServiceClient</code> and there are extensions for each MEP that Axis2
-Client API supports.</p></div><div class="subsection"><a name="One_Way_Messaging_Support"></a><h3>One Way Messaging Support</h3><p>The One-Way support is provided by the <code>fireAndForget</code> which provide by
- <code>ServiceClient</code> that provides a much simpler interface for the user.
-The Axis2 supports HTTP/SMTP and TCP transports. In the case of the HTTP transport
- the return channel is not used and the HTTP 202 OK is returned in the return Channel.</p></div><div class="subsection"><a name="Request_Response_Messaging_Support"></a><h3>Request Response Messaging Support</h3><p>The Request-Response support is provided by the
-<code>sendReceive()</code> method in ServiceClient ,that provides a much simpler interface for the user. The
-Client API has four ways to configure a given Message Exchange</p><ol>
- <li><p style="margin-bottom: 0in">Blocking or Non-Blocking nature - this
- can be decided by using <code>sendReceive()</code> or
- <code>sendReceiveNonBlocking()</code> methods</p>
- </li>
- <li><p style="margin-bottom: 0in">Sender transport - transport used to send
- the SOAP Message</p>
- </li>
- <li><p style="margin-bottom: 0in">Listener transport - transport the
- Response is received</p>
- </li>
+Client API supports.</p></div><div class="subsection"><a name="One_Way_Messaging_Support"></a><h3>One Way Messaging Support</h3><p>The One-Way support is provided by the <code>fireAndForget</code> which
+provide by <code>ServiceClient</code> that provides a much simpler interface
+for the user. The Axis2 supports HTTP/SMTP and TCP transports. In the case of
+the HTTP transport the return channel is not used and the HTTP 202 OK is
+returned in the return Channel.</p><p><a name="requestresponse"></a></p></div><div class="subsection"><a name="Request_Response_Messaging_Support"></a><h3>Request Response Messaging Support</h3><p>The Request-Response support is provided by the <code>sendReceive()</code>
+method in ServiceClient ,that provides a much simpler interface for the user.
+The Client API has four ways to configure a given Message Exchange</p><ol>
+ <li>Blocking or Non-Blocking nature - this can be decided by using
+ <code>sendReceive()</code> or <code>sendReceiveNonBlocking()</code>
+ methods</li>
+ <li>Sender transport - transport used to send the SOAP Message</li>
+ <li>Listener transport - transport the Response is received</li>
<li><p>Use Separate Channel - determines whether the response is send over
a separate transport connection or not. This can be false only when
sender and listener transport is same and is a Two-Way transport.</p>
@@ -436,40 +404,34 @@
one.</p><p>At the client side the user is free to specify the transport to be
used.</p><p>Transport In Configuration and the transport Out Configuration contains
following information.</p><ol>
- <li><style>Transport Sender for Out Configuration</style></li>
- <li><p style="margin-bottom: 0in">Transport Listener for In
- Configuration</p>
- </li>
- <li><p style="margin-bottom: 0in">Parameters of the transport</p>
- </li>
+ <li>Transport Sender for Out Configuration</li>
+ <li>Transport Listener for In Configuration</li>
+ <li>Parameters of the transport</li>
<li><p>Transport handlers</p>
</li>
</ol><p>Each and every transport Out Configuration defines a transport tender.
Transport sender sends the SOAP Message over its transport.</p><p>Transport receiver waits for the SOAP Messages and for each SOAP Message
that arrives, it uses the <i>In Pipe</i> to process the SOAP Message.</p><p>Axis2 Presently support the following transports:</p><ol>
- <li><style>HTTP - In HTTP transport the transport
- listener is a servlet or org.apache.axis2.transport.http.SimpleHTTPServer
- provided by Axis2. The transport sender uses commons-httpclient to
- connect and send the SOAP Message.</style></li>
- <li><p style="margin-bottom: 0in">TCP - This is the most simplest
- transport, but needs the WS - Addressing support to be functional.</p>
- </li>
- <li><p style="margin-bottom: 0in">SMTP - This works off a single email
- account. Transport receiver is a thread that checks for emails in fixed
- time intervals.</p>
- </li>
-</ol></div><div class="subsection"><a name="Code_generation"></a><h3>Code generation</h3><p>Although the basic objective of the code generation tool has not changed,
+ <li>HTTP - In HTTP transport the transport listener is a servlet or
+ org.apache.axis2.transport.http.SimpleHTTPServer provided by Axis2. The
+ transport sender uses commons-httpclient to connect and send the SOAP
+ Message.</li>
+ <li>TCP - This is the most simplest transport, but needs the WS -
+ Addressing support to be functional.</li>
+ <li>SMTP - This works off a single email account. Transport receiver is a
+ thread that checks for emails in fixed time intervals.</li>
+</ol><p><a name="bmWSDL" id="bmWSDL"></a></p></div><div class="subsection"><a name="Code_generation"></a><h3>Code generation</h3><p>Although the basic objective of the code generation tool has not changed,
the code generation module of Axis2 has taken a different approach to
generate code. Primarily the change is in the use of templates, namely XSL
templates which gives the code generator the flexibility to generate code in
multiple languages.</p><p>The basic approach is to set the code generator to generate an XML and
parse it with a template to generate the code file. The following figure
-describes how this shows up in the architecture of the tool.</p><p><img src="images/archi-guide/CodegenArchitecture.jpg" name="Graphic6" align="bottom" width="478" height="218" border="0" alt=""></img></p><p>The fact here is that it is the same information that is extracted from
+describes how this shows up in the architecture of the tool.</p><p><img src="images/archi-guide/CodegenArchitecture.jpg" name="Graphic6" alt="" align="bottom" width="478" height="218" border="0"></img></p><p>The fact here is that it is the same information that is extracted from
the WSDL no matter what code is generated. Code generator uses the WOM (WSDL
Object Model) internally to manipulate the WSDL and passes that information
to the emitter which emits an XML. The XML is then parsed with the relevant
XSL to generate the code. No matter what the language, the process is the
-same except for the template that is being used</p></div><div class="subsection"><a name="Data_Binding"></a><h3>Data Binding</h3></div><div class="subsection"><a name="Integration_with_the_code_generation_engine"></a><h3>Integration with the code generation engine</h3><p>Axis2 M2 was released with code generation support but without data
+same except for the template that is being used</p></div><div class="subsection"><a name="Data_Binding"></a><h3>Data Binding</h3><p><a name="integration"></a></p></div><div class="subsection"><a name="Integration_with_the_code_generation_engine"></a><h3>Integration with the code generation engine</h3><p>Axis2 M2 was released with code generation support but without data
binding. The version 0.9 was shipped with data binding support with complete
schema support. Such claim is made possible because of the fact that the data
binding tool, xml-beans, has the full schema support. The original
@@ -477,7 +439,7 @@
changes because of the way that the code generation framework was originally
designed. Data binding was incorporated as a pluggable extension to the code
generation engine. Axis2 version 0.91 does not support SOAP encoding. It only
-supports RPC literal or document literal massages.</p><p><img src="images/codegen.gif" name="Graphic7" align="bottom" width="406" height="467" border="0" alt=""></img></p></div><div class="subsection"><a name="Serialization_and_De-Serialization"></a><h3>Serialization and De-Serialization</h3><p>AXIOM is based on a StAX (Streaming API for XML) API. Xml-beans supports
+supports RPC literal or document literal massages.</p><p><img src="images/codegen.gif" name="Graphic7" align="bottom" width="406" alt="" height="467" border="0"></img></p></div><div class="subsection"><a name="Serialization_and_De-Serialization"></a><h3>Serialization and De-Serialization</h3><p>AXIOM is based on a StAX (Streaming API for XML) API. Xml-beans supports
StAX API. Data binding in Axis2 is achieved through interfacing the AXIOM
with the Xml-beans using the StAX API which is supported by both parties. At
the time of the code generation there will be supporter classes for each WSDL
Modified: webservices/axis2/site/0_94/CodegenToolReference.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/site/0_94/CodegenToolReference.html?rev=370524&r1=370523&r2=370524&view=diff
==============================================================================
--- webservices/axis2/site/0_94/CodegenToolReference.html (original)
+++ webservices/axis2/site/0_94/CodegenToolReference.html Thu Jan 19 08:22:01 2006
@@ -2,7 +2,7 @@
@import url("../style/maven-base.css");
@import url("../style/maven-theme.css");</style><link rel="stylesheet" href="../style/print.css" type="text/css" media="print"></link><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"></meta></head><body class="composite"><div id="banner"><a href="http://www.apache.org/" id="organizationLogo"><img alt="Apache Software Foundation" src="http://www.apache.org/images/asf-logo.gif"></img></a><a href="http://ws.apache.org/axis2/" id="projectLogo"><img alt="Apache Axis 2.0" src="http://ws.apache.org/axis2/images/axis.jpg"></img></a><div class="clear"><hr></hr></div></div><div id="breadcrumbs"><div class="xleft">
- Last published: 18 January 2006
+ Last published: 19 January 2006
| Doc for 0.95</div><div class="xright"></div><div class="clear"><hr></hr></div></div><div id="leftColumn"><div id="navcolumn"><div id="menuAxis_2_0"><h5>Axis 2.0</h5><ul><li class="none"><a href="../index.html">Home</a></li><li class="expanded"><a href="../">Download Axis2</a><ul><li class="none"><a href="../download.cgi">Releases</a></li><li class="none"><a href="http://svn.apache.org/viewcvs.cgi/webservices/axis2/trunk/?root=Apache-SVN" class="externalLink" title="External Link">Source Code</a></li></ul></li><li class="expanded"><a href="../">Documentation</a><ul><li class="none"><a href="../0_93/index.html">Version 0.93</a></li><li class="none"><a href="../0_94/index.html">Version 0.94</a></li></ul></li><li class="expanded"><a href="../overview.html">Get Involved</a><ul><li class="none"><a href="../svn.html">Checkout the Source</a></li><li class="none"><a href="../siteHowTo.html">Build the Site</a></li><li class="none"><a href="../guidelines.html">Devel
oper Guidelines</a></li><li class="none"><a href="../refLib.html">Reference Library</a></li><li class="none"><a href="../mail-lists.html">Mailing Lists</a></li><li class="none"><a href="../faq.html">FAQ</a></li></ul></li><li class="none"><a href="../modules/index.html">Modules</a></li><li class="none"><a href="../thanks.html">Acknowledgements</a></li><li class="expanded"><a href="../">Project Information</a><ul><li class="none"><a href="../team-list.html">Project Team</a></li><li class="none"><a href="../issue-tracking.html">Issue Tracking</a></li></ul></li></ul></div><a href="http://maven.apache.org/" title="Built by Maven" id="poweredBy"><img alt="Built by Maven" src="../images/logos/maven-button-1.png"></img></a></div></div><div id="bodyColumn"><div class="contentBox"><div class="section"><a name="Code_Generator_Wizard_-_Command_Line_Tool"></a><h2>Code Generator Wizard - Command Line Tool</h2><div class="subsection"><a name="Introduction"></a><h3>Introduction</h3><p>Just
as old times there will be users who wish to use the command line
version of the tool. This basic tool is implemented by the WSDL2Code class
and just for the convenience in the java case (which would be the majority)
@@ -27,7 +27,7 @@
</ul>
</td><td></td></tr>
<tr class="a"><td width="20%">-p <package name></td><td width="20%">--package</td><td width="60%">The target package name. If omitted, a default package
- (formed using the target namespace of the WSDL) will be used.</td><td></td></tr>
+ (formed using the target namespace of the WSDL) will be used.</td><td></td></tr>
<tr class="b"><td width="20%">-a</td><td width="20%">--async</td><td width="60%">Generate code only for async style . when this option
is used the generated stubs will have only the asynchronous
invocation methods. Switched off by default.</td><td></td></tr>
@@ -81,8 +81,8 @@
<p>Maps to the -l option of the command line tool</p>
</td></tr>
<tr class="a"><td width="50%" height="57">packagename</td><td width="50%" height="57">The target package name. If omitted, a
- default package (formed using the target namespace of the WSDL) will
- be used. Maps to the -p option of the command line tool.</td></tr>
+ default package (formed using the target namespace of the WSDL) will
+ be used. Maps to the -p option of the command line tool.</td></tr>
<tr class="b"><td width="50%" height="75">asynconly</td><td width="50%" height="75">Generate code only for async style . when
this option is used the generated stubs will have only the
asynchronous invocation methods. Defaults to false if omitted Only
@@ -110,15 +110,15 @@
<project name="CodegenExample" default="main" basedir=".">
<target name="declare" >
<taskdef name="codegen"
- classname="org.apache.axis2.tool.ant.AntCodegenTask"
- classpath="classes"/>
+ classname="org.apache.axis2.tool.ant.AntCodegenTask"
+ classpath="classes"/>
</target>
<target name="main" depends="declare">
<codegen
- wsdlfilename="C:\test\wsdl\CombinedService.wsdl"
- output="C:\"
- serverside="true"
- generateserverxml="true"/>
+ wsdlfilename="C:\test\wsdl\CombinedService.wsdl"
+ output="C:\"
+ serverside="true"
+ generateserverxml="true"/>
</target>
</project>
@@ -546,6 +546,6 @@
<p></p></div><div class="section"><a name="Appendix"></a><h2>Appendix</h2><ul>
<li>Eclipse reference - <a href="http://www.eclipse.org/" class="externalLink" title="External Link">
http://www.eclipse.org/</a></li>
- <li>Custom Ant Tasks - <a href="http://ant.apache.org/manual/develop.html" class="externalLink" title="External Link">
+ <li>Custom Ant Tasks - <a href="http://ant.apache.org/manual/develop.html" class="externalLink" title="External Link">
http://ant.apache.org/manual/develop.html</a></li>
-</ul><p> </p><p> </p><p> </p><p> </p><p> </p></div></div></div><div class="clear"><hr></hr></div><div id="footer"><div class="xright">© 2004-2006, Apache Software Foundation</div><div class="clear"><hr></hr></div></div></body></html>
\ No newline at end of file
+</ul><p></p><p></p><p></p><p></p><p></p></div></div></div><div class="clear"><hr></hr></div><div id="footer"><div class="xright">© 2004-2006, Apache Software Foundation</div><div class="clear"><hr></hr></div></div></body></html>
\ No newline at end of file
Modified: webservices/axis2/site/0_94/CodegenTools-EclipsePlugin.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/site/0_94/CodegenTools-EclipsePlugin.html?rev=370524&r1=370523&r2=370524&view=diff
==============================================================================
--- webservices/axis2/site/0_94/CodegenTools-EclipsePlugin.html (original)
+++ webservices/axis2/site/0_94/CodegenTools-EclipsePlugin.html Thu Jan 19 08:22:01 2006
@@ -2,7 +2,7 @@
@import url("../style/maven-base.css");
@import url("../style/maven-theme.css");</style><link rel="stylesheet" href="../style/print.css" type="text/css" media="print"></link><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"></meta></head><body class="composite"><div id="banner"><a href="http://www.apache.org/" id="organizationLogo"><img alt="Apache Software Foundation" src="http://www.apache.org/images/asf-logo.gif"></img></a><a href="http://ws.apache.org/axis2/" id="projectLogo"><img alt="Apache Axis 2.0" src="http://ws.apache.org/axis2/images/axis.jpg"></img></a><div class="clear"><hr></hr></div></div><div id="breadcrumbs"><div class="xleft">
- Last published: 18 January 2006
+ Last published: 19 January 2006
| Doc for 0.95</div><div class="xright"></div><div class="clear"><hr></hr></div></div><div id="leftColumn"><div id="navcolumn"><div id="menuAxis_2_0"><h5>Axis 2.0</h5><ul><li class="none"><a href="../index.html">Home</a></li><li class="expanded"><a href="../">Download Axis2</a><ul><li class="none"><a href="../download.cgi">Releases</a></li><li class="none"><a href="http://svn.apache.org/viewcvs.cgi/webservices/axis2/trunk/?root=Apache-SVN" class="externalLink" title="External Link">Source Code</a></li></ul></li><li class="expanded"><a href="../">Documentation</a><ul><li class="none"><a href="../0_93/index.html">Version 0.93</a></li><li class="none"><a href="../0_94/index.html">Version 0.94</a></li></ul></li><li class="expanded"><a href="../overview.html">Get Involved</a><ul><li class="none"><a href="../svn.html">Checkout the Source</a></li><li class="none"><a href="../siteHowTo.html">Build the Site</a></li><li class="none"><a href="../guidelines.html">Devel
oper Guidelines</a></li><li class="none"><a href="../refLib.html">Reference Library</a></li><li class="none"><a href="../mail-lists.html">Mailing Lists</a></li><li class="none"><a href="../faq.html">FAQ</a></li></ul></li><li class="none"><a href="../modules/index.html">Modules</a></li><li class="none"><a href="../thanks.html">Acknowledgements</a></li><li class="expanded"><a href="../">Project Information</a><ul><li class="none"><a href="../team-list.html">Project Team</a></li><li class="none"><a href="../issue-tracking.html">Issue Tracking</a></li></ul></li></ul></div><a href="http://maven.apache.org/" title="Built by Maven" id="poweredBy"><img alt="Built by Maven" src="../images/logos/maven-button-1.png"></img></a></div></div><div id="bodyColumn"><div class="contentBox"><div class="section"><a name="Code_Generator_Wizard_-_Eclipse_Plug-in"></a><h2>Code Generator Wizard - Eclipse Plug-in</h2><p><a href="http://ws.apache.org/axis2/download.cgi" class="externalLink" title="Ext
ernal Link">[Download]</a></p><div class="subsection"><a name="Introduction"></a><h3>Introduction</h3><p>The Axis2 code generator comes built-in with an <a href="http://www.eclipse.org" class="externalLink" title="External Link">Eclipse</a> plug-in. This document explains the
installation and usage of the Axis2 code generator plug-in.</p></div><div class="subsection"><a name="Installation"></a><h3>Installation</h3><p>The easiest way to obtain the plug-in would be the binary distribution.
The full Axis binary distribution contains the compiled version of this
@@ -21,7 +21,7 @@
provided screen shots may slightly differ with what the user would actually
see but the fuctuonality has not been changed.</i></p></div><div class="subsection"><a name="Operation"></a><h3>Operation</h3><p>If the plug-in is properly installed you should see a new wizard under the
"New" section.(use the File -> New -> Other or Ctrl + N )</p><p><img src="images/tools/wsdl/wizardSelectionPage.jpg" width="500" height="500" alt=""></img></p><p>Selecting the wizard and pressing the next button will start the code
-generator wizard. Following is the first wizard page.</p><p><img src="images/tools/wsdl/toolSelectionpage.jpg" width="557" height="501" alt=""></img></p><p>Selecting the generate code from WSDL option leads to the next page. Note
+generator wizard. Following is the first wizard page.</p><p><img alt="" src="images/tools/wsdl/toolSelectionpage.jpg" width="557" height="501"></img></p><p>Selecting the generate code from WSDL option leads to the next page. Note
that the Java-to-WSDL tool is disabled.</p><p><img src="images/tools/wsdl/WSDLSelectionPage.jpg" width="518" height="500" alt=""></img></p><p>To move on to the next page the WSDL file location must be given. The
browse button can be used to easily browse for a file rather than typing the
whole path.</p><p>Once the WSDL file is selected, codegen options are to be selected. By far
Modified: webservices/axis2/site/0_94/OMTutorial.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/site/0_94/OMTutorial.html?rev=370524&r1=370523&r2=370524&view=diff
==============================================================================
--- webservices/axis2/site/0_94/OMTutorial.html (original)
+++ webservices/axis2/site/0_94/OMTutorial.html Thu Jan 19 08:22:01 2006
@@ -2,7 +2,7 @@
@import url("../style/maven-base.css");
@import url("../style/maven-theme.css");</style><link rel="stylesheet" href="../style/print.css" type="text/css" media="print"></link><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"></meta></head><body class="composite"><div id="banner"><a href="http://www.apache.org/" id="organizationLogo"><img alt="Apache Software Foundation" src="http://www.apache.org/images/asf-logo.gif"></img></a><a href="http://ws.apache.org/axis2/" id="projectLogo"><img alt="Apache Axis 2.0" src="http://ws.apache.org/axis2/images/axis.jpg"></img></a><div class="clear"><hr></hr></div></div><div id="breadcrumbs"><div class="xleft">
- Last published: 18 January 2006
+ Last published: 19 January 2006
| Doc for 0.95</div><div class="xright"></div><div class="clear"><hr></hr></div></div><div id="leftColumn"><div id="navcolumn"><div id="menuAxis_2_0"><h5>Axis 2.0</h5><ul><li class="none"><a href="../index.html">Home</a></li><li class="expanded"><a href="../">Download Axis2</a><ul><li class="none"><a href="../download.cgi">Releases</a></li><li class="none"><a href="http://svn.apache.org/viewcvs.cgi/webservices/axis2/trunk/?root=Apache-SVN" class="externalLink" title="External Link">Source Code</a></li></ul></li><li class="expanded"><a href="../">Documentation</a><ul><li class="none"><a href="../0_93/index.html">Version 0.93</a></li><li class="none"><a href="../0_94/index.html">Version 0.94</a></li></ul></li><li class="expanded"><a href="../overview.html">Get Involved</a><ul><li class="none"><a href="../svn.html">Checkout the Source</a></li><li class="none"><a href="../siteHowTo.html">Build the Site</a></li><li class="none"><a href="../guidelines.html">Devel
oper Guidelines</a></li><li class="none"><a href="../refLib.html">Reference Library</a></li><li class="none"><a href="../mail-lists.html">Mailing Lists</a></li><li class="none"><a href="../faq.html">FAQ</a></li></ul></li><li class="none"><a href="../modules/index.html">Modules</a></li><li class="none"><a href="../thanks.html">Acknowledgements</a></li><li class="expanded"><a href="../">Project Information</a><ul><li class="none"><a href="../team-list.html">Project Team</a></li><li class="none"><a href="../issue-tracking.html">Issue Tracking</a></li></ul></li></ul></div><a href="http://maven.apache.org/" title="Built by Maven" id="poweredBy"><img alt="Built by Maven" src="../images/logos/maven-button-1.png"></img></a></div></div><div id="bodyColumn"><div class="contentBox"><div class="section"><p>
</p></div><div class="section"><a name="OM_Tutorial"></a><h2>OM Tutorial</h2><div class="subsection"><a name="Introduction"></a><h3>Introduction</h3></div><div class="subsection"><a name="What_is_OM_"></a><h3>What is OM?</h3><p>OM stands for Object Model (also known as AXIOM - AXis Object Model) and
@@ -67,14 +67,14 @@
</ul><p>
</p><p class="special"></p><table class="bodyTable"><tbody>
- <tr class="a"><td><img src="images/OM005.gif" alt="Remember this" width="35" height="57"></img></td><td class="special-td">OM is tightly bound to StAX API. To work with OM
+ <tr class="b"><td><img src="images/OM005.gif" alt="Remember this" width="35" height="57"></img></td><td class="special-td">OM is tightly bound to StAX API. To work with OM
a StAX compliant parser and the API <i>must</i> be present in the
classpath.</td><td></td></tr>
</tbody></table><p>
</p><p>The Following image shows how OM API is viewed by the user</p><p>
-</p><p align="center" class="img"><img src="images/archi006.jpg" alt="OM Structure" class="img" width="490" height="282"></img></p><p align="center" class="img-title">Figure 1</p><p>
+</p><p align="center" class="img"><img alt="" src="images/archi006.jpg" class="img" width="490" height="282"></img></p><p align="center" class="img-title">Figure 1</p><p>
</p><p>OM Builder wraps the raw xml character stream through the StAX reader API.
Hence the complexities of the pull event stream is covered</p></div><div class="subsection"><a name="A_Bit_About_Caching"></a><h3>A Bit About Caching</h3><p>Since OM is a differed built Object model, It incorporates the concept of
@@ -127,9 +127,9 @@
used in this example.</p><div align="left">
<p><b>Code Listing 1</b></p>
</div>
- <div class="source"><pre><pre>//create the parser<br></br>
+ <div class="source"><pre><pre>//create the parser<br></br>
XMLStreamReader parser = XMLInputFactory.newInstance().createXMLStreamReader(new FileReader(file));
-<br></br>//create the builder<br></br>
+<br></br>//create the builder<br></br>
OMXMLParserWrapper builder = OMXMLBuilderFactory.createStAXSOAPModelBuilder(OMAbstractFactory.getSOAP11Factory(), parser);
//get the root element (in this case the envelope)<br></br>
SOAPEnvelope envelope = (SOAPEnvelope) builder.getDocumentElement();</pre>
@@ -286,7 +286,7 @@
object structure at once, until its required.</p><p>
</p><p class="special"></p><table class="bodyTable"><tbody>
- <tr class="b"><td><img src="images/OM005.gif" alt="Remember this" width="35" height="57"></img></td><td class="special-td">All iterator implementations internally stay one
+ <tr class="a"><td><img src="images/OM005.gif" alt="Remember this" width="35" height="57"></img></td><td class="special-td">All iterator implementations internally stay one
step ahead of their apparent location to provide the correct value
for the hasNext() method. This hidden advancement can build elements
that are not intended to be built at all. Hence these iterators are
@@ -319,7 +319,7 @@
//dump the output to console with caching
envelope.serializeWithCache(writer);
writer.flush();
-
+
</pre></div>
<p>The above mentioned features of the serializer forces a correct
@@ -403,11 +403,11 @@
models. This makes such operations faster and efficient.</p><p>
</p><p class="special"></p><table class="bodyTable"><tbody>
- <tr class="a"><td><img src="images/OM005.gif" alt="Remember this" width="35" height="57"></img></td><td class="special-td">For consistency reasons once the cache is
+ <tr class="b"><td><img src="images/OM005.gif" alt="Remember this" width="35" height="57"></img></td><td class="special-td">For consistency reasons once the cache is
switched off it cannot be switched on again.</td><td></td></tr>
</tbody></table><p>
-</p></div><div class="subsection"><a name=" Known_Limitations_of_OM"></a><h3> Known Limitations of OM</h3></div><div class="subsection"><a name="Inefficient_Namespace_serialization"></a><h3>Inefficient Namespace serialization</h3><p>Although the serializer acts correctly in every situation, the code that
+</p></div><div class="subsection"><a name="Known_Limitations_of_OM"></a><h3>Known Limitations of OM</h3></div><div class="subsection"><a name="Inefficient_Namespace_serialization"></a><h3>Inefficient Namespace serialization</h3><p>Although the serializer acts correctly in every situation, the code that
it produces may not be efficient all the time. Take the following case where
a similar Code Listing to Code Listing 6 is used, but with two elements
having the same namespace. Note that the newly added items are in bold.</p><div align="left">
@@ -431,9 +431,9 @@
<p>Serialization of the root element provides the following XML</p>
<div class="source"><pre><x:root xmlns:x="bar" xmlns:y="bar1">
<x:foo>
- <y:yuck>blahblah</y:yuck>
+ <y:yuck>blahblah</y:yuck>
<y:yuck>blah</y:yuck>
- </x:foo>
+</x:foo>
</x:root>
@@ -442,9 +442,9 @@
<p>However if the serialization is carried on the foo element then the
following XML is produced</p>
<div class="source"><pre><x:foo xmlns:x="bar" >
- <y:yuck " xmlns:y="bar1">blahblah</y:yuck>
- <y:yuck " xmlns:y="bar1">blah</y:yuck>
- </x:foo>
+ <y:yuck " xmlns:y="bar1">blahblah</y:yuck>
+ <y:yuck " xmlns:y="bar1">blah</y:yuck>
+</x:foo>
@@ -507,6 +507,6 @@
to Pull parsing</a></li>
</ul>
</p></div></div><div class="section"><table class="bodyTable"><tbody>
- <tr class="b"><td align="center">All rights reserved by Apache Software
+ <tr class="a"><td align="center">All rights reserved by Apache Software
Foundation</td></tr>
</tbody></table></div></div></div><div class="clear"><hr></hr></div><div id="footer"><div class="xright">© 2004-2006, Apache Software Foundation</div><div class="clear"><hr></hr></div></div></body></html>
Modified: webservices/axis2/site/0_94/ServiceArchiveToolReference.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/site/0_94/ServiceArchiveToolReference.html?rev=370524&r1=370523&r2=370524&view=diff
==============================================================================
--- webservices/axis2/site/0_94/ServiceArchiveToolReference.html (original)
+++ webservices/axis2/site/0_94/ServiceArchiveToolReference.html Thu Jan 19 08:22:01 2006
@@ -2,7 +2,7 @@
@import url("../style/maven-base.css");
@import url("../style/maven-theme.css");</style><link rel="stylesheet" href="../style/print.css" type="text/css" media="print"></link><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"></meta></head><body class="composite"><div id="banner"><a href="http://www.apache.org/" id="organizationLogo"><img alt="Apache Software Foundation" src="http://www.apache.org/images/asf-logo.gif"></img></a><a href="http://ws.apache.org/axis2/" id="projectLogo"><img alt="Apache Axis 2.0" src="http://ws.apache.org/axis2/images/axis.jpg"></img></a><div class="clear"><hr></hr></div></div><div id="breadcrumbs"><div class="xleft">
- Last published: 18 January 2006
+ Last published: 19 January 2006
| Doc for 0.95</div><div class="xright"></div><div class="clear"><hr></hr></div></div><div id="leftColumn"><div id="navcolumn"><div id="menuAxis_2_0"><h5>Axis 2.0</h5><ul><li class="none"><a href="../index.html">Home</a></li><li class="expanded"><a href="../">Download Axis2</a><ul><li class="none"><a href="../download.cgi">Releases</a></li><li class="none"><a href="http://svn.apache.org/viewcvs.cgi/webservices/axis2/trunk/?root=Apache-SVN" class="externalLink" title="External Link">Source Code</a></li></ul></li><li class="expanded"><a href="../">Documentation</a><ul><li class="none"><a href="../0_93/index.html">Version 0.93</a></li><li class="none"><a href="../0_94/index.html">Version 0.94</a></li></ul></li><li class="expanded"><a href="../overview.html">Get Involved</a><ul><li class="none"><a href="../svn.html">Checkout the Source</a></li><li class="none"><a href="../siteHowTo.html">Build the Site</a></li><li class="none"><a href="../guidelines.html">Devel
oper Guidelines</a></li><li class="none"><a href="../refLib.html">Reference Library</a></li><li class="none"><a href="../mail-lists.html">Mailing Lists</a></li><li class="none"><a href="../faq.html">FAQ</a></li></ul></li><li class="none"><a href="../modules/index.html">Modules</a></li><li class="none"><a href="../thanks.html">Acknowledgements</a></li><li class="expanded"><a href="../">Project Information</a><ul><li class="none"><a href="../team-list.html">Project Team</a></li><li class="none"><a href="../issue-tracking.html">Issue Tracking</a></li></ul></li></ul></div><a href="http://maven.apache.org/" title="Built by Maven" id="poweredBy"><img alt="Built by Maven" src="../images/logos/maven-button-1.png"></img></a></div></div><div id="bodyColumn"><div class="contentBox"><div class="section"><a name="Service_Archive_Wizard_-_Eclipse_Plug-in"></a><h2>Service Archive Wizard - Eclipse Plug-in</h2><p><a href="http://ws.apache.org/axis2/download.cgi" class="externalLink" title="E
xternal Link">[Download]</a></p><p>Axis2 comes with a simple service archiver tool. This tool provides easy
to use functionality to develop an Axis archive or an "aar" file or a "jar"
file that can be deployed as a web service to the Axis2. This tool is in the
@@ -11,26 +11,26 @@
zip file into the Eclipse installation folder. (The plug-in will actually go
into the plugins directory in the Eclipse installation root). Restarting
Eclipse will set the plug-in automatically.</p></div><div class="subsection"><a name="Operation"></a><h3>Operation</h3><p>If the plug-in is properly installed you should see a new wizard under the
-"New" section.(use the File -> New -> Other or Ctrl + N )</p><p align="center"><img border="0" src="images/tools/service/ServiceWizardSelection.jpg" width="500" height="500" alt=""></img></p><p>Selecting the wizard and pressing the next button will start the service
-generator wizard. Following is the first wizard page.</p><p align="center"><img border="0" src="images/tools/service/ServicePage1.jpg" width="500" height="500" alt=""></img></p><p>Once the class file folder is given (which should be a folder in the file
+"New" section.(use the File -> New -> Other or Ctrl + N )</p><p align="center"><img alt="" border="0" src="images/tools/service/ServiceWizardSelection.jpg" width="500" height="500"></img></p><p>Selecting the wizard and pressing the next button will start the service
+generator wizard. Following is the first wizard page.</p><p align="center"><img alt="" border="0" src="images/tools/service/ServicePage1.jpg" width="500" height="500"></img></p><p>Once the class file folder is given (which should be a folder in the file
system) the next button will be enabled. </p><p>Page 2 of the wizard requires you to locate the wsdl file. Note that the
-WSDL file cannot be skipped in this version of the tool.</p><p align="center"><img border="0" src="images/tools/service/service_page2.JPG" width="500" height="500" alt=""></img></p><p align="center">Select the service.XML file in the next wizard page</p><p align="center"><img border="0" src="images/tools/service/service_page3.JPG" width="500" height="500" alt=""></img></p><p>Note that The service XML file can be generated if needed. To proceed to
-the service generation page, check the "generate automatically" checkbox.</p><p align="center"><img border="0" src="images/tools/service/service_page3_hl.JPG" alt=""></img></p><p>If the automatic mode is not selected, then the wizard will directly jump
+WSDL file cannot be skipped in this version of the tool.</p><p align="center"><img alt="" border="0" src="images/tools/service/service_page2.JPG" width="500" height="500"></img></p><p align="center">Select the service.XML file in the next wizard page</p><p align="center"><img alt="" border="0" src="images/tools/service/service_page3.JPG" width="500" height="500"></img></p><p>Note that The service XML file can be generated if needed. To proceed to
+the service generation page, check the "generate automatically" checkbox.</p><p align="center"><img alt="" border="0" src="images/tools/service/service_page3_hl.JPG"></img></p><p>If the automatic mode is not selected, then the wizard will directly jump
to the library selection page. However if the automatic mode is selected the
-wizard will show the following page.</p><p align="center"><img border="0" src="images/tools/service/service_page4_plain.JPG" width="500" height="500" alt=""></img></p><p>This is a somewhat complicated page. The service name textbox should
+wizard will show the following page.</p><p align="center"><img alt="" border="0" src="images/tools/service/service_page4_plain.JPG" width="500" height="500"></img></p><p>This is a somewhat complicated page. The service name textbox should
include the name of the service that you wish to give the service. For the
implementation class, type in the fully qualified class name and hit the load
-button to view the operations.</p><p align="center"><img border="0" src="images/tools/service/service_page4_load.JPG" alt=""></img></p><p>The loaded operations should be displayed in a table. Once this is
+button to view the operations.</p><p align="center"><img alt="" border="0" src="images/tools/service/service_page4_load.JPG"></img></p><p>The loaded operations should be displayed in a table. Once this is
displayed you can filter the methods by selecting/deselecting the methods
-using the checkbox at each row.</p><p align="center"><img border="0" src="images/tools/service/service_page4_table.JPG" width="500" height="500" alt=""></img></p><p>Further filtering can be achieved by using the "search declared methods"
-only checkbox.</p><p align="center"><img border="0" src="images/tools/service/service_page4_search_declared.JPG" alt=""></img></p><p>Once the method selection is complete the wizard has enough information to
+using the checkbox at each row.</p><p align="center"><img alt="" border="0" src="images/tools/service/service_page4_table.JPG" width="500" height="500"></img></p><p>Further filtering can be achieved by using the "search declared methods"
+only checkbox.</p><p align="center"><img alt="" border="0" src="images/tools/service/service_page4_search_declared.JPG"></img></p><p>Once the method selection is complete the wizard has enough information to
generate a basic services.xml file. If further customization is required,
there's no choice but to manually edit it!</p><p>The next step is to add the libraries. The library addition page looks
-like this</p><p align="center"><img border="0" src="images/tools/service/service_page5.JPG" alt=""></img></p><p>The library name (with full path) can be either typed on the text box or
-browsed for using the browse button.</p><p align="center"><img border="0" src="images/tools/service/service_page5_browsed.JPG" alt=""></img></p><p>Hit the Add button to add the library to the list. The added libraries
-should be displayed in the list box</p><p align="center"><img border="0" src="images/tools/service/service_page5_hl.JPG" alt=""></img></p><p align="center"><img border="0" src="images/tools/service/service_page5_added.JPG" alt=""></img></p><p>If any library needs to be removed, highlight it in the list and hit
-remove. Click next to proceed to the last page of the wizard</p><p align="center"><img border="0" src="images/tools/service/service_page5_remove.JPG" alt=""></img></p><p>The last page of the wizard asks for the output location and the output
-archive name.</p><p></p><p align="center"><img border="0" src="images/tools/service/service_page6.JPG" alt=""></img></p><p>Once all the parameters are filled, hit the finish button to complete the
-wizard and generate the service archive.</p><p align="center"><img border="0" src="images/tools/service/success_msg.JPG" alt=""></img></p><p>If you see the above message, then you've successfully generated the
+like this</p><p align="center"><img alt="" border="0" src="images/tools/service/service_page5.JPG"></img></p><p>The library name (with full path) can be either typed on the text box or
+browsed for using the browse button.</p><p align="center"><img alt="" border="0" src="images/tools/service/service_page5_browsed.JPG"></img></p><p>Hit the Add button to add the library to the list. The added libraries
+should be displayed in the list box</p><p align="center"><img alt="" border="0" src="images/tools/service/service_page5_hl.JPG"></img></p><p align="center"><img alt="" border="0" src="images/tools/service/service_page5_added.JPG"></img></p><p>If any library needs to be removed, highlight it in the list and hit
+remove. Click next to proceed to the last page of the wizard</p><p align="center"><img alt="" border="0" src="images/tools/service/service_page5_remove.JPG"></img></p><p>The last page of the wizard asks for the output location and the output
+archive name.</p><p></p><p align="center"><img alt="" border="0" src="images/tools/service/service_page6.JPG"></img></p><p>Once all the parameters are filled, hit the finish button to complete the
+wizard and generate the service archive.</p><p align="center"><img alt="" border="0" src="images/tools/service/success_msg.JPG"></img></p><p>If you see the above message, then you've successfully generated the
service archive! This service archive can be hot deployed to Axis2</p><p>The plugin also adds a help document to the Eclipse help system. You
-should see it if you go to Eclipse help content</p><p align="center"><img border="0" src="images/tools/service/help.JPG" alt=""></img></p></div></div><div class="section"><p> </p><p> </p><p> </p><p> </p></div></div></div><div class="clear"><hr></hr></div><div id="footer"><div class="xright">© 2004-2006, Apache Software Foundation</div><div class="clear"><hr></hr></div></div></body></html>
\ No newline at end of file
+should see it if you go to Eclipse help content</p><p align="center"><img alt="" border="0" src="images/tools/service/help.JPG"></img></p></div></div><div class="section"><p></p><p></p><p></p><p></p></div></div></div><div class="clear"><hr></hr></div><div id="footer"><div class="xright">© 2004-2006, Apache Software Foundation</div><div class="clear"><hr></hr></div></div></body></html>
\ No newline at end of file
Modified: webservices/axis2/site/0_94/WS_policy.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/site/0_94/WS_policy.html?rev=370524&r1=370523&r2=370524&view=diff
==============================================================================
--- webservices/axis2/site/0_94/WS_policy.html (original)
+++ webservices/axis2/site/0_94/WS_policy.html Thu Jan 19 08:22:01 2006
@@ -2,7 +2,7 @@
@import url("../style/maven-base.css");
@import url("../style/maven-theme.css");</style><link rel="stylesheet" href="../style/print.css" type="text/css" media="print"></link><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"></meta></head><body class="composite"><div id="banner"><a href="http://www.apache.org/" id="organizationLogo"><img alt="Apache Software Foundation" src="http://www.apache.org/images/asf-logo.gif"></img></a><a href="http://ws.apache.org/axis2/" id="projectLogo"><img alt="Apache Axis 2.0" src="http://ws.apache.org/axis2/images/axis.jpg"></img></a><div class="clear"><hr></hr></div></div><div id="breadcrumbs"><div class="xleft">
- Last published: 18 January 2006
+ Last published: 19 January 2006
| Doc for 0.95</div><div class="xright"></div><div class="clear"><hr></hr></div></div><div id="leftColumn"><div id="navcolumn"><div id="menuAxis_2_0"><h5>Axis 2.0</h5><ul><li class="none"><a href="../index.html">Home</a></li><li class="expanded"><a href="../">Download Axis2</a><ul><li class="none"><a href="../download.cgi">Releases</a></li><li class="none"><a href="http://svn.apache.org/viewcvs.cgi/webservices/axis2/trunk/?root=Apache-SVN" class="externalLink" title="External Link">Source Code</a></li></ul></li><li class="expanded"><a href="../">Documentation</a><ul><li class="none"><a href="../0_93/index.html">Version 0.93</a></li><li class="none"><a href="../0_94/index.html">Version 0.94</a></li></ul></li><li class="expanded"><a href="../overview.html">Get Involved</a><ul><li class="none"><a href="../svn.html">Checkout the Source</a></li><li class="none"><a href="../siteHowTo.html">Build the Site</a></li><li class="none"><a href="../guidelines.html">Devel
oper Guidelines</a></li><li class="none"><a href="../refLib.html">Reference Library</a></li><li class="none"><a href="../mail-lists.html">Mailing Lists</a></li><li class="none"><a href="../faq.html">FAQ</a></li></ul></li><li class="none"><a href="../modules/index.html">Modules</a></li><li class="none"><a href="../thanks.html">Acknowledgements</a></li><li class="expanded"><a href="../">Project Information</a><ul><li class="none"><a href="../team-list.html">Project Team</a></li><li class="none"><a href="../issue-tracking.html">Issue Tracking</a></li></ul></li></ul></div><a href="http://maven.apache.org/" title="Built by Maven" id="poweredBy"><img alt="Built by Maven" src="../images/logos/maven-button-1.png"></img></a></div></div><div id="bodyColumn"><div class="contentBox"><div class="section"><a name="Web_Services_Policy_Support_In_Axis2"></a><h2>Web Services Policy Support In Axis2</h2><div class="subsection"><a name="-Experimental_Feature"></a><h3>-Experimental Feature</h3>
<p><em>Axis2 version 0.94</em></p><i>E-mail comments/ suggestions to: <a href="mailto:axis-dev@ws.apache.org">axis-dev@ws.apache.org</a></i></div><div class="subsection"><a name="What_is_Web_Services__WS__Policy_"></a><h3>What is Web Services (WS) Policy?</h3><p>To consume non trivial web services one must fully understand its xml
contract (WSDL) along with any other additional requirements, capabilities or
preferences which translates to the configuration of the service, and
Modified: webservices/axis2/site/0_94/adb/adb-codegen-integration.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/site/0_94/adb/adb-codegen-integration.html?rev=370524&r1=370523&r2=370524&view=diff
==============================================================================
--- webservices/axis2/site/0_94/adb/adb-codegen-integration.html (original)
+++ webservices/axis2/site/0_94/adb/adb-codegen-integration.html Thu Jan 19 08:22:01 2006
@@ -2,7 +2,7 @@
@import url("../../style/maven-base.css");
@import url("../../style/maven-theme.css");</style><link rel="stylesheet" href="../../style/print.css" type="text/css" media="print"></link><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"></meta></head><body class="composite"><div id="banner"><a href="http://www.apache.org/" id="organizationLogo"><img alt="Apache Software Foundation" src="http://www.apache.org/images/asf-logo.gif"></img></a><a href="http://ws.apache.org/axis2/" id="projectLogo"><img alt="Apache Axis 2.0" src="http://ws.apache.org/axis2/images/axis.jpg"></img></a><div class="clear"><hr></hr></div></div><div id="breadcrumbs"><div class="xleft">
- Last published: 18 January 2006
+ Last published: 19 January 2006
| Doc for 0.95</div><div class="xright"></div><div class="clear"><hr></hr></div></div><div id="leftColumn"><div id="navcolumn"><div id="menuAxis_2_0"><h5>Axis 2.0</h5><ul><li class="none"><a href="../../index.html">Home</a></li><li class="expanded"><a href="../../">Download Axis2</a><ul><li class="none"><a href="../../download.cgi">Releases</a></li><li class="none"><a href="http://svn.apache.org/viewcvs.cgi/webservices/axis2/trunk/?root=Apache-SVN" class="externalLink" title="External Link">Source Code</a></li></ul></li><li class="expanded"><a href="../../">Documentation</a><ul><li class="none"><a href="../../0_93/index.html">Version 0.93</a></li><li class="none"><a href="../../0_94/index.html">Version 0.94</a></li></ul></li><li class="expanded"><a href="../../overview.html">Get Involved</a><ul><li class="none"><a href="../../svn.html">Checkout the Source</a></li><li class="none"><a href="../../siteHowTo.html">Build the Site</a></li><li class="none"><a href
="../../guidelines.html">Developer Guidelines</a></li><li class="none"><a href="../../refLib.html">Reference Library</a></li><li class="none"><a href="../../mail-lists.html">Mailing Lists</a></li><li class="none"><a href="../../faq.html">FAQ</a></li></ul></li><li class="none"><a href="../../modules/index.html">Modules</a></li><li class="none"><a href="../../thanks.html">Acknowledgements</a></li><li class="expanded"><a href="../../">Project Information</a><ul><li class="none"><a href="../../team-list.html">Project Team</a></li><li class="none"><a href="../../issue-tracking.html">Issue Tracking</a></li></ul></li></ul></div><a href="http://maven.apache.org/" title="Built by Maven" id="poweredBy"><img alt="Built by Maven" src="../../images/logos/maven-button-1.png"></img></a></div></div><div id="bodyColumn"><div class="contentBox"><div class="section"><a name="ADB_Integration_With_Axis2"></a><h2>ADB Integration With Axis2</h2><div class="subsection"><a name="Introduction"></a><h
3>Introduction</h3><p>ADB Integration with Axis2 is simple and straightforward. Given the
extension mechanism of the Axis2 code generator, the obvious choice for the
integrator is to write an extension. The extension that is added to support
Modified: webservices/axis2/site/0_94/adb/adb-howto.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/site/0_94/adb/adb-howto.html?rev=370524&r1=370523&r2=370524&view=diff
==============================================================================
--- webservices/axis2/site/0_94/adb/adb-howto.html (original)
+++ webservices/axis2/site/0_94/adb/adb-howto.html Thu Jan 19 08:22:01 2006
@@ -2,7 +2,7 @@
@import url("../../style/maven-base.css");
@import url("../../style/maven-theme.css");</style><link rel="stylesheet" href="../../style/print.css" type="text/css" media="print"></link><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"></meta></head><body class="composite"><div id="banner"><a href="http://www.apache.org/" id="organizationLogo"><img alt="Apache Software Foundation" src="http://www.apache.org/images/asf-logo.gif"></img></a><a href="http://ws.apache.org/axis2/" id="projectLogo"><img alt="Apache Axis 2.0" src="http://ws.apache.org/axis2/images/axis.jpg"></img></a><div class="clear"><hr></hr></div></div><div id="breadcrumbs"><div class="xleft">
- Last published: 18 January 2006
+ Last published: 19 January 2006
| Doc for 0.95</div><div class="xright"></div><div class="clear"><hr></hr></div></div><div id="leftColumn"><div id="navcolumn"><div id="menuAxis_2_0"><h5>Axis 2.0</h5><ul><li class="none"><a href="../../index.html">Home</a></li><li class="expanded"><a href="../../">Download Axis2</a><ul><li class="none"><a href="../../download.cgi">Releases</a></li><li class="none"><a href="http://svn.apache.org/viewcvs.cgi/webservices/axis2/trunk/?root=Apache-SVN" class="externalLink" title="External Link">Source Code</a></li></ul></li><li class="expanded"><a href="../../">Documentation</a><ul><li class="none"><a href="../../0_93/index.html">Version 0.93</a></li><li class="none"><a href="../../0_94/index.html">Version 0.94</a></li></ul></li><li class="expanded"><a href="../../overview.html">Get Involved</a><ul><li class="none"><a href="../../svn.html">Checkout the Source</a></li><li class="none"><a href="../../siteHowTo.html">Build the Site</a></li><li class="none"><a href
="../../guidelines.html">Developer Guidelines</a></li><li class="none"><a href="../../refLib.html">Reference Library</a></li><li class="none"><a href="../../mail-lists.html">Mailing Lists</a></li><li class="none"><a href="../../faq.html">FAQ</a></li></ul></li><li class="none"><a href="../../modules/index.html">Modules</a></li><li class="none"><a href="../../thanks.html">Acknowledgements</a></li><li class="expanded"><a href="../../">Project Information</a><ul><li class="none"><a href="../../team-list.html">Project Team</a></li><li class="none"><a href="../../issue-tracking.html">Issue Tracking</a></li></ul></li></ul></div><a href="http://maven.apache.org/" title="Built by Maven" id="poweredBy"><img alt="Built by Maven" src="../../images/logos/maven-button-1.png"></img></a></div></div><div id="bodyColumn"><div class="contentBox"><div class="section"><a name="Axis2_Databinding_Framework"></a><h2>Axis2 Databinding Framework</h2><div class="subsection"><a name="Introduction"></a>
<h3>Introduction</h3><p>The objective of the Axis2Databinding framework is to provide a
lightweight and simple schema compiler/ Java bean generator for Axis2. By no
means it's to be a fully functional schema compiler like XMLBeans. This
@@ -12,7 +12,7 @@
allows it to be used as a standalone schema compiler and also to be extended
to generate code for other languages.</p></div><div class="subsection"><a name="Architectural_Overview"></a><h3>Architectural Overview</h3><p>ADB is built on a modular architecture that allows it to utilize a pre
configured writer depending on the configuration.The 'big block diagram' for
-the code generator architecture is depicted below</p><p><img src="images/ADB.jpg" alt=""></img></p><p>ADB utilizes the WS-commons XmlSchema library for reading the Schema. The
+the code generator architecture is depicted below</p><p><img alt="" src="images/ADB.jpg"></img></p><p>ADB utilizes the WS-commons XmlSchema library for reading the Schema. The
object model for the schema comes in the form of an XmlSchema object. The
schema compiler keeps an instance of the writer (in the default case it's the
JavaBeanWriter) which actually writes the classes. The writers may use
Modified: webservices/axis2/site/0_94/adb/adb-tweaking.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/site/0_94/adb/adb-tweaking.html?rev=370524&r1=370523&r2=370524&view=diff
==============================================================================
--- webservices/axis2/site/0_94/adb/adb-tweaking.html (original)
+++ webservices/axis2/site/0_94/adb/adb-tweaking.html Thu Jan 19 08:22:01 2006
@@ -2,7 +2,7 @@
@import url("../../style/maven-base.css");
@import url("../../style/maven-theme.css");</style><link rel="stylesheet" href="../../style/print.css" type="text/css" media="print"></link><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"></meta></head><body class="composite"><div id="banner"><a href="http://www.apache.org/" id="organizationLogo"><img alt="Apache Software Foundation" src="http://www.apache.org/images/asf-logo.gif"></img></a><a href="http://ws.apache.org/axis2/" id="projectLogo"><img alt="Apache Axis 2.0" src="http://ws.apache.org/axis2/images/axis.jpg"></img></a><div class="clear"><hr></hr></div></div><div id="breadcrumbs"><div class="xleft">
- Last published: 18 January 2006
+ Last published: 19 January 2006
| Doc for 0.95</div><div class="xright"></div><div class="clear"><hr></hr></div></div><div id="leftColumn"><div id="navcolumn"><div id="menuAxis_2_0"><h5>Axis 2.0</h5><ul><li class="none"><a href="../../index.html">Home</a></li><li class="expanded"><a href="../../">Download Axis2</a><ul><li class="none"><a href="../../download.cgi">Releases</a></li><li class="none"><a href="http://svn.apache.org/viewcvs.cgi/webservices/axis2/trunk/?root=Apache-SVN" class="externalLink" title="External Link">Source Code</a></li></ul></li><li class="expanded"><a href="../../">Documentation</a><ul><li class="none"><a href="../../0_93/index.html">Version 0.93</a></li><li class="none"><a href="../../0_94/index.html">Version 0.94</a></li></ul></li><li class="expanded"><a href="../../overview.html">Get Involved</a><ul><li class="none"><a href="../../svn.html">Checkout the Source</a></li><li class="none"><a href="../../siteHowTo.html">Build the Site</a></li><li class="none"><a href
="../../guidelines.html">Developer Guidelines</a></li><li class="none"><a href="../../refLib.html">Reference Library</a></li><li class="none"><a href="../../mail-lists.html">Mailing Lists</a></li><li class="none"><a href="../../faq.html">FAQ</a></li></ul></li><li class="none"><a href="../../modules/index.html">Modules</a></li><li class="none"><a href="../../thanks.html">Acknowledgements</a></li><li class="expanded"><a href="../../">Project Information</a><ul><li class="none"><a href="../../team-list.html">Project Team</a></li><li class="none"><a href="../../issue-tracking.html">Issue Tracking</a></li></ul></li></ul></div><a href="http://maven.apache.org/" title="Built by Maven" id="poweredBy"><img alt="Built by Maven" src="../../images/logos/maven-button-1.png"></img></a></div></div><div id="bodyColumn"><div class="contentBox"><div class="section"><a name="ADB_Tweaking_Guide"></a><h2>ADB Tweaking Guide</h2><div class="subsection"><a name="Introduction"></a><h3>Introduction</
h3><p>ADB is written with future extensions in mind, with a clear and flexible
way to extend or modify it's functionality. This document explains available
mechanisms to extend ADB and possibly adopt it to compile schemas to support