You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fx-dev@ws.apache.org by we...@apache.org on 2005/07/22 20:58:00 UTC
cvs commit: ws-wss4j build.xml README.txt
werner 2005/07/22 11:58:00
Modified: . build.xml README.txt
Log:
Add some more info to readme.txt, add files to bindist target
of build.xml.
Prepare for binary distribution WSS4J 1.0.0
Revision Changes Path
1.31 +3 -3 ws-wss4j/build.xml
Index: build.xml
===================================================================
RCS file: /home/cvs/ws-wss4j/build.xml,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -r1.30 -r1.31
--- build.xml 10 Jun 2005 10:56:50 -0000 1.30
+++ build.xml 22 Jul 2005 18:58:00 -0000 1.31
@@ -45,7 +45,7 @@
<property name='product.version.major' value='1'/>
<property name='product.version.minor' value='0'/>
- <property name='product.version.level' value='Beta'/>
+ <property name='product.version.level' value='0'/>
<property name='product.Version' value='${product.version.major}.${product.version.minor}.${product.version.level}'/>
<property name='product.version' value='${product.version.major}.${product.version.minor}.${product.version.level}'/>
<property name='product_version' value='${product.version.major}_${product.version.minor}_${product.version.level}'/>
@@ -561,9 +561,9 @@
<zip destfile="${dir.dist}/${product.shortname}-bin-${product.version}.zip">
<zipfileset prefix="wss4j" dir="."
includes="keys/**, interop/**, interop2/**, test/**, samples/**,
- LICENSE.txt, legal/**, webapps/**"/>
+ LICENSE.txt, README.txt legal/**, webapps/**"/>
<zipfileset prefix="wss4j/classes" dir="${build.classes}"
- includes="interop/**, wssec/**, org/**/oasis/**, org/**/samples/**"/>
+ includes="*.properties, interop/**, wssec/**, org/**/oasis/**, org/**/samples/**"/>
<zipfileset prefix="wss4j/doc/api" dir="${build.javadoc}"/>
<zipfileset fullpath="wss4j/${jar.library}" dir="${dir.dist}" includes="${jar.library}"/>
</zip>
1.2 +50 -7 ws-wss4j/README.txt
Index: README.txt
===================================================================
RCS file: /home/cvs/ws-wss4j/README.txt,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- README.txt 9 Jul 2005 20:33:27 -0000 1.1
+++ README.txt 22 Jul 2005 18:58:00 -0000 1.2
@@ -15,13 +15,18 @@
* OASIS Web Serives Security: SOAP Message Security 1.0 Standard 200401,
March 2004
- * Username Token profile V1.0
- * X.509 Token Profile V1.0
+ * Username Token profile V1.0
+ * X.509 Token Profile V1.0
+
+The Web Services Security part of WSS4J is fairl well tested and many
+WebService projects use it already. Also interoperability with
+various other implementations is well tested.
WSS4J can also be configured to emulate previous WSS spec implementations
with older namespaces, such as WebSphere 5.1 and WebLogic 8.1 SP2.
-WS-Security Features
+
+* Web Services Security Features *
WSS4J can generate and process the following SOAP Bindings:
@@ -44,14 +49,52 @@
http://wiki.apache.org/ws/FrontPage/WsFx
-TODO: describe parts Trust, Conversation
+The 'Trust' and 'Conversation' parts of WSS4J implements the WS-Trust
+and WS-Secure Conversation specifications.
+
+Status of these two parts right now:
+ * WS-Trust implementation is in the process of being re-done.
+ * WS-Secure Conversation impl will be re-worked burning the
+ WS-Addressing stuff into it once we have the components of WS-Trust
+ implementation ready.
+
+Introperability of these two parts:
+The SecurityTokenService successfully interoped with IBM's implementation
+last year (Token issuance only). But as of now we cannot confirm
+interoperability due to the changes.
+
+Therefore the 'Trust' and 'Conversation' parts of WSS4J are experimental.
+
+
+* Installation (binary distribution) *
+
+The WSS4J zip archive is the binary distribution and contains the wss4j
+jar file, some examples, test classes (incl. sources), the interop test
+classes (incl. sources and necessary certificate store), and the according
+client and server deployment and protery files.
+
+The WSS4J jar file contains all classes that implement the basic functions
+and the handlers. To install it make sure this jar file is in the classpath
+of your Axis client and/or Axis server. In addition you need to set up
+the property files that contain information about the certificate keystores
+you use. The property files and the keystore are accessed either as
+resources via classpath or, if that fails, as files using the relative path
+of the application
+
+Thus no specific installation is required. The wss4j.jar file could be
+included into ear or war files of enterprise or web application servers.
+
+Please refer to the JAVADOC files of the distribution for further
+information how to use WSS4J, the handlers, and how to setup the
+deployment files.
+
-Required software
+* Required software *
To work with WSS4J you need additional software. Most of
the software is also needed by your SOAP base system, e.g.
-Apache Axis. To implement the Web Service Security (WSS) parts
-specific software is required such. See below.
+Apache Axis. To implement the Web Service Security (WSS) part
+specific software is required:
addressing-1.0.jar
This jar contains the implementation of WS-Adressing, required
---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org