axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cha...@apache.org
Subject svn commit: r395932 - in /webservices/axis2/trunk/java/xdocs/latest: security-module.html userguide1.html
Date Fri, 21 Apr 2006 16:23:55 GMT
Author: chatra
Date: Fri Apr 21 09:23:52 2006
New Revision: 395932

URL: http://svn.apache.org/viewcvs?rev=395932&view=rev
Log:
fixed jira issue AXIS2-599 and updated features for 1.0

Modified:
    webservices/axis2/trunk/java/xdocs/latest/security-module.html
    webservices/axis2/trunk/java/xdocs/latest/userguide1.html

Modified: webservices/axis2/trunk/java/xdocs/latest/security-module.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/security-module.html?rev=395932&r1=395931&r2=395932&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/latest/security-module.html (original)
+++ webservices/axis2/trunk/java/xdocs/latest/security-module.html Fri Apr 21 09:23:52 2006
@@ -1,211 +1,234 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html><title>The Security Module</title>
+<html>
+<head>
+  <meta http-equiv="content-type" content="">
+  <title>The Security Module</title>
+</head>
 
 <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>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>
-    &lt;module ref="security"/&gt;
-</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>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 with the Axis2 release.</p>
+
+<p>First it should be engaged by inserting the following in the axis2.xml
+file.</p>
+<source><pre>    &lt;module ref="security"/&gt;</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 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:
 
 <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>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/>
+element of the OutflowSecurity parameter</p>
+<br>
+
+
 <table border="1">
+  <tbody>
     <tr>
-        <td><b>Parameter</b></td>
-        <td><b>Description</b></td>
-        <td><b>Example</b></td>
+      <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/>&lt;items&gt;
-            Timestamp Signature Encrypt&lt;/items&gt;</td>
+      <td>items</td>
+      <td>Security actions for the inflow</td>
+      <td>Add a Timestamp, Sign the SOAP body and Encrypt the SOAP body <br>
+        &lt;items&gt; Timestamp Signature Encrypt&lt;/items&gt;</td>
     </tr>
     <tr>
-        <td>user</td>
-        <td>The user's name</td>
-        <td>Set alias of the key to be used to sign<br/>&lt;user&gt;
bob&lt;/user&gt;</td>
+      <td>user</td>
+      <td>The user's name</td>
+      <td>Set alias of the key to be used to sign<br>
+        &lt;user&gt; bob&lt;/user&gt;</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>&lt;passwordCallbackClass&gt; org.apache.axis2.security.PWCallback&lt;/passwordCallbackClass&gt;</td>
+      <td>passwordCallbackClass</td>
+      <td>Callback class used to provide the password required to create the
+        UsernameToken or to sign the message</td>
+      <td>&lt;passwordCallbackClass&gt;
+        org.apache.axis2.security.PWCallback&lt;/passwordCallbackClass&gt;</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/>&lt;signaturePropFile&gt;
-            example.properties&lt;/signaturePropFile&gt;</td>
+      <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>
+        &lt;signaturePropFile&gt;
+      example.properties&lt;/signaturePropFile&gt;</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/>&lt;signatureKeyIdentifier&gt;
IssuerSerial&lt;/signatureKeyIdentifier&gt;
-        </td>
+      <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>
+        &lt;signatureKeyIdentifier&gt;
+        IssuerSerial&lt;/signatureKeyIdentifier&gt;</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/>&lt;encryptionKeyIdentifier&gt;IssuerSerial&lt;/encryptionKeyIdentifier&gt;
-        </td>
+      <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>
+        &lt;encryptionKeyIdentifier&gt;IssuerSerial&lt;/encryptionKeyIdentifier&gt;</td>
     </tr>
     <tr>
-        <td>encryptionUser</td>
-        <td>The user's name for encryption.</td>
-        <td><br/>&lt;encryptionUser&gt;alice&lt;/encryptionUser&gt;</td>
+      <td>encryptionUser</td>
+      <td>The user's name for encryption.</td>
+      <td><br>
+        &lt;encryptionUser&gt;alice&lt;/encryptionUser&gt;</td>
     </tr>
     <tr>
