From seam-commits at lists.jboss.org Tue Aug 14 13:20:43 2012
Content-Type: multipart/mixed; boundary="===============2489631549537967922=="
MIME-Version: 1.0
From: seam-commits at lists.jboss.org
To: seam-commits at lists.jboss.org
Subject: [seam-commits] Seam SVN: r15039 -
 branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US.
Date: Tue, 14 Aug 2012 13:20:42 -0400
Message-ID: <201208141720.q7EHKgT8029656@svn01.web.mwc.hst.phx2.redhat.com>

--===============2489631549537967922==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

Author: manaRH
Date: 2012-08-14 13:20:41 -0400 (Tue, 14 Aug 2012)
New Revision: 15039

Modified:
   branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Webse=
rvices.xml
Log:
JBSEAM-5013 webservices updated

Modified: branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-U=
S/Webservices.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Webs=
ervices.xml	2012-08-14 16:42:50 UTC (rev 15038)
+++ branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Webs=
ervices.xml	2012-08-14 17:20:41 UTC (rev 15039)
@@ -2,7 +2,7 @@
   <title>Web Services</title>
 =

   <para>
-    Seam integrates with JBossWS to allow standard JEE web services to tak=
e full advantage of Seam's contextual framework,
+    Seam integrates with JBossWS to allow standard Java EE web services to=
 take full advantage of Seam's contextual framework,
     including support for conversational web services. This chapter walks =
through the steps required to allow web =

     services to run within a Seam environment.
   </para>
@@ -17,28 +17,20 @@
     </para>
     =

     <para>
-      A special configuration file, <literal>standard-jaxws-endpoint-confi=
g.xml</literal> should be placed =

+      A special configuration file, <literal>soap-handlers.xml</literal> s=
hould be placed =

       into the <literal>META-INF</literal> directory of the <literal>jar</=
literal> file that contains the =

       web service classes.  This file contains the following SOAP handler =
configuration:
     </para>
     =

-    <programlisting role=3D"XML"><![CDATA[<jaxws-config xmlns=3D"urn:jboss=
:jaxws-config:2.0" =

-              xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" =

-              xmlns:javaee=3D"http://java.sun.com/xml/ns/javaee"
-              xsi:schemaLocation=3D"urn:jboss:jaxws-config:2.0 jaxws-confi=
g_2_0.xsd">
-   <endpoint-config>
-      <config-name>Seam WebService Endpoint</config-name>
-      <pre-handler-chains>
-         <javaee:handler-chain>
-            <javaee:protocol-bindings>##SOAP11_HTTP</javaee:protocol-bindi=
ngs>
-            <javaee:handler>
-               <javaee:handler-name>SOAP Request Handler</javaee:handler-n=
ame>
-               <javaee:handler-class>org.jboss.seam.webservice.SOAPRequest=
Handler</javaee:handler-class>
-            </javaee:handler>
-         </javaee:handler-chain>
-      </pre-handler-chains>
-   </endpoint-config>
-</jaxws-config>]]></programlisting>
+    <programlisting role=3D"XML"><![CDATA[<?xml version=3D"1.0" encoding=
=3D"UTF-8"?>
+<handler-chains xmlns=3D"http://java.sun.com/xml/ns/javaee">
+  <handler-chain>
+    <handler>
+      <handler-name>SOAP Request Handler</handler-name>
+      <handler-class>org.jboss.seam.webservice.SOAPRequestHandler</handler=
-class>
+    </handler>
+  </handler-chain>
+</handler-chains>]]></programlisting>
 =

   </sect1>
   =

@@ -51,19 +43,21 @@
     </para>
     =

     <programlisting role=3D"XML"><![CDATA[<soapenv:Envelope xmlns:soapenv=
=3D"http://schemas.xmlsoap.org/soap/envelope/" =

-    xmlns:seam=3D"http://seambay.example.seam.jboss.org/">
+    xmlns:sb=3D"http://seambay.example.seam.jboss.org/">
   <soapenv:Header>
-    <seam:conversationId xmlns:seam=3D'http://www.jboss.org/seam/webservic=
e'>2</seam:conversationId>
+    <seam:conversationId xmlns:seam=3D'http://www.jboss.org/seam/webservic=
e'>4</seam:conversationId>
   </soapenv:Header>
   <soapenv:Body>
-    <seam:confirmAuction/>
+    <sb:setAuctionPrice>
+      <arg0>100</arg0>
+    </sb:setAuctionPrice>
   </soapenv:Body>
-</soapenv:Envelope>    =

+</soapenv:Envelope>
     ]]></programlisting>
     =

     <para>
       As you can see in the above SOAP message, there is a <literal>conver=
sationId</literal> element within the
-      SOAP header that contains the conversation ID for the request, in th=
is case <literal>2</literal>.  =

+      SOAP header that contains the conversation ID for the request, in th=
is case <literal>4</literal>.  =

       Unfortunately, because web services may be consumed by a variety of =
web service clients written in a =

       variety of languages, it is up to the developer to implement convers=
ation ID propagation between individual =

       web services that are intended to be used within the scope of a sing=
le conversation.
@@ -75,14 +69,14 @@
       able to read the conversation ID from the request. Here's an example=
 of a response to the above request message:
     </para>
     =

-    <programlisting role=3D"XML"><![CDATA[<env:Envelope xmlns:env=3D'http:=
//schemas.xmlsoap.org/soap/envelope/'>
-  <env:Header>
-    <seam:conversationId xmlns:seam=3D'http://www.jboss.org/seam/webservic=
e'>2</seam:conversationId>
-  </env:Header>
-  <env:Body>
-    <confirmAuctionResponse xmlns=3D"http://seambay.example.seam.jboss.org=
/"/>
-  </env:Body>
-</env:Envelope>    =

+    <programlisting role=3D"XML"><![CDATA[<soap:Envelope xmlns:soap=3D"htt=
p://schemas.xmlsoap.org/soap/envelope/">
+    <soap:Header>
+        <seam:conversationId xmlns:seam=3D"http://www.jboss.org/seam/webse=
rvice">4</seam:conversationId>
+    </soap:Header>
+    <soap:Body>
+        <ns2:setAuctionPriceResponse xmlns:ns2=3D"http://seambay.example.s=
eam.jboss.org/"/>
+    </soap:Body>
+ </soap:Envelope>    =

     ]]></programlisting>
     =

     <para>
@@ -127,7 +121,9 @@
     </para>
 =

     <programlisting role=3D"JAVA"><![CDATA[@Stateless
-(a)WebService(name =3D "AuctionService", serviceName =3D "AuctionService")
+(a)Name("auctionService")
+(a)WebService(name =3D "AuctionService")
+(a)HandlerChain(file =3D "soap-handlers.xml")
 public class AuctionService implements AuctionServiceRemote
 {
    @WebMethod


--===============2489631549537967922==--