cxf-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cohei...@apache.org
Subject svn commit: r1429759 - /cxf/branches/2.6.x-fixes/distribution/src/main/release/samples/wsdl_first_xmlbeans/README.txt
Date Mon, 07 Jan 2013 11:52:28 GMT
Author: coheigea
Date: Mon Jan  7 11:52:27 2013
New Revision: 1429759

URL: http://svn.apache.org/viewvc?rev=1429759&view=rev
Log:
README cleanup


Conflicts:
	distribution/src/main/release/samples/wsdl_first/README.txt

Modified:
    cxf/branches/2.6.x-fixes/distribution/src/main/release/samples/wsdl_first_xmlbeans/README.txt

Modified: cxf/branches/2.6.x-fixes/distribution/src/main/release/samples/wsdl_first_xmlbeans/README.txt
URL: http://svn.apache.org/viewvc/cxf/branches/2.6.x-fixes/distribution/src/main/release/samples/wsdl_first_xmlbeans/README.txt?rev=1429759&r1=1429758&r2=1429759&view=diff
==============================================================================
--- cxf/branches/2.6.x-fixes/distribution/src/main/release/samples/wsdl_first_xmlbeans/README.txt
(original)
+++ cxf/branches/2.6.x-fixes/distribution/src/main/release/samples/wsdl_first_xmlbeans/README.txt
Mon Jan  7 11:52:27 2013
@@ -1,8 +1,9 @@
 Hello World Demo using Document/Literal Style and XMLBeans
 ==========================================================
 
-This demo illustrates the use of the JAX-WS APIs and with the XMLBeans data binding
-to run a simple client against a standalone server using SOAP 1.1 over HTTP.
+This demo illustrates the use of the JAX-WS APIs and with the XMLBeans data
+binding to run a simple client against a standalone server using SOAP 1.1 over
+HTTP.
 
 It also shows how CXF configuration can be used to enable schema validation
 on the client and/or server side: By default the message parameters would not
@@ -10,19 +11,23 @@ be validated, but the presence of the cx
 the classpath, and its content change this default behavior:
 The configuration file specifies that 
 
-a) if a JAX-WS client proxy is created for port {http://apache.org/hello_world_soap_http}SoapPort
-it should have schema validation enabled.
-
-b) if a JAX-WS server endpoint is created for port {http://apache.org/hello_world_soap_http}SoapPort
-it should have schema validation enabled.
+a) if a JAX-WS client proxy is created for port
+{http://apache.org/hello_world_soap_http}SoapPort it should have schema
+validation enabled.
+
+b) if a JAX-WS server endpoint is created for port
+{http://apache.org/hello_world_soap_http}SoapPort it should have schema
+validation enabled.
 
 The client's second greetMe invocation causes an exception (a marshalling
 error) on the client side, i.e. before the request with the invalid parameter
 goes on the wire.
+
 After commenting the definition of the <jaxws:client> element in cxf.xml you 
-will notice that the client's second greetMe invocation still throws an exception,
-but that this time the exception is caused by an unmarshalling error on the
-server side.
+will notice that the client's second greetMe invocation still throws an
+exception, but that this time the exception is caused by an unmarshalling
+error on the server side.
+
 Commenting both elements, or renaming/removing the cfg.xml file, and thus
 restoring the default behavior, results in the second greetMe invocation
 not causing an exception.



Mime
View raw message