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 07:50:45 UTC
svn commit: r370401 [1/3] - in /webservices/axis2/trunk/java/xdocs/0_94: ./
adb/ tools/idea/
Author: chinthaka
Date: Wed Jan 18 22:50:19 2006
New Revision: 370401
URL: http://svn.apache.org/viewcvs?rev=370401&view=rev
Log:
applying Azeez'z patch correcting internal links on xdocs. Thanks Azeez. Good work!
Modified:
webservices/axis2/trunk/java/xdocs/0_94/CodegenToolReference.html
webservices/axis2/trunk/java/xdocs/0_94/CodegenTools-EclipsePlugin.html
webservices/axis2/trunk/java/xdocs/0_94/OMTutorial.html
webservices/axis2/trunk/java/xdocs/0_94/ServiceArchiveToolReference.html
webservices/axis2/trunk/java/xdocs/0_94/adb/adb-howto.html
webservices/axis2/trunk/java/xdocs/0_94/axis2config.html
webservices/axis2/trunk/java/xdocs/0_94/http-transport.html
webservices/axis2/trunk/java/xdocs/0_94/index.html
webservices/axis2/trunk/java/xdocs/0_94/mail-transport.html
webservices/axis2/trunk/java/xdocs/0_94/mtom-guide.html
webservices/axis2/trunk/java/xdocs/0_94/rest-ws.html
webservices/axis2/trunk/java/xdocs/0_94/security-module.html
webservices/axis2/trunk/java/xdocs/0_94/tools/idea/Idea_plug-in_userguide.html
webservices/axis2/trunk/java/xdocs/0_94/transport_howto.html
webservices/axis2/trunk/java/xdocs/0_94/userguide.html
webservices/axis2/trunk/java/xdocs/0_94/userguide1.html
webservices/axis2/trunk/java/xdocs/0_94/userguide2.html
webservices/axis2/trunk/java/xdocs/0_94/userguide3.html
webservices/axis2/trunk/java/xdocs/0_94/userguide4.html
webservices/axis2/trunk/java/xdocs/0_94/userguide5.html
webservices/axis2/trunk/java/xdocs/0_94/webadminguide.html
Modified: webservices/axis2/trunk/java/xdocs/0_94/CodegenToolReference.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/0_94/CodegenToolReference.html?rev=370401&r1=370400&r2=370401&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/0_94/CodegenToolReference.html (original)
+++ webservices/axis2/trunk/java/xdocs/0_94/CodegenToolReference.html Wed Jan 18 22:50:19 2006
@@ -62,7 +62,7 @@
<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>
+ (formed using the target namespace of the WSDL) will be used.</td>
<td></td>
</tr>
<tr>
@@ -192,8 +192,8 @@
<tr>
<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>
+ 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>
<td width="50%" height="75">asynconly</td>
@@ -253,15 +253,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></pre>
@@ -714,19 +714,19 @@
<ul>
<li>Eclipse reference - <a href="http://www.eclipse.org/">
http://www.eclipse.org/</a></li>
- <li>Custom Ant Tasks - <a
+ <li>Custom Ant Tasks - <a
href="http://ant.apache.org/manual/develop.html">
http://ant.apache.org/manual/develop.html</a></li>
</ul>
-<p> </p>
+<p></p>
-<p> </p>
+<p></p>
-<p> </p>
+<p></p>
-<p> </p>
+<p></p>
-<p> </p>
+<p></p>
</body>
</html>
Modified: webservices/axis2/trunk/java/xdocs/0_94/CodegenTools-EclipsePlugin.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/0_94/CodegenTools-EclipsePlugin.html?rev=370401&r1=370400&r2=370401&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/0_94/CodegenTools-EclipsePlugin.html (original)
+++ webservices/axis2/trunk/java/xdocs/0_94/CodegenTools-EclipsePlugin.html Wed Jan 18 22:50:19 2006
@@ -56,8 +56,8 @@
<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="" /></p>
+<p><img alt="" src="images/tools/wsdl/toolSelectionpage.jpg" width="557"
+height="501"/></p>
<p>Selecting the generate code from WSDL option leads to the next page. Note
that the Java-to-WSDL tool is disabled.</p>
Modified: webservices/axis2/trunk/java/xdocs/0_94/OMTutorial.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/0_94/OMTutorial.html?rev=370401&r1=370400&r2=370401&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/0_94/OMTutorial.html (original)
+++ webservices/axis2/trunk/java/xdocs/0_94/OMTutorial.html Wed Jan 18 22:50:19 2006
@@ -2,7 +2,7 @@
<head>
<meta http-equiv="content-type" content="">
<title>OM Tutorial</title>
- <link href="css/axis-docs.css" type="text/css" rel="stylesheet">
+ <link href="css/axis-docs.css" type="text/css" rel="stylesheet"/>
</head>
<body>
@@ -10,7 +10,7 @@
<table width="100%">
<tr>
<td align="left"><h1>Apache Axis2</h1></td>
-<td align="right"><img src="images/axis.jpg"/></td>
+<td align="right"><img alt="" src="images/axis.jpg"/></td>
</tr>
</table>
end of header section -->
@@ -118,8 +118,8 @@
<p>The Following image shows how OM API is viewed by the user</p>
<!-- Image -->
-<p align="center" class="img"><img src="images/archi006.jpg"
-alt="OM Structure" class="img" width="490" height="282"></p>
+<p align="center" class="img"><img alt="" src="images/archi006.jpg"
+ class="img" width="490" height="282"></p>
<p align="center" class="img-title">Figure 1</p>
<!-- End of Image -->
@@ -214,11 +214,11 @@
<div align="left">
<p><b>Code Listing 1</b></p>
</div>
-<source><pre>//create the parser<br>
+<source><pre>//create the parser<br/>
XMLStreamReader parser = XMLInputFactory.newInstance().createXMLStreamReader(new FileReader(file));
-<br>//create the builder<br>
+<br/>//create the builder<br/>
OMXMLParserWrapper builder = OMXMLBuilderFactory.createStAXSOAPModelBuilder(OMAbstractFactory.getSOAP11Factory(), parser);
-//get the root element (in this case the envelope)<br>
+//get the root element (in this case the envelope)<br/>
SOAPEnvelope envelope = (SOAPEnvelope) builder.getDocumentElement();</pre>
</source>
<p>As the example shows, creating an OM from an input stream is pretty
@@ -454,7 +454,7 @@
//dump the output to console with caching
envelope.serializeWithCache(writer);
writer.flush();</pre>
-<pre class="code"> </pre>
+<pre class="code"></pre>
<p>The above mentioned features of the serializer forces a correct
serialization even if only a part of the OM tree is serialized. The following
@@ -565,7 +565,7 @@
</table>
<!-- End of special section -->
-<h3> Known Limitations of OM</h3>
+<h3>Known Limitations of OM</h3>
<h3>Inefficient Namespace serialization</h3>
@@ -595,9 +595,9 @@
<p>Serialization of the root element provides the following XML</p>
<pre class="xml"><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>
</pre>
@@ -605,9 +605,9 @@
<p>However if the serialization is carried on the foo element then the
following XML is produced</p>
<pre class="xml"><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>
</pre>
Modified: webservices/axis2/trunk/java/xdocs/0_94/ServiceArchiveToolReference.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/0_94/ServiceArchiveToolReference.html?rev=370401&r1=370400&r2=370401&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/0_94/ServiceArchiveToolReference.html (original)
+++ webservices/axis2/trunk/java/xdocs/0_94/ServiceArchiveToolReference.html Wed Jan 18 22:50:19 2006
@@ -27,41 +27,41 @@
<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"
+<p align="center"><img alt="" border="0"
src="images/tools/service/ServiceWizardSelection.jpg" width="500"
height="500"></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"
+<p align="center"><img alt="" border="0" src="images/tools/service/ServicePage1.jpg"
width="500" height="500"></p>
-<p>Once the class file folder is given (which should be a folder in the file
+<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"
+<p align="center"><img alt="" border="0"
src="images/tools/service/service_page2.JPG" width="500" height="500"></p>
<p align="center">Select the service.XML file in the next wizard page</p>
-<p align="center"><img border="0"
+<p align="center"><img alt="" border="0"
src="images/tools/service/service_page3.JPG" width="500" height="500"></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"
+<p align="center"><img alt="" border="0"
src="images/tools/service/service_page3_hl.JPG"></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"
+<p align="center"><img alt="" border="0"
src="images/tools/service/service_page4_plain.JPG" width="500"
height="500"></p>
@@ -70,21 +70,21 @@
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"
+<p align="center"><img alt="" border="0"
src="images/tools/service/service_page4_load.JPG"></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"
+<p align="center"><img alt="" border="0"
src="images/tools/service/service_page4_table.JPG" width="500"
height="500"></p>
<p>Further filtering can be achieved by using the "search declared methods"
only checkbox.</p>
-<p align="center"><img border="0"
+<p align="center"><img alt="" border="0"
src="images/tools/service/service_page4_search_declared.JPG"></p>
<p>Once the method selection is complete the wizard has enough information to
@@ -94,28 +94,28 @@
<p>The next step is to add the libraries. The library addition page looks
like this</p>
-<p align="center"><img border="0"
+<p align="center"><img alt="" border="0"
src="images/tools/service/service_page5.JPG"></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"
+<p align="center"><img alt="" border="0"
src="images/tools/service/service_page5_browsed.JPG"></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"
+<p align="center"><img alt="" border="0"
src="images/tools/service/service_page5_hl.JPG"></p>
-<p align="center"><img border="0"
+<p align="center"><img alt="" border="0"
src="images/tools/service/service_page5_added.JPG"></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"
+<p align="center"><img alt="" border="0"
src="images/tools/service/service_page5_remove.JPG"></p>
<p>The last page of the wizard asks for the output location and the output
@@ -123,13 +123,13 @@
<p></p>
-<p align="center"><img border="0"
+<p align="center"><img alt="" border="0"
src="images/tools/service/service_page6.JPG"></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"
+<p align="center"><img alt="" border="0"
src="images/tools/service/success_msg.JPG"></p>
<p>If you see the above message, then you've successfully generated the
@@ -138,15 +138,15 @@
<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"></p>
+<p align="center"><img alt="" border="0" src="images/tools/service/help.JPG"></p>
<hr>
-<p> </p>
+<p></p>
-<p> </p>
+<p></p>
-<p> </p>
+<p></p>
-<p> </p>
+<p></p>
</body>
</html>
Modified: webservices/axis2/trunk/java/xdocs/0_94/adb/adb-howto.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/0_94/adb/adb-howto.html?rev=370401&r1=370400&r2=370401&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/0_94/adb/adb-howto.html (original)
+++ webservices/axis2/trunk/java/xdocs/0_94/adb/adb-howto.html Wed Jan 18 22:50:19 2006
@@ -30,7 +30,7 @@
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"></p>
+<p><img alt="" src="images/ADB.jpg"></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
Modified: webservices/axis2/trunk/java/xdocs/0_94/axis2config.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/0_94/axis2config.html?rev=370401&r1=370400&r2=370401&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/0_94/axis2config.html (original)
+++ webservices/axis2/trunk/java/xdocs/0_94/axis2config.html Wed Jan 18 22:50:19 2006
@@ -18,7 +18,8 @@
(module.xml)</a></li>
</ul>
-<h2><a name="Global_Configuration">Global Configuration</a></h2>
+<a name="Global_Configuration"/>
+<h2>Global Configuration</h2>
<ul>
<li>Writing axis2.xml</li>
</ul>
@@ -37,20 +38,22 @@
<li>Listeners (Observers)</li>
</ul>
-<p><b>Parameter </b> <br>
+<p><b>Parameter </b> <br/>
In axis2 a parameter is nothing but name value pair, each and every top level
parameter available in the axis2.xml (direct sub elements of root element)
will be transformed into properties in AxisConfiguration. Therefore the top
level parameters in configuration document can be accessed via
AxisConfiguration in the running system. The correct way of defining a
-parameter looks like what is shown below; <source></p>
+parameter looks like what is shown below;</p>
+<source>
<pre>
<parameter name="name of the parameter" >parameter value </parameter></pre>
</source>
-<p><b>Transport Receiver</b><br>
+
+<p><b>Transport Receiver</b><br/>
Depending on the underline transport that axis going to be run , need to have
different transport receivers so the way of adding them to the system can be
-done as follows; <source></p>
+done as follows; <p><source>
<pre>
<transportReceiver name="http" class="org.apache.axis2.transport.http.SimpleHTTPServer">
<parameter name="port" >6060</parameter>
@@ -66,12 +69,12 @@
any, then those parameters can be accessed via the corresponding transport
receiver.
-<p><b>Transport Senders</b><br>
+<p><b>Transport Senders</b><br/>
As same as transport receivers it is possible to register transport senders
in the system, and latter at the run time those senders can be used to send
the messages. As an example consider Axis2 running under tomcat, then axis
can use TCP transport senders to send message rather than HTTP. The way of
-specifying transport senders is as follows: <source></p>
+specifying transport senders is as follows: <p><source>
<pre>
<transportSender name="http" class="org.apache.axis2.transport.http.CommonsHTTPTransportSender">
<parameter name="PROTOCOL" locked="xsd:false">HTTP/1.0</parameter>
@@ -83,9 +86,9 @@
more parameters, and if there is any then it can be accessed via
corresponding transport sender.
-<p><b>Phase Order</b><br>
+<p><b>Phase Order</b><br/>
The specifying order of phases in execution chain has to be done using phase
-order element and it will be look like below; <source></p>
+order element and it will be look like below; <p><source>
<pre><phaseOrder type="inflow">
<phase name="TransportIn"/>
.
@@ -156,9 +159,9 @@
<p>In addition to that only child element allowed inside pahseOrder is phase
element, which represents available phases in the execution chain. The way of
-specifying phase inside phaseOrder has to be done as follows; <source></p>
+specifying phase inside phaseOrder has to be done as follows; <p><source>
<pre> <phase name="TransportIn"/></pre>
-</source>name: Name of the phase. <br>
+</source>name: Name of the phase. <br/>
There are number of things that one has to keep in mind when changing
pahseOrder,
<ul>
@@ -171,9 +174,9 @@
<ol>
If you closely look at the default axis2.xml can clearly identify that.</ol>
-<p><b>Module References</b><br>
+<p><b>Module References</b><br/>
If you want to engage a module system wide you can do it by adding top level
-module element in axis2.xml. It should be look like following: <source></p>
+module element in axis2.xml. It should be look like following: <p><source>
<pre><module ref="addressing"/> </pre>
</source>ref: the module name which is going to be engage, system wide.
Listeners (Observers) In Axis2 AxisConfiguration is observable so that one
@@ -195,8 +198,8 @@
be note that the implementation class should implement AxisObserver
interface, and the class has to be available in the classpath.
-<h2><font><a name="Service_Configuration">Service
-Configuration</a></font></h2>
+<a name="Service_Configuration"/>
+<h2><font>Service Configuration</font></h2>
<ul>
<li><font>Writing services.xml</font></li>
</ul>
@@ -204,8 +207,10 @@
<p><font>The description of service is specified using services.xml, each
service archive file need to have services.xml in order to be a valid
service. And which has to be available in META-INF directory of the archive
-file. <br>
-A very simple services.xml is shown below: </font><font><source></font></p>
+file. <br/>
+A very simple services.xml is shown below: </font>
+ </p>
+ <source>
<pre><font><service >
<description> The description of the service </description>
@@ -216,69 +221,70 @@
<messageReceiver class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver"/>
</operation>
</service>
-</font><font></source></font></pre>
+</font></pre></source>
+
<font>service name: the service name will be the name of the archive file.
-<br>
+<br/>
description: This is an optional element if you want to display any
description about the service via Axis2 web-admin module then the description
can be specified here.</font>
-<p><b>Parameter:</b><br>
+<p><b>Parameter:</b><br/>
services.xml can have any number of top level parameters and all the
specified parameters will be transformed into service properties in
corresponding ServiceDescrption. There is a compulsory parameter in a
services.xml called ServiceClass which specify the java class which really
does the job and the class will be loaded by MessageReceiver.</p>
-<p><b>Handler</b><br>
+<p><b>Handler</b><br/>
Handler element consists of compulsory and optional attribute and the way of
-defining a handler will be look like follows; <source></p>
+defining a handler will be look like follows; <p><source>
<pre><handler name="handler1" class="handlerClass ">
<order phase="userphase1" />
</handler>
-</source></pre>
-<b><i>Compulsory attributes</i></b> <br>
-name: name of the handler<br>
-nlass: handler implementation class<br>
+</pre></source>
+<b><i>Compulsory attributes</i></b> <br/>
+name: name of the handler<br/>
+nlass: handler implementation class<br/>
phase: name of the phase that the handler should stay in the execution chain
-<br>
-<br>
-<i><b>Optional attributes :</b></i><br>
-phaseLast: to indicate the handler is last handler of the phase<br>
-phaseFirst: to indicate the handler is first handler of the phase.<br>
+<br/>
+<br/>
+<i><b>Optional attributes :</b></i><br/>
+phaseLast: to indicate the handler is last handler of the phase<br/>
+phaseFirst: to indicate the handler is first handler of the phase.<br/>
before : the handler should be invoked before the handler specified by before
-handler<br>
+handler<br/>
after: the handler should be invoked after the handler specified by after
-handler<br>
+handler<br/>
-<p><b>Operations</b><br>
+<p><b>Operations</b><br/>
All the operations you are going to exposeby the service has to be indicated
in the services.xml and the correct way of specifying that should be as
-follows: <source></p>
+follows: <p><source>
<pre> <operation name="echoString">
<module ref=" a module name "/>
<messageReceiver class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver"/>
</operation>
-</source></pre>
+</pre></source>
Only compulsory attribute here is name, which represent the operation name
that is going to be exposed. Any operation can contains module references,
any number of parameters. The most interesting is that one can register
custom message receiver per operation, then the registered message receiver
will be the message receiver for the corresponding operation. If one does not
specify the message receiver then the default message receiver will do the
-job. <br>
-
+job. <br/>
-<h2><a name="Module_Configuration">Module Configuration</a></h2>
+<a name="Module_Configuration"/>
+<h2>Module Configuration</h2>
<ul>
<li>Writing module.xml</li>
</ul>
<p>The description of module is specified using module.xml, each module
archive file need to have module.xml in order to be a valid module. And which
-has to be available in META-INF directory of the archive file. <br>
-A very simple module.xml is shown below: <source></p>
+has to be available in META-INF directory of the archive file. <br/>
+A very simple module.xml is shown below: <p><source>
<pre><module name="module1" class="org.apache.module.Module1Impl">
<inflow>
.
@@ -304,9 +310,9 @@
<parameter name="para1" locked="xsd:true">10</parameter>
</operation>
</module>
-</source></pre>
+</pre></source>
name: This is a compulsory attribute and which indicates the name of the
-module <br>
+module <br/>
class: This is an optional attribute which indicate module implementation
class, a module may or may not contain module implementation class since the
module can also be a collection of handlers. If a module contains an
@@ -317,16 +323,16 @@
listed parameters in the module.xml will be transformed into corresponding
ModuleDescription of the module.</p>
-<p><b>Flow :</b><br>
+<p><b>Flow :</b><br/>
It is possible to add handlers into a flow directly form services.xml rather
than engaging a modules and the way of doing that is through flow elements.
It is possible to add any number of handlers into a flow and those handlers
will be available in corresponding operations flows in the service (inflow
consist of two parts, one part is up to post dispatch phase and other part is
-consisting of operation handlers) <br>
+consisting of operation handlers) <br/>
There are four types of valid flows that can be available in services.xml,
and the adding the handles into them can be done by following the above
-procedure. <br>
+procedure. <br/>
Valid flows:</p>
<ul>
<li>Inflow</li>
@@ -338,6 +344,6 @@
<p><b>operations</b> If a module wants to add an operation when it is engaged
into a service it can be done by adding operation tag in module.xml and the
way of specifying the operation is same as operation in services.xml.</p>
-<br>
+<br/>
</body>
</html>
Modified: webservices/axis2/trunk/java/xdocs/0_94/http-transport.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/0_94/http-transport.html?rev=370401&r1=370400&r2=370401&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/0_94/http-transport.html (original)
+++ webservices/axis2/trunk/java/xdocs/0_94/http-transport.html Wed Jan 18 22:50:19 2006
@@ -6,7 +6,8 @@
</head>
<body lang="en">
-<h1><a name="#configTransport">HTTP transports</a></h1>
+<a name="configTransport"/>
+<h1>HTTP transports</h1>
<h3>CommonsHTTPTransportSender</h3>
@@ -21,7 +22,7 @@
<p><transportSender/> element is used to define transport senders in
the axis2.xml as follows:</p>
-<pre><code><transportSender name="http" class="org.apache.axis2.transport.http.CommonsHTTPTransportSender"><br> <parameter name="PROTOCOL" locked="false">HTTP/1.1</parameter><br> <parameter name="Transfer-Encoding">chunked</parameter><br></transportSender><br></code></pre>
+<pre><code><transportSender name="http" class="org.apache.axis2.transport.http.CommonsHTTPTransportSender"><br/> <parameter name="PROTOCOL" locked="false">HTTP/1.1</parameter><br/> <parameter name="Transfer-Encoding">chunked</parameter><br/></transportSender><br/></code></pre>
<p>Above code snippet shows the complete configuration of the transport
sender. <parameter/> element introduces the additional parameters that
@@ -38,7 +39,7 @@
<h4>HTTPS support</h4>
It should be noted that CommonsHTTPTransportSender can be used to communicate
over https. <code></code>
-<pre><transportSender name="<b>https</b>" class="org.apache.axis2.transport.http.CommonsHTTPTransportSender"><br> <parameter name="PROTOCOL" locked="false">HTTP/1.1</parameter><br> <parameter name="Transfer-Encoding">chunked</parameter><br></transportSender><br></pre>
+<pre><transportSender name="<b>https</b>" class="org.apache.axis2.transport.http.CommonsHTTPTransportSender"><br/> <parameter name="PROTOCOL" locked="false">HTTP/1.1</parameter><br/> <parameter name="Transfer-Encoding">chunked</parameter><br/></transportSender><br/></pre>
Please note that https works only when the server does not expect to
authenticate the clients and where the server has the clients' public keys in
its trust store.
@@ -55,7 +56,7 @@
<p>For Connection timeout:</p>
<pre> <parameter name="CONNECTION_TIMEOUT" locked="false">some_int_value</parameter></pre>
-<br>
+<br/>
In runtime it's set as follows in the Stub. <source>
<pre>...
Options options = new Options();
@@ -76,7 +77,7 @@
<pre><transportSender name="<b>http</b>" class="org.apache.axis2.transport.http.CommonsHTTPTransportSender">
<parameter name="PROTOCOL" locked="false">HTTP/1.1</parameter>
<parameter name="PROXY" proxy_host="proxy_host_name" proxy_port="proxy_host_port" locked="true>userName:domain:passWord</parameter>
-</transportSender><br></pre>
+</transportSender><br/></pre>
<p>For a particular proxy, if authentication is not available fill
"userName:domain:passWord"as "anonymous:anonymous:anonymous".</p>
Modified: webservices/axis2/trunk/java/xdocs/0_94/index.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/0_94/index.html?rev=370401&r1=370400&r2=370401&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/0_94/index.html (original)
+++ webservices/axis2/trunk/java/xdocs/0_94/index.html Wed Jan 18 22:50:19 2006
@@ -22,7 +22,7 @@
Eclipse Plug-in</a></li>
<li><a href="ServiceArchiveToolReference.html">Service Archive Wizard -
Eclipse Plug-in</a></li>
- <li><a href="tools\idea\Idea_plug-in_userguide.html">IntelliJ IDEA
+ <li><a href="tools/idea/Idea_plug-in_userguide.html">IntelliJ IDEA
Plug-ins</a></li>
</ul>
Modified: webservices/axis2/trunk/java/xdocs/0_94/mail-transport.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/0_94/mail-transport.html?rev=370401&r1=370400&r2=370401&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/0_94/mail-transport.html (original)
+++ webservices/axis2/trunk/java/xdocs/0_94/mail-transport.html Wed Jan 18 22:50:19 2006
@@ -32,9 +32,9 @@
<p>Broadly speaking there are 3 ways of calling a service through mail.</p>
<blockquote>
- 1. Using the simple mail server included in Axis2.<br>
- 2. Using a generic mail server.<br>
- 3. Using mailets.<br>
+ 1. Using the simple mail server included in Axis2.<br/>
+ 2. Using a generic mail server.<br/>
+ 3. Using mailets.<br/>
</blockquote>
<p></p>
@@ -60,7 +60,7 @@
<p>Now that we have the environment set up, let us start pumping out some
code to get the mail functionality off the ground. First we'll have a look at
-it from the mail server side. <br>
+it from the mail server side. <br/>
</p>
<source><pre> // Start the mail server using the default configurations.
ConfigurationContext configContext = UtilsMailServer.start();
Modified: webservices/axis2/trunk/java/xdocs/0_94/mtom-guide.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/0_94/mtom-guide.html?rev=370401&r1=370400&r2=370401&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/0_94/mtom-guide.html (original)
+++ webservices/axis2/trunk/java/xdocs/0_94/mtom-guide.html Wed Jan 18 22:50:19 2006
@@ -35,7 +35,7 @@
there are times when serializing data into XML does not make sense. Web
services users may need to transmit binary attachments of various sorts like
images, drawings, xml docs, etc together with SOAP message. Such data are
-often in a particular binary format.<br>
+often in a particular binary format.<br/>
Traditionally, two techniques have been used in dealing with opaque data in
XML;</p>
<ol>
@@ -238,9 +238,11 @@
</li>
</ul>
-<p><source></p>
+<p><source>
<pre><parameter name="enableMTOM" locked="false">true</parameter></pre>
-</source><ul>
+</source>
+</p>
+<ul>
<ul>
<p>User must restart the server after setting this parameter.</p>
</ul>
@@ -276,7 +278,8 @@
}
}</pre>
</source><ul>
- <li><strong><a name="242"></a>Client</strong></li>
+ <a name="242"/>
+ <li><strong>Client</strong></li>
</ul>
<source><pre> Options options = new Options();
options.setTo(targetEPR);
Modified: webservices/axis2/trunk/java/xdocs/0_94/rest-ws.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/0_94/rest-ws.html?rev=370401&r1=370400&r2=370401&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/0_94/rest-ws.html (original)
+++ webservices/axis2/trunk/java/xdocs/0_94/rest-ws.html Wed Jan 18 22:50:19 2006
@@ -54,12 +54,12 @@
<p>There is an example named, userguide.clients.RESTClient.java which
demonstrates the usage of the above, using the "echo"operation of the
-<source></p>
+ </p>
<pre>userguide.example1.MyService </pre>
<p>of the samples.The class source will be as follows:</p>
-<p><source></p>
+<source>
<pre>public class RESTClient {
private static String toEpr = "http://localhost:8080/axis2/services/MyService";
@@ -111,9 +111,9 @@
<source><pre>http://127.0.0.1:8080/axis2/services/version/getVersion</pre>
</source>
<p>Result can be shown in the browser as follows:</p>
-<img src="images/userguide/http-get-ws.png">
+<img src="images/userguide/http-get-ws.png" alt="" />
-<p>For example, the following request, <source></p>
+<p>For example, the following request, </p><source>
<pre>http://127.0.0.1:8080/axis2/services/version/getVersion</pre>
</source>will be converted to the following SOAP Message for processing by
Axis2.<source>
@@ -124,5 +124,7 @@
</soapenv:Body>
</soapenv:Envelope>
</pre>
-</source></body>
+</source>
+
+</body>
</html>
Modified: webservices/axis2/trunk/java/xdocs/0_94/security-module.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/0_94/security-module.html?rev=370401&r1=370400&r2=370401&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/0_94/security-module.html (original)
+++ webservices/axis2/trunk/java/xdocs/0_94/security-module.html Wed Jan 18 22:50:19 2006
@@ -1,23 +1,34 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html><title>The Security Module</title>
+<html><title>The Security Module</title>
+
<body>
<h1>Securing SOAP Messages with WSS4J</h1>
-<p>Axis2 comes with a module based on WSS4J [1] to provide WS-Security features. This section explains how to engage and configure the security module. Since the security module inserts handlers in the system specific pre-dispatch phase, it must be engaged globally. But it is possible to activate the security module for the inflow or the outflow when required by the service or the clients.</p>
+<p>Axis2 comes with a module based on WSS4J [1] to provide WS-Security features. This section
+ explains how to engage and configure the security module. Since the security module inserts
+ handlers in the system specific pre-dispatch phase, it must be engaged globally. But it is
+ possible to activate the security module for the inflow or the outflow when required by the
+ service or the clients.</p>
+
+<p>The security module (security.mar) is available in the axis2.war but it is not engaged by
+ default.</p>
-<p>The security module (security.mar) is available in the axis2.war but it is not engaged by default.</p>
<p>First it should be engaged by inserting the following in the axis2.xml file.</p>
<source><pre>
- <module ref="security"/>
+ <module ref="security"/>
</pre></source>
-<p>The web admin interface can be used when Axis2 is deployed in a servlet container such as Apache Tomcat.</p>
-<p>At the server it is possible to provide security on a per service basis. The configuration parameters should be set in the service.xml file of the service. The client side config parameters should be set in the axis2.xml of the client's Axis2 repository.</p>
+<p>The web admin interface can be used when Axis2 is deployed in a servlet container such as Apache
+ Tomcat.</p>
+
+<p>At the server it is possible to provide security on a per service basis. The configuration
+ parameters should be set in the service.xml file of the service. The client side config
+ parameters should be set in the axis2.xml of the client's Axis2 repository.</p>
<p>The security module uses two parameters:</p>
<ul>
-<li>OutflowSecurity</li>
-<li>InflowSecurity</li>
+ <li>OutflowSecurity</li>
+ <li>InflowSecurity</li>
</ul>
The configuration that can go in each of these parameters are described below:
@@ -25,145 +36,176 @@
<h3>OutflowSecurity parameter</h3>
This parameter is used to configure the outflow security handler. The outflow
- handler can be invoked more than once in the outflow one can provide
- configuration for each of these invocations. The 'action' element describes
- one of these configurations. Therefore the 'OutflowSecurity' parameter can
- contain more than one 'action' elements. The schema of this 'action' element
- is available <a href="sec-conf/out-action.xsd">here</a>.
-<p>An outflow configuration to add a timestamp, sing and encrypt
- the message once, is shown in<a href="#ex1"> Example 1</a> and <a href="#ex1">
- Example 2</a> shows how to sign the message twice by chaining the outflow
- handler (using two 'action' elements)</p>
-
-<p>Following is a description of the elements that can go in an 'action'
-element of the OutflowSecurity parameter</p>
-<br>
+handler can be invoked more than once in the outflow one can provide
+configuration for each of these invocations. The 'action' element describes
+one of these configurations. Therefore the 'OutflowSecurity' parameter can
+contain more than one 'action' elements. The schema of this 'action' element
+is available <a href="sec-conf/out-action.xsd">here</a>.
+<p>An outflow configuration to add a timestamp, sing and encrypt
+ the message once, is shown in<a href="#ex1"> Example 1</a> and <a href="#ex1">
+ Example 2</a> shows how to sign the message twice by chaining the outflow
+ handler (using two 'action' elements)</p>
+
+<p>Following is a description of the elements that can go in an 'action'
+ element of the OutflowSecurity parameter</p>
+<br/>
<table border="1">
-<tr>
-<td><b>Parameter</b></td>
-<td><b>Description</b></td>
-<td><b>Example</b></td>
-</tr>
-<tr>
-<td>items</td>
-<td>Security actions for the inflow</td>
-<td>Add a Timestamp, Sign the SOAP body and Encrypt the SOAP body <br><items> Timestamp Signature Encrypt</items></td>
-</tr>
-<tr>
-<td>user</td>
-<td>The user's name</td>
-<td>Set alias of the key to be used to sign<br><user> bob</user></td>
-</tr>
-<tr>
-<td>passwordCallbackClass</td>
-<td>Callback class used to provide the password required to create the UsernameToken or to sign the message</td>
-<td><passwordCallbackClass> org.apache.axis2.security.PWCallback</passwordCallbackClass></td>
-</tr>
-<tr>
-<td>signaturePropFile</td>
-<td>property file used to get the signature parameters such as crypto provider, keystore and its password</td>
-<td>Set example.properties file as the signature property file<br><signaturePropFile> example.properties</signaturePropFile></td>
-</tr>
-<tr>
-<td>signatureKeyIdentifier</td>
-<td>Key identifier to be used in referring the key in the signature</td>
-<td>Use the serial number of the certificate<br><signatureKeyIdentifier> IssuerSerial</signatureKeyIdentifier></td>
-</tr>
-<tr>
-<td>encryptionKeyIdentifier</td>
-<td>Key identifier to be used in referring the key in encryption</td>
-<td>Use the serial number of the certificate <br><encryptionKeyIdentifier>IssuerSerial</encryptionKeyIdentifier></td>
-</tr>
-<tr>
-<td>encryptionUser</td>
-<td>The user's name for encryption.</td>
-<td><br><encryptionUser>alice</encryptionUser></td>
-</tr>
-<tr>
-<td>encryptionSymAlgorithm</td>
-<td>Symmetric algorithm to be used for encryption</td>
-<td>Use AES-128<br><encryptionSymAlgorithm> http://www.w3.org/2001/04/xmlenc#aes128-cbc</encryptionSymAlgorithm></td>
-</tr>
-<tr>
-<td>encryptionKeyTransportAlgorithm</td>
-<td>Key encryption algorithm</td>
-<td>Use RSA-OAEP<br><parameter name="encryptionSymAlgorithm"> http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p</parameter></td>
-</tr>
-<tr>
-<td>signatureParts</td>
-<td>Sign multiple parts in the SOAP message</td>
-<td>Sign Foo and Bar elements qualified by "http://app.ns/ns"<br><signatureParts> {Element}{http://app.ns/ns}Foo;{Element}{http://app.ns/ns}Bar </signatureParts></td>
-</tr>
-<tr>
-<td>optimizeParts</td>
-<td>MTOM Optimize the elements specified by the XPath query</td>
-<td>Optimize the CipherValue<br><optimizeParts> //xenc:EncryptedData/xenc:CipherData/xenc:CipherValue </optimizeParts></td>
-</tr>
+ <tr>
+ <td><b>Parameter</b></td>
+ <td><b>Description</b></td>
+ <td><b>Example</b></td>
+ </tr>
+ <tr>
+ <td>items</td>
+ <td>Security actions for the inflow</td>
+ <td>Add a Timestamp, Sign the SOAP body and Encrypt the SOAP body <br/><items>
+ Timestamp Signature Encrypt</items></td>
+ </tr>
+ <tr>
+ <td>user</td>
+ <td>The user's name</td>
+ <td>Set alias of the key to be used to sign<br/><user> bob</user></td>
+ </tr>
+ <tr>
+ <td>passwordCallbackClass</td>
+ <td>Callback class used to provide the password required to create the UsernameToken or to
+ sign the message</td>
+ <td><passwordCallbackClass> org.apache.axis2.security.PWCallback</passwordCallbackClass></td>
+ </tr>
+ <tr>
+ <td>signaturePropFile</td>
+ <td>property file used to get the signature parameters such as crypto provider, keystore and
+ its password</td>
+ <td>Set example.properties file as the signature property file<br/><signaturePropFile>
+ example.properties</signaturePropFile></td>
+ </tr>
+ <tr>
+ <td>signatureKeyIdentifier</td>
+ <td>Key identifier to be used in referring the key in the signature</td>
+ <td>Use the serial number of the certificate<br/><signatureKeyIdentifier> IssuerSerial</signatureKeyIdentifier>
+ </td>
+ </tr>
+ <tr>
+ <td>encryptionKeyIdentifier</td>
+ <td>Key identifier to be used in referring the key in encryption</td>
+ <td>Use the serial number of the certificate <br/><encryptionKeyIdentifier>IssuerSerial</encryptionKeyIdentifier>
+ </td>
+ </tr>
+ <tr>
+ <td>encryptionUser</td>
+ <td>The user's name for encryption.</td>
+ <td><br/><encryptionUser>alice</encryptionUser></td>
+ </tr>
+ <tr>
+ <td>encryptionSymAlgorithm</td>
+ <td>Symmetric algorithm to be used for encryption</td>
+ <td>Use AES-128<br/><encryptionSymAlgorithm>
+ http://www.w3.org/2001/04/xmlenc#aes128-cbc</encryptionSymAlgorithm></td>
+ </tr>
+ <tr>
+ <td>encryptionKeyTransportAlgorithm</td>
+ <td>Key encryption algorithm</td>
+ <td>Use RSA-OAEP<br/><parameter name="encryptionSymAlgorithm">
+ http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p</parameter></td>
+ </tr>
+ <tr>
+ <td>signatureParts</td>
+ <td>Sign multiple parts in the SOAP message</td>
+ <td>Sign Foo and Bar elements qualified by "http://app.ns/ns"<br/><signatureParts>
+ {Element}{http://app.ns/ns}Foo;{Element}{http://app.ns/ns}Bar </signatureParts>
+ </td>
+ </tr>
+ <tr>
+ <td>optimizeParts</td>
+ <td>MTOM Optimize the elements specified by the XPath query</td>
+ <td>Optimize the CipherValue<br/><optimizeParts>
+ //xenc:EncryptedData/xenc:CipherData/xenc:CipherValue </optimizeParts></td>
+ </tr>
</table>
-<br>
+<br/>
+
<h3>InflowSecurity parameter</h3>
-<p>This parameter is used to configure the inflow security handler. The 'action' element is used to
-encapsulate the configuration elements here as well. The schema of the 'action' element is available here.
-<a href="#ex3">Example 3</a> shows the configuration to decrypt, verify signature and validate timestamp.</p>
-<table border="1">
-<tr>
-<td><b>Parameter</b></td>
-<td><b>Description</b></td>
-<td><b>Example</b></td>
-</tr>
-<tr>
-<td>items</td>
-<td>Security actions for the inflow</td>
-<td>first the incoming message should be decrypted and then the signatures should be verified and should be checked for the availability of the Timestamp <br><items> Timestamp Signature Encrypt</items></td>
-</tr>
-<tr>
-<td>passwordCallbackClass</td>
-<td>Callback class used to obtain password for decryption and UsernameToken verification</td>
-<td><br><passwordCallbackClass> org.apache.axis2.security.PWCallback</passwordCallbackClass></td>
-</tr>
-<tr>
-<td>signaturePropFile</td>
-<td>Property file used for signature verification</td>
-<td><br><signaturePropFile> sig.properties</signaturePropFile></td>
-</tr>
-<td>decryptionPropFile</td>
-<td>Property file used for decryption</td>
-<td> <br><decryptionPropFile> dec.properties</decryptionPropFile></td>
-</tr>
+<p>This parameter is used to configure the inflow security handler. The 'action' element is used to
+ encapsulate the configuration elements here as well. The schema of the 'action' element is
+ available here.
+ <a href="#ex3">Example 3</a> shows the configuration to decrypt, verify signature and validate
+ timestamp.</p>
+<table border="1">
+ <tr>
+ <td><b>Parameter</b></td>
+ <td><b>Description</b></td>
+ <td><b>Example</b></td>
+ </tr>
+ <tr>
+ <td>items</td>
+ <td>Security actions for the inflow</td>
+ <td>first the incoming message should be decrypted and then the signatures should be
+ verified and should be checked for the availability of the Timestamp <br/><items>
+ Timestamp Signature Encrypt</items></td>
+ </tr>
+ <tr>
+ <td>passwordCallbackClass</td>
+ <td>Callback class used to obtain password for decryption and UsernameToken
+ verification</td>
+ <td><br/><passwordCallbackClass> org.apache.axis2.security.PWCallback</passwordCallbackClass>
+ </td>
+ </tr>
+ <tr>
+ <td>signaturePropFile</td>
+ <td>Property file used for signature verification</td>
+ <td><br/><signaturePropFile> sig.properties</signaturePropFile></td>
+ </tr>
+ <tr>
+ <td>decryptionPropFile</td>
+ <td>Property file used for decryption</td>
+ <td><br/><decryptionPropFile> dec.properties</decryptionPropFile></td>
+ </tr>
</table>
-<br>
-<p>Please note that the '.properties' files used in properties such as OutSignaturePropFile are the same property files that are using in the WSS4J project.
-Following shows the properties defined in a sample property file</p>
+<br/>
+
+<p>Please note that the '.properties' files used in properties such as OutSignaturePropFile are the
+ same property files that are using in the WSS4J project.
+ Following shows the properties defined in a sample property file</p>
<source>
-<pre>
-org.apache.ws.security.crypto.provider=org.apache.ws.security.components.crypto.Merlin
-org.apache.ws.security.crypto.merlin.keystore.type=pkcs12
-org.apache.ws.security.crypto.merlin.keystore.password=security
-org.apache.ws.security.crypto.merlin.keystore.alias=16c73ab6-b892-458f-abf5-2f875f74882e
-org.apache.ws.security.crypto.merlin.alias.password=security
-org.apache.ws.security.crypto.merlin.file=keys/x509.PFX.MSFT
-</pre>
+ <pre>
+ org.apache.ws.security.crypto.provider=org.apache.ws.security.components.crypto.Merlin
+ org.apache.ws.security.crypto.merlin.keystore.type=pkcs12
+ org.apache.ws.security.crypto.merlin.keystore.password=security
+ org.apache.ws.security.crypto.merlin.keystore.alias=16c73ab6-b892-458f-abf5-2f875f74882e
+ org.apache.ws.security.crypto.merlin.alias.password=security
+ org.apache.ws.security.crypto.merlin.file=keys/x509.PFX.MSFT
+ </pre>
</source>
-org.apache.ws.security.crypto.provider defines the implementation of the org.apache.ws.security.components.crypto.Crypto
-interface to provide the crypto information required by WSS4J. The other properties defined are the configuration
- properties used by the implementation class (org.apache.ws.security.components.crypto.Merlin).
-
+org.apache.ws.security.crypto.provider defines the implementation of the
+org.apache.ws.security.components.crypto.Crypto
+interface to provide the crypto information required by WSS4J. The other properties defined are the
+configuration
+properties used by the implementation class (org.apache.ws.security.components.crypto.Merlin).
+
<p><b>References</b></p>
+
<p>1. <a href="http://ws.apache.org/wss4j">Apache WSS4J</a></p>
-<br>
+<br/>
+
<p><b>Examples</b></p>
-<p id="ex1">Example 1: An outflow configuration to add a timestamp, sing and encrypt
- the message once</p>
-<p><img src="sec-conf/out-sample.png"/>
+
+<p id="ex1">Example 1: An outflow configuration to add a timestamp, sing and encrypt
+ the message once</p>
+
+<p><img alt="" src="sec-conf/out-sample.png"/>
</p>
<p id="ex2">Example 2: An outflow configuration to sign the message twice and add a timestamp</p>
-<p><img src="sec-conf/out-sample2.png"/>
+
+<p><img alt="" src="sec-conf/out-sample2.png"/>
</p>
-<p id="ex3">Example 3: An inflow configuration to decrypt, verify signature and validate timestamp</p>
-<p><img src="sec-conf/in-sample.png"/>
+
+<p id="ex3">Example 3: An inflow configuration to decrypt, verify signature and validate
+ timestamp</p>
+
+<p><img alt="" src="sec-conf/in-sample.png"/>
</p>
</body></html>
Modified: webservices/axis2/trunk/java/xdocs/0_94/tools/idea/Idea_plug-in_userguide.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/0_94/tools/idea/Idea_plug-in_userguide.html?rev=370401&r1=370400&r2=370401&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/0_94/tools/idea/Idea_plug-in_userguide.html (original)
+++ webservices/axis2/trunk/java/xdocs/0_94/tools/idea/Idea_plug-in_userguide.html Wed Jan 18 22:50:19 2006
@@ -11,7 +11,7 @@
<body lang="en">
<h1>IntelliJ IDEA Plug-ins</h1>
-<p><a href="http://ws.apache.org/axis2/download.cgi">[Download]</p>
+<p><a href="http://ws.apache.org/axis2/download.cgi">[Download]</a></p>
<h2>Introduction</h2>
@@ -47,7 +47,8 @@
<p><img alt="Figure3" src="images/fig1.jpg"></p>
-<h2><a name="WSDL2Java_Code_Generation">WSDL2Java Code Generation</a></h2>
+<a name="WSDL2Java_Code_Generation"/>
+<h2>WSDL2Java Code Generation</h2>
<p>Select WSDL2Java codegenaration and click OK to generate code from a WSDL
file. Then the following window will appear.</p>
@@ -89,7 +90,8 @@
<p>If everything has gone well you will see the above message.</p>
-<h2><a name="Create_Service_Archive">Ceate Service Archive</a></h2>
+<a name="Create_Service_Archive"/>
+<h2>Ceate Service Archive</h2>
<p>First step is to click on Axis2 IDEA plug-in icon and select 'create a
service archive' radio button.</p>
@@ -175,7 +177,8 @@
<p>If you click No, Next button will enable and you can go to next page.</p>
-<p><a name="Note">Note</a>: From this point onwards the steps are similar to
+<a name="Note">
+<p>Note: From this point onwards the steps are similar to
all the sub wizards.</p>
<p><img alt="fig12" src="images/fig12.jpg"></p>
Modified: webservices/axis2/trunk/java/xdocs/0_94/transport_howto.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/0_94/transport_howto.html?rev=370401&r1=370400&r2=370401&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/0_94/transport_howto.html (original)
+++ webservices/axis2/trunk/java/xdocs/0_94/transport_howto.html Wed Jan 18 22:50:19 2006
@@ -70,7 +70,7 @@
should ideally be only done once for the lifetime of the Transport
receiver.</p>
-<p><source></p>
+<p><source>
<pre>try {
//Create a factory
ConfigurationContextFactory factory = new ConfigurationContextFactory();
@@ -80,6 +80,7 @@
log.info(e.getMessage());
}</pre>
</source>
+</p>
<p>Now we need some kind of a listener to listen to the requests that come
in. This you will need to implement according to the transport that you are
trying to build. After a message is received at the receiver you can use the