-        <td>encryptionSymAlgorithm</td>
-        <td>Symmetric algorithm to be used for encryption</td>
-        <td>Use AES-128<br/>&lt;encryptionSymAlgorithm&gt;
-            http://www.w3.org/2001/04/xmlenc#aes128-cbc&lt;/encryptionSymAlgorithm&gt;</td>
+      <td>encryptionSymAlgorithm</td>
+      <td>Symmetric algorithm to be used for encryption</td>
+      <td>Use AES-128<br>
+        &lt;encryptionSymAlgorithm&gt;
+        http://www.w3.org/2001/04/xmlenc#aes128-cbc&lt;/encryptionSymAlgorithm&gt;</td>
     </tr>
     <tr>
-        <td>encryptionKeyTransportAlgorithm</td>
-        <td>Key encryption algorithm</td>
-        <td>Use RSA-OAEP<br/>&lt;parameter name="encryptionSymAlgorithm"&gt;
-            http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p&lt;/parameter&gt;</td>
+      <td>encryptionKeyTransportAlgorithm</td>
+      <td>Key encryption algorithm</td>
+      <td>Use RSA-OAEP<br>
+        &lt;parameter name="encryptionSymAlgorithm"&gt;
+        http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p&lt;/parameter&gt;</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/>&lt;signatureParts&gt;
-            {Element}{http://app.ns/ns}Foo;{Element}{http://app.ns/ns}Bar &lt;/signatureParts&gt;
-        </td>
+      <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>
+        &lt;signatureParts&gt;
+        {Element}{http://app.ns/ns}Foo;{Element}{http://app.ns/ns}Bar
+        &lt;/signatureParts&gt;</td>
     </tr>
     <tr>
-        <td>optimizeParts</td>
-        <td>MTOM Optimize the elements specified by the XPath query</td>
-        <td>Optimize the CipherValue<br/>&lt;optimizeParts&gt;
-            //xenc:EncryptedData/xenc:CipherData/xenc:CipherValue &lt;/optimizeParts&gt;</td>
+      <td>optimizeParts</td>
+      <td>MTOM Optimize the elements specified by the XPath query</td>
+      <td>Optimize the CipherValue<br>
+        &lt;optimizeParts&gt;
+        //xenc:EncryptedData/xenc:CipherData/xenc:CipherValue
+        &lt;/optimizeParts&gt;</td>
     </tr>
+  </tbody>
 </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>
+<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">
+  <tbody>
     <tr>
-        <td><b>Parameter</b></td>
-        <td><b>Description</b></td>
-        <td><b>Example</b></td>
+      <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/>&lt;items&gt;
-            Timestamp Signature Encrypt&lt;/items&gt;</td>
+      <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>
+        &lt;items&gt; Timestamp Signature Encrypt&lt;/items&gt;</td>
     </tr>
     <tr>
-        <td>passwordCallbackClass</td>
-        <td>Callback class used to obtain password for decryption and UsernameToken
-            verification</td>
-        <td><br/>&lt;passwordCallbackClass&gt; org.apache.axis2.security.PWCallback&lt;/passwordCallbackClass&gt;
-        </td>
+      <td>passwordCallbackClass</td>
+      <td>Callback class used to obtain password for decryption and
+        UsernameToken verification</td>
+      <td><br>
+        &lt;passwordCallbackClass&gt;
+        org.apache.axis2.security.PWCallback&lt;/passwordCallbackClass&gt;</td>
     </tr>
     <tr>
-        <td>signaturePropFile</td>
-        <td>Property file used for signature verification</td>
-        <td><br/>&lt;signaturePropFile&gt; sig.properties&lt;/signaturePropFile&gt;</td>
+      <td>signaturePropFile</td>
+      <td>Property file used for signature verification</td>
+      <td><br>
+        &lt;signaturePropFile&gt;
+      sig.properties&lt;/signaturePropFile&gt;</td>
     </tr>
     <tr>
-        <td>decryptionPropFile</td>
-        <td>Property file used for decryption</td>
-        <td><br/>&lt;decryptionPropFile&gt; dec.properties&lt;/decryptionPropFile&gt;</td>
+      <td>decryptionPropFile</td>
+      <td>Property file used for decryption</td>
+      <td><br>
+        &lt;decryptionPropFile&gt;
+      dec.properties&lt;/decryptionPropFile&gt;</td>
     </tr>
+  </tbody>
 </table>
-<br/>
+<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
+<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>
-</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).
+</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).
 
 <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 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><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 id="ex2">Example 2: An outflow configuration to sign the message twice and
+add a timestamp</p>
 
-<p><img alt="" src="sec-conf/out-sample2.png"/>
-</p>
+<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 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>
\ No newline at end of file
+<p><img alt="" src="sec-conf/in-sample.png"></p>
+</body>
+</html>

Modified: webservices/axis2/trunk/java/xdocs/latest/userguide1.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/userguide1.html?rev=395932&r1=395931&r2=395932&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/latest/userguide1.html (original)
+++ webservices/axis2/trunk/java/xdocs/latest/userguide1.html Fri Apr 21 09:23:52 2006
@@ -135,60 +135,57 @@
 <h3><a name="Axis2_Complete_Features_List">Axis2 Complete Features
 List</a></h3>
 <ol type="1"> 
- <li>AXIOM, an XML object model working on StAX (Streaming API for XML) parsing optimized
for SOAP 1.1/1.2 Messages. This has complete XML infoset support.</li>
- <li>Support for One-Way Messaging (In-Only) and Request Response Messaging (In-Out)</li>
- <li>Module Architecture, mechanism to extend the SOAP Processing Model</li>
- <li>Module version support , can have multiple versions of the same module and use
them depending on the requirement.</li>
- <li>Content hierarchy</li>
- <li>Archive based deployment Model and Directory based deployment model</li>
- <li>JWS like deployment (making Java class into Web service)</li>
- <li>WSDL Code Generation Tool for Stub and skeletons</li>
- <li>WS-Addressing, both the submission (2004/08) and final (2005/08) versions</li>
- <li>WSS4J module for security</li>
- <li>Improved and user friendly Client API</li>
- <li>WSDL2Java and Java2WSDL</li>
- <li>REST (REpresentational State Transfer) Support</li>
- <li>Transports supports: HTTP, SMTP, TCP, JMS</li>
- <li>Raw XML providers</li>
- <li>Support for MTOM/ MIME/ SwA</li>
- <li>SAAJ implementation</li>
- <li>DOOM</li>
- <li>Pack/Unpack capability for the generated code</li>
- <li>Axis Data Binding - ADB (Framework and Schema Compiler)</li>
- <li>Numerous bug fixes since last release</li>
- <li>Transport framework improvements (ListenerManager)- <span style="color: #FF0000">New</span></li>
- <li>AxisServlet auto start when application server get start up- <span style="color:
#FF0000">New</span></li>
- <li>Module dis-engagemnt support- <span style="color: #FF0000">New</span></li>
- <li>Loading module (.mar) from classpath- <span style="color: #FF0000">New</span></li>
- <li>Sessions scoping for Application, SOAP, Transport and Request levels-<span
style="color: #FF0000">New</span></li>
-</ol>
+  <li>AXIOM, an XML object model working on StAX (Streaming API for XML)
+    parsing optimized for SOAP 1.1/1.2 Messages. This has complete XML
+    infoset support.</li>
+  <li>Support for One-Way Messaging (In-Only) and Request Response Messaging
+    (In-Out).</li>
+  <li>Module Architecture, mechanism to extend the SOAP Processing model.</li>
+  <li>Module version support, can have multiple versions of the same module
+    and use them depending on the requirement.</li>
+  <li>Content hierarchy</li>
+  <li>Archive based deployment model and Directory based deployment model</li>
+  <li>JWS like deployment (making Java class into Web service)</li>
+  <li>WSDL Code Generation tool for stubs and skeletons</li>
+  <li>WS-Addressing, both the submission (2004/08) and final (2005/08)
+    versions</li>
+  <li>WSS4J module for security</li>
+  <li>Improved and user friendly Client API</li>
+  <li>WSDL2Java and Java2WSDL</li>
+  <li>REST (REpresentational State Transfer) Support</li>
+  <li>Transports supports: HTTP, SMTP, TCP, JMS</li>
+  <li>Raw XML providers</li>
+  <li>Support for MTOM/ MIME/ SwA</li>
+  <li>SAAJ implementation</li>
+  <li>DOOM (OM DOM implementation)</li>
+  <li>Pack/Unpack capability for the generated code</li>
+  <li>Axis Data Binding - ADB (Framework and Schema Compiler)</li>
+  <li>Transport framework improvements (ListenerManager)</li>
+  <li>Module disengagemnt support</li>
+  <li>Loading modules (.mar files) from classpath</li>
+  <li>Sessions scoping for Application, SOAP, Transport and Request
+  levels</li>
+  <li>Server side and client side Web service Policy support</li>
+  <li>?wsdl and ?xsd support</li>
+  <li>Dynamic ServiceClient generation for a given WSDL and invoking the
+    corresponding service using generated client</li>
+  <li>WSDL fault handling (fault code generation)</li>
+  <li>SOAP 1.2 and HTTP binding generation (?wsdl)</li>
+  <li>Streaming Attachments support for MTOM (SOAP Message Transamission
+    Optimization Mechanism)</li></ol>
 
 <h4><a name="Experimental_Features_List">Experimental Features List</a></h4>
 <ol type="1">
- <li><a href="WS_policy.html" target="_blank">Server side & client side Web
Service Policy support</a></li>
- <li>?wsdl and ?xsd support</li>
- <li>Generating ServiceClient for a given WSDL and invoke the corresponding service
using generated client.</li>
+  <li>URL based deployment mechanism (starting Axis with remote
+  repository)</li>
+  <li>Unexpanded war support (location of axis2.xml and repository can be
+    specified in web.xml )</li>
 </ol>
 
-<h4><a name="Major_Changes_Since_Last_Release">Major Changes Since Last
+<!--<h4><a name="Major_Changes_Since_Last_Release">Major Changes Since Last
 Release</a></h4>
 <ol type="1">
-   <li>Transport framework improvements (ListenerManager)</li>
-   <li>Changed the way of adding action to mapping (wsamapping) from parameter to child
element so with this version onward the way of adding mapping is as follows:</li>
-   <pre>
-   
-&lt;actionMapping&gt;MyMapping&lt;/actionMapping&gt;
-
-</pre>
-<li>Refactored following packages in Axiom.
-    <ul>
-     <li>org.apache.axiom.om.impl.llom.builder to org.apache.axiom.om.impl.builder</li>
-     <li>org.apache.axiom.om.impl.llom.mtom to org.apache.axiom.om.impl.mtom</li>
-     <li>org.apache.axiom.om.impl.llom.serialize to org.apache.axiom.om.impl.serialize</li>
-     <li>org.apache.axiom.om.impl.llom.traverse to org.apache.axiom.om.impl.traverse</li>
-   </ul>
- </li>
-</ol>
+</ol>-->
 
 <h3><a name="Tools_included_in this_Release">Tools Included In This
 Release</a></h3>
@@ -205,6 +202,19 @@
     IDEA plugin</a>--></li>
 </ol>
 <p><a href="http://ws.apache.org/axis2/download.cgi" target="_blank">Download</a>
above plugins</p>
+
+<h3>What Still To Do?</h3>
+<p>See list of what we think needs to be done, and consider helping out if
+you're interested and able!</p>
+<ol type="1">
+  <li>JAX-RPC 1.1 and/or JAX-WS compliance</li>
+  <li>SOAP Encoding</li>
+  <li>Binary serialization and de-serialization support</li>
+  <li>Resource framework implementation (WS-RF) and Enterprise web services
+    such as JSR 109 support</li>
+  <li>HTTP transport based on URL.openConnection (to be usable in Java Web
+    Start clients, because of authenticating proxies)</li>
+</ol>
 
 <p align="right"><a href="userguide.html"><img
 src="images/arrow_left.gif"> Previous</a> | <a href="userguide2.html">Next
<img src="images/arrow_right.gif"></a></p>



Mime
View raw message