Author: coheigea
Date: Thu Jun 14 10:52:02 2012
New Revision: 1350186
URL: http://svn.apache.org/viewvc?rev=1350186&view=rev
Log:
Minor spelling fixes to the sample READMEs
Modified:
cxf/trunk/distribution/src/main/release/samples/corba/bank/README.txt
cxf/trunk/distribution/src/main/release/samples/jax_rs/basic_https/README.txt
cxf/trunk/distribution/src/main/release/samples/jaxws_dispatch_provider/README.txt
cxf/trunk/distribution/src/main/release/samples/oauth/README.txt
cxf/trunk/distribution/src/main/release/samples/ws_security/ut/README.txt
Modified: cxf/trunk/distribution/src/main/release/samples/corba/bank/README.txt
URL:
http://svn.apache.org/viewvc/cxf/trunk/distribution/src/main/release/samples/corba/bank/README.txt?rev=1350186&r1=1350185&r2=1350186&view=diff
==============================================================================
--- cxf/trunk/distribution/src/main/release/samples/corba/bank/README.txt
(original)
+++ cxf/trunk/distribution/src/main/release/samples/corba/bank/README.txt Thu
Jun 14 10:52:02 2012
@@ -3,7 +3,7 @@ CORBA Bank Demo
This demo illustrates the user of JAX-WS API's for creating a service
that uses the CORBA/IIOP protocol for communication. It also
-shows throwing exceptions accross that connection.
+shows throwing exceptions across that connection.
Please review the README in the samples main directory before continuing.
Modified:
cxf/trunk/distribution/src/main/release/samples/jax_rs/basic_https/README.txt
URL:
http://svn.apache.org/viewvc/cxf/trunk/distribution/src/main/release/samples/jax_rs/basic_https/README.txt?rev=1350186&r1=1350185&r2=1350186&view=diff
==============================================================================
---
cxf/trunk/distribution/src/main/release/samples/jax_rs/basic_https/README.txt
(original)
+++
cxf/trunk/distribution/src/main/release/samples/jax_rs/basic_https/README.txt
Thu Jun 14 10:52:02 2012
@@ -18,7 +18,7 @@ certificates.
Likewise the client authenticates the server's certificate "CN=Cherry"
and chain against the same trust store. Note also the usage of the
cipherSuitesFilter configuration in the configuration files,
-where each party imposes different ciphersuites contraints, so that the
+where each party imposes different ciphersuites constraints, so that the
ciphersuite eventually negotiated during the TLS handshake is acceptable
to both sides. This may be viewed by adding a -Djavax.net.debug=all
argument to the JVM.
Modified:
cxf/trunk/distribution/src/main/release/samples/jaxws_dispatch_provider/README.txt
URL:
http://svn.apache.org/viewvc/cxf/trunk/distribution/src/main/release/samples/jaxws_dispatch_provider/README.txt?rev=1350186&r1=1350185&r2=1350186&view=diff
==============================================================================
---
cxf/trunk/distribution/src/main/release/samples/jaxws_dispatch_provider/README.txt
(original)
+++
cxf/trunk/distribution/src/main/release/samples/jaxws_dispatch_provider/README.txt
Thu Jun 14 10:52:02 2012
@@ -3,7 +3,7 @@ JAX-WS Dispatch/Provider Demo
The demo demonstrates the use of JAX-WS Dispatch and Provider interface.
The client side Dispatch instance invokes upon an endpoint using a JAX-WS
-Provider implementor. There are three differnt invocations from the client.
+Provider implementor. There are three different invocations from the client.
The first uses the SOAPMessage data in MESSAGE mode. The second uses the
DOMSource
data in MESSAGE mode. The third uses the DOMSource in PAYLOAD mode. The three
different messages are constructed by reading in the XML files found in the
Modified: cxf/trunk/distribution/src/main/release/samples/oauth/README.txt
URL:
http://svn.apache.org/viewvc/cxf/trunk/distribution/src/main/release/samples/oauth/README.txt?rev=1350186&r1=1350185&r2=1350186&view=diff
==============================================================================
--- cxf/trunk/distribution/src/main/release/samples/oauth/README.txt (original)
+++ cxf/trunk/distribution/src/main/release/samples/oauth/README.txt Thu Jun 14
10:52:02 2012
@@ -5,7 +5,7 @@ The OAuth 1.0a demo that shows protocol'
client:
A web application capable of making OAuth-authenticated requests.
It is a usual OAuth client,
not dependent on Apache CXF framework, built to test this demo
server part and for OAuth
- educational purposes. Implementation works with any OAuth 1.0a
providers, not only inluded
+ educational purposes. Implementation works with any OAuth 1.0a
providers, not only included
in this demo.
@@ -39,7 +39,7 @@ Building and running the demo using mave
Port number is defined in pom.xml.
- Both client and server modules sepends on Spring 3, so you need to use
CXF spring3 profile.
+ Both client and server modules depend on Spring 3, so you need to use
CXF spring3 profile.
You can build both client and server modules using command:
mvn clean install
@@ -54,7 +54,7 @@ When you have successfully deployed clie
3. You have registered client application at the OAuth server, with associated
and displayed
client identifier, client shared-secret and callback url. You will need
those on the client side.
4. Go to OAuth client demo (http://localhost:8080) and provide information
about the registered application.
-5. Perform usuall OAuth 1.0 flow steps
+5. Perform usual OAuth 1.0 flow steps
Modified:
cxf/trunk/distribution/src/main/release/samples/ws_security/ut/README.txt
URL:
http://svn.apache.org/viewvc/cxf/trunk/distribution/src/main/release/samples/ws_security/ut/README.txt?rev=1350186&r1=1350185&r2=1350186&view=diff
==============================================================================
--- cxf/trunk/distribution/src/main/release/samples/ws_security/ut/README.txt
(original)
+++ cxf/trunk/distribution/src/main/release/samples/ws_security/ut/README.txt
Thu Jun 14 10:52:02 2012
@@ -49,7 +49,7 @@ Using either UNIX or Windows:
mvn install (builds the demo)
mvn -Pserver (from one command line window)
- Mvn -Pclient (from a second command line window)
+ mvn -Pclient (from a second command line window)
On startup, the client makes a sequence of 4 two-way invocations.
