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
===================================================================
--- 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 @@
-<?xml version="1.0" encoding="UTF-8"?><chapter
id="chap_JBossWS-UserGuide"><title>JBossWS-UserGuide</title><para/><section
id="JBossWS-UserGuide_Introduction_and_architecture"><title>Introduction
and architecture</title><para> </para><para>The high level
architecture of the JBossWS Web Service Framework is presented in the image here
below:</para><para><ulink
url="http://jboss.org/file-access/default/members/jbossws/images/wsf...
fileref="images/wsf.png" depth="436"
width="579"/></imageobject></mediaobject></ulink></para><para> </para><para>This
basically means users can choose to download, install and use three different JBossWS
versions:</para><itemizedlist><listitem><para><emphasis
role="bold">JBossWS Native</emphasis>: this is the JBossWS Web Service
Framework integrating the original JBossWS native stack that has been developed in the
past years. This is what currently comes installed by default in every JBoss Application
Server!
released version and has been used on top of JBoss AS 5 to make it successfully
certified for Java EE 5. Please refer the <link
linkend="chap_JBossWS-NativeUserGuide">JBossWS Native stack user
guide</link> for a complete documentation of JBossWS-Native specific
features.</para></listitem><listitem><para><emphasis
role="bold">JBossWS CXF</emphasis>: this is the JBossWS Web Service
Framework integrating the <ulink
url="http://cxf.apache.org/">Apache
CXF</ulink> web service stack. Please refer the <ulink
url="http://community.jboss.org/docs/DOC-13562">JBossWS CXF stack user
guide</ulink> for a complete documentation of JBossWS-CXF specific
features.</para></listitem><listitem><para><emphasis
role="bold">JBossWS Metro</emphasis>: this is the JBossWS Web Service
Framework integrating the <ulink
url="https://metro.dev.java.net/">GlassFish Metro</ulink> web service
stack. Please refer the <ulink
url="http://community.jboss.org/docs/DOC-13561">JBossWS Metro stack user
guide</ulink!
for a complete documentation of JBossWS-Metro specific featu!
res.</pa
ra></listitem></itemizedlist><para> </para><para>The
JBossWS web service framework provides common features, tooling, management, deployment
framework, etc. for all the supported stacks. At the same time, each stack comes with its
own specific functional feature set, performance characteristics and -of course-
community. So users can definitely choose the stack that best suits their needs and
successfully use it on top of JBoss Application
Server.</para><para> </para></section>
+<?xml version="1.0" encoding="UTF-8"?><chapter
id="chap_JBossWS-UserGuide"><title>JBossWS-UserGuide</title><para/>
<section id="JBossWS-UserGuide_Common_User_Guide"><title>Common
User Guide</title><para> </para><para>Here below is the
documentation that applies to every supported stacks. This includes basic JAX-WS usage as
well as references to common additional functionalities the JBossWS Web Service Framework
provides on top of the supported stacks.</para><section
id="JBossWS-UserGuide_Web_Service_Concepts"><title>Web Service
Concepts</title><section
id="JBossWS-UserGuide_DocumentLiteral"><title>Document/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 other responds (immediately or later) with a
document that describes the status of the purchase order. No need to agree on such low
level details as operation names and their associated
parameters.</para><para>The payload of the 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:space="preserve"> <binding name='EndpointInterfaceBinding'
type='tns:EndpointInterface'>
<soap:binding style='document' transport='<ulink
url="http://schemas.xmlsoap.org/soap/http'/">http://sche...
<operation name='concat'>