From 4cf07f75604bd0a95d8492694bc57dd49e4a720e Mon Sep 17 00:00:00 2001
From: Arjen Poutsma <apoutsma@vmware.com>
Date: Fri, 18 May 2007 21:37:51 +0000
Subject: [PATCH] Docs

---
 src/docbkx/index.xml  | 13 ++++---------
 src/docbkx/server.xml | 11 ++++++++---
 2 files changed, 12 insertions(+), 12 deletions(-)

diff --git a/src/docbkx/index.xml b/src/docbkx/index.xml
index 004830bd..5e052f2a 100644
--- a/src/docbkx/index.xml
+++ b/src/docbkx/index.xml
@@ -5,9 +5,9 @@
 
 	<bookinfo>
 		<title>Spring Web Services - Reference Documentation</title>
-		<releaseinfo>
-			&version;
-		</releaseinfo>
+      <!-- <releaseinfo> -->
+      <!--  &version; -->
+      <!-- </releaseinfo> -->
 
 		<authorgroup>
 			<author>
@@ -57,12 +57,7 @@
             </para>
         </partintro>
         <xi:include href="common.xml" />
-    
-    	<chapter id="server">
-    		<title>Document-driven Web services with Spring-WS</title>
-    		<para>This chapter will contain the reference for server-side Spring-WS usage.</para>
-    	</chapter>
-    	<!--<xi:include href="server.xml" />-->
+        <xi:include href="server.xml" />
     	<xi:include href="client.xml" />
     	<xi:include href="security.xml" />
     	<xi:include href="oxm.xml" />
diff --git a/src/docbkx/server.xml b/src/docbkx/server.xml
index 89164541..3e8ecb9b 100644
--- a/src/docbkx/server.xml
+++ b/src/docbkx/server.xml
@@ -394,7 +394,7 @@ public class AnnotationOrderEndpoint {
                 endpoint. Because the endpoint class can have multiple request handling methods, we need to instruct
                 Spring-WS which method to invoke for which request. This is done using the
                 <interfacename>@PayloadRoot</interfacename> annotation: the <methodname>getOrder</methodname> method
-                will be invoked for requests with a <literal>orderRequest</literal> local name, and a
+                will be invoked for requests with a <literal>orderRequest</literal> local name and a
                 <uri>http://samples</uri> namespace URI; the <methodname>order</methodname> method for requests with
                 a <literal>order</literal> local name. For more information about these annotations, refer to
                 <xref linkend="server-method-endpoint-mapping"/>.
@@ -415,7 +415,12 @@ public class AnnotationOrderEndpoint {
     </bean>
 
     <bean id="marshaller" class="org.springframework.oxm.jaxb.Jaxb2Marshaller">
-        <property name="contextPath" value="samples"/>
+        <property name="classesToBeBound">
+            <list>
+                <value>samples.OrderRequest</value>
+                <value>samples.Order</value>
+            </list>
+        </property>        
     </bean>
 
     <bean class="org.springframework.ws.server.endpoint.mapping.PayloadRootAnnotationMethodEndpointMapping"/>
@@ -432,7 +437,7 @@ public class AnnotationOrderEndpoint {
                 <para>
                     As an alternative to using marshalling, we could have used <link linkend="xpath">XPath</link> to
                     extract the information out of the incoming XML request. Spring-WS offers another annotation for
-                    this purpose: <interfacename>@XPathParam</interfacename>. You simply annotate a method paramters
+                    this purpose: <interfacename>@XPathParam</interfacename>. You simply annotate method parameters
                     with this annotation, and it will be bound with the evaluation of that annotation.
                     Here is an example:
                 </para>