From jbossws-commits at lists.jboss.org Wed Nov 3 03:52:01 2010 Content-Type: multipart/mixed; boundary="===============6641453108968395504==" MIME-Version: 1.0 From: jbossws-commits at lists.jboss.org To: jbossws-commits at lists.jboss.org Subject: [jbossws-commits] JBossWS SVN: r13203 - stack/native/trunk/src/main/doc. Date: Wed, 03 Nov 2010 03:52:01 -0400 Message-ID: <201011030752.oA37q1lh000967@svn01.web.mwc.hst.phx2.redhat.com> --===============6641453108968395504== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Author: alessio.soldano(a)jboss.com Date: 2010-11-03 03:52:01 -0400 (Wed, 03 Nov 2010) New Revision: 13203 Modified: stack/native/trunk/src/main/doc/JBossWS-UserGuide.xml Log: [JBWS-2215] Fix to common user guide Modified: stack/native/trunk/src/main/doc/JBossWS-UserGuide.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 --- stack/native/trunk/src/main/doc/JBossWS-UserGuide.xml 2010-11-02 19:25:= 45 UTC (rev 13202) +++ stack/native/trunk/src/main/doc/JBossWS-UserGuide.xml 2010-11-03 07:52:= 01 UTC (rev 13203) @@ -1,4 +1,4 @@ -JBossWS-UserGuide
Introduction and architecture</ti= tle><para>=C2=A0</para><para>The high level architecture of the JBossWS Web= Service Framework is presented in the image here below:</para><para><ulink= url=3D"http://jboss.org/file-access/default/members/jbossws/images/wsf.png= "><mediaobject><imageobject><imagedata fileref=3D"images/wsf.png" depth=3D"= 436" width=3D"579"/></imageobject></mediaobject></ulink></para><para>=C2=A0= </para><para>This basically means users can choose to download, install and= use three different JBossWS versions:</para><itemizedlist><listitem><para>= <emphasis role=3D"bold">JBossWS Native</emphasis>: this is the JBossWS Web = Service Framework integrating the original JBossWS native stack that has be= en developed in the past years. This is what currently comes installed by d= efault in every JBoss Application Server! released version and has been used on top of JBoss AS 5 to make it succes= sfully certified for Java EE 5. Please refer the <link linkend=3D"chap_JBos= sWS-NativeUserGuide">JBossWS Native stack user guide</link> for a complete = documentation of JBossWS-Native specific features.</para></listitem><listit= em><para><emphasis role=3D"bold">JBossWS CXF</emphasis>: this is the JBossW= S Web Service Framework integrating the <ulink url=3D"http://cxf.apache.org= /">Apache CXF</ulink> web service stack. Please refer the <ulink url=3D"htt= p://community.jboss.org/docs/DOC-13562">JBossWS CXF stack user guide</ulink= > for a complete documentation of JBossWS-CXF specific features.</para></li= stitem><listitem><para><emphasis role=3D"bold">JBossWS Metro</emphasis>: th= is is the JBossWS Web Service Framework integrating the <ulink url=3D"https= ://metro.dev.java.net/">GlassFish Metro</ulink> web service stack. Please r= efer the <ulink url=3D"http://community.jboss.org/docs/DOC-13561">JBossWS M= etro stack user guide</ulink! > for a complete documentation of JBossWS-Metro specific featu! res.</pa ra></listitem></itemizedlist><para>=C2=A0</para><para>The JBossWS web servi= ce framework provides common features, tooling, management, deployment fram= ework, etc. for all the supported stacks. At the same time, each stack come= s with its own specific functional feature set, performance characteristics= and -of course- community. So users can definitely choose the stack that b= est suits their needs and successfully use it on top of JBoss Application S= erver.</para><para>=C2=A0</para></section> +<?xml version=3D"1.0" encoding=3D"UTF-8"?><chapter id=3D"chap_JBossWS-User= Guide"><title>JBossWS-UserGuide
Common User Gui= de=C2=A0Here below is the documentation that app= lies to every supported stacks. This includes basic JAX-WS usage as well as= references to common additional functionalities the JBossWS Web Service Fr= amework provides on top of the supported stacks.
Web Service ConceptsDocument/Literal</title= ><para>With document style web services two business partners agree on the = exchange of complex business documents that are well defined in XML schema.= For example, one party sends a document describing a purchase order, the o= ther responds (immediately or later) with a document that describes the sta= tus of the purchase order. No need to agree on such low level details as op= eration names and their associated parameters.</para><para>The payload of t= he SOAP message is an XM! L document that can be validated against XML schema.</para><para>Document = is defined by the style attribute on the SOAP binding.</para><screen xml:sp= ace=3D"preserve"> <binding name=3D'EndpointInterfaceBinding' type=3D'tns= :EndpointInterface'> =C2=A0 <soap:binding style=3D'document' transport=3D'<ulink url=3D"http= ://schemas.xmlsoap.org/soap/http'/">http://schemas.xmlsoap.org/soap/http'/<= /ulink>> =C2=A0 <operation name=3D'concat'> --===============6641453108968395504==--