Author: coheigea
Date: Mon Jan 7 11:55:43 2013
New Revision: 1429763
URL: http://svn.apache.org/viewvc?rev=1429763&view=rev
Log:
Merged revisions 1429759 via git cherry-pick from
https://svn.apache.org/repos/asf/cxf/branches/2.6.x-fixes
........
r1429759 | coheigea | 2013-01-07 11:52:27 +0000 (Mon, 07 Jan 2013) | 6 lines
README cleanup
Conflicts:
distribution/src/main/release/samples/wsdl_first/README.txt
........
Modified:
cxf/branches/2.5.x-fixes/distribution/src/main/release/samples/wsdl_first_xmlbeans/README.txt
Modified:
cxf/branches/2.5.x-fixes/distribution/src/main/release/samples/wsdl_first_xmlbeans/README.txt
URL:
http://svn.apache.org/viewvc/cxf/branches/2.5.x-fixes/distribution/src/main/release/samples/wsdl_first_xmlbeans/README.txt?rev=1429763&r1=1429762&r2=1429763&view=diff
==============================================================================
---
cxf/branches/2.5.x-fixes/distribution/src/main/release/samples/wsdl_first_xmlbeans/README.txt
(original)
+++
cxf/branches/2.5.x-fixes/distribution/src/main/release/samples/wsdl_first_xmlbeans/README.txt
Mon Jan 7 11:55:43 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.
