[jboss-svn-commits] JBossWS SVN: r871 - in tags/jbossws-1.0.3.GA: docs/user-guide/project/en/modules/installation docs/user-guide/project/en/modules/secureejb docs/user-guide/project/en/modules/wssecurity src/main/resources/dist

[jboss-svn-commits at lists.jboss.org]

Author: heiko.braun at jboss.com
Date: 2006-08-31 05:31:47 -0400 (Thu, 31 Aug 2006)
New Revision: 871

Modified:
   tags/jbossws-1.0.3.GA/docs/user-guide/project/en/modules/installation/install-tomcat.xml
   tags/jbossws-1.0.3.GA/docs/user-guide/project/en/modules/secureejb/secure-ejb.xml
   tags/jbossws-1.0.3.GA/docs/user-guide/project/en/modules/wssecurity/wssecurity.xml
   tags/jbossws-1.0.3.GA/src/main/resources/dist/ReleaseNotes.txt
Log:
Updated release notes and documentation

Modified: tags/jbossws-1.0.3.GA/docs/user-guide/project/en/modules/installation/install-tomcat.xml
===================================================================
--- tags/jbossws-1.0.3.GA/docs/user-guide/project/en/modules/installation/install-tomcat.xml	2006-08-31 08:06:17 UTC (rev 870)
+++ tags/jbossws-1.0.3.GA/docs/user-guide/project/en/modules/installation/install-tomcat.xml	2006-08-31 09:31:47 UTC (rev 871)
@@ -30,7 +30,7 @@
         </listitem>
         <listitem>
             <para>
-              Copy jbossws-core.jar, jbossws-tomcat-integration.jar, jbossws-thirdparty.jar to ${tomcat.home}/common/lib. 
+              Copy jbossws-core.jar, jbossws-tomcat-integration.jar, jbossws-thirdparty.jar, jboss-jaxrpc.jar, jboss-saaj.jar to ${tomcat.home}/common/lib. 
             </para>
         </listitem>
         <listitem>

Modified: tags/jbossws-1.0.3.GA/docs/user-guide/project/en/modules/secureejb/secure-ejb.xml
===================================================================
--- tags/jbossws-1.0.3.GA/docs/user-guide/project/en/modules/secureejb/secure-ejb.xml	2006-08-31 08:06:17 UTC (rev 870)
+++ tags/jbossws-1.0.3.GA/docs/user-guide/project/en/modules/secureejb/secure-ejb.xml	2006-08-31 09:31:47 UTC (rev 871)
@@ -198,8 +198,7 @@
   </jboss>
    ]]></programlisting></para>
   
-  <para>At last, make sure that your WSDL files point to the right url. 
-    Otherwise your webservice client may be redirected to the unsecure HTTP access method. 
+  <para>At last, make sure that the endpoint address in your WSDL file uses a secure protocol. 
     The easiest way is to add "https://" to the SOAP Address entry:</para>
 
   <para>

Modified: tags/jbossws-1.0.3.GA/docs/user-guide/project/en/modules/wssecurity/wssecurity.xml
===================================================================
--- tags/jbossws-1.0.3.GA/docs/user-guide/project/en/modules/wssecurity/wssecurity.xml	2006-08-31 08:06:17 UTC (rev 870)
+++ tags/jbossws-1.0.3.GA/docs/user-guide/project/en/modules/wssecurity/wssecurity.xml	2006-08-31 09:31:47 UTC (rev 871)
@@ -286,11 +286,46 @@
          </orderedlist>
       </para>
 
-      <para>We did not specify a key store or trust store, because client apps instead use the wsse System properties instead. If this was a web or ejb client (meaning a webservice client in a war or ejb jar file), then we would have specified them in the client descriptor.</para>
+      <para>We did not specify a key store or trust store, because client apps instead use the wsse System properties instead. If this was a web or ejb client (meaning a webservice client in a war or ejb jar file), then we would have specified them in the client descriptor. In that case, the keystore/truststore tags are the same as the one specified in the server config.</para>
 
    </sect1>
-
    <sect1>
+      <title>Standalone Client System Properties</title>
+      <para>If the client is standalone (not running within the container), then you need to specify the keystore and truststore values as system properties. They are as follows:</para> 
+   
+     <table frame="all">
+      <title>Standlone Client System Properties</title>
+      <tgroup cols="2">
+        <tbody>
+          <row>
+            <entry>org.jboss.wsse.keyStore</entry>
+            <entry>The keystore file.</entry>
+          </row>
+          <row>
+            <entry>org.jboss.wsse.keyStorePassword</entry>
+            <entry>The password for the keystore.</entry>
+          </row>
+          <row>
+            <entry>org.jboss.wsse.keyStoreType</entry>
+            <entry>The type of the keystore (JKS, pkcs12, etc).</entry>
+          </row>
+          <row>
+            <entry>org.jboss.wsse.trustStore</entry>
+            <entry>The trust store. It must contain the certs for any peer that communicates with the service.</entry>
+          </row>
+          <row>
+            <entry>org.jboss.wsse.trustStorePassword</entry>
+            <entry>The password for the truststore.</entry>
+          </row>
+          <row>
+            <entry>org.jboss.wsse.trustStoreType</entry>
+            <entry>The type of the truststore (JKS, pkcs12, etc).</entry>
+          </row>
+        </tbody>
+      </tgroup>
+     </table>
+   </sect1>
+   <sect1>
       <title>SOAP message exchange</title>
 
       <para>Below you see the incomming SOAP message with the details of the security headers ommited. The idea is, that the SOAP body is still

Modified: tags/jbossws-1.0.3.GA/src/main/resources/dist/ReleaseNotes.txt
===================================================================
--- tags/jbossws-1.0.3.GA/src/main/resources/dist/ReleaseNotes.txt	2006-08-31 08:06:17 UTC (rev 870)
+++ tags/jbossws-1.0.3.GA/src/main/resources/dist/ReleaseNotes.txt	2006-08-31 09:31:47 UTC (rev 871)
@@ -36,6 +36,7 @@
 
 Feature Request
 
+* [JBWS-1160] - XOP Inline base64 for doc/lit requests  
 * [JBWS-1090] - preventing override of webservices.xml when multiple web services are processed with wstools
 * [JBWS-1106] - java.io.NotSerializableException: org.jboss.ws.wsse.SimplePrincipal
 * [JBWS-1119] - Add support for fault signing and encryption