[jboss-cvs] JBossAS SVN: r102499 - projects/docs/enterprise/5.0.1/Administration_And_Configuration_Guide/en-US.

Wed Mar 17 00:06:00 EDT 2010

Author: laubai
Date: 2010-03-17 00:05:59 -0400 (Wed, 17 Mar 2010)
New Revision: 102499

Modified:
   projects/docs/enterprise/5.0.1/Administration_And_Configuration_Guide/en-US/Web_Services.xml
Log:
Updates for JBPAPP-3916, JBPAPP-3914.

Modified: projects/docs/enterprise/5.0.1/Administration_And_Configuration_Guide/en-US/Web_Services.xml
===================================================================

--- projects/docs/enterprise/5.0.1/Administration_And_Configuration_Guide/en-US/Web_Services.xml	2010-03-17 03:59:54 UTC (rev 102498)
+++ projects/docs/enterprise/5.0.1/Administration_And_Configuration_Guide/en-US/Web_Services.xml	2010-03-17 04:05:59 UTC (rev 102499)
@@ -235,7 +235,7 @@
 	
 	<section><title>RPC/Encoded</title>
 		<para>
-			SOAP encodeding style is defined by the infamous <ulink url="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/#_Toc478383512">chapter 5</ulink> of the <ulink url="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/">SOAP-1.1</ulink> specification. It has inherent interoperability issues that cannot be fixed. The <ulink url="http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html">Basic Profile-1.0</ulink> prohibits this encoding style in <ulink url="http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html#refinement16448072">4.1.7 SOAP encodingStyle Attribute</ulink>. 
+			SOAP encoding style is defined by <ulink url="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/#_Toc478383512">chapter 5</ulink> of the <ulink url="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/">SOAP-1.1</ulink> specification. It has inherent interoperability issues that cannot be fixed. The <ulink url="http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html">Basic Profile-1.0</ulink> prohibits this encoding style in <ulink url="http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html#refinement16448072">4.1.7 SOAP encodingStyle Attribute</ulink>. 
 			
 			JBossWS has basic support for RPC/Encoded that is provided as is for simple interop scenarios with SOAP stacks that do not support literal encoding.
 			Specifically, JBossWS does not support:-
@@ -327,11 +327,11 @@
 		
 <screen>http://yourhost:8080/jbossws/services</screen>
 <para>
-It is also possible to generate the abstract contract off line using jboss tools. For details of that see <ulink url="http://www.jboss.org/community/wiki/JBossWS-JAX-WSTools#TopDown_Using_wsconsume">#Top Down (Using wsconsume)</ulink></para>
+It is also possible to generate the abstract contract off line using jboss tools. For details of that see <ulink url="http://www.jboss.org/community/wiki/JBossWS-JAX-WSTools#TopDown_Using_wsconsume">Top Down (Using wsconsume)</ulink></para>
 	</section>
 	<section>
 		<title>EJB3 Stateless Session Bean (SLSB)</title>
-		<para>The JAX-WS programming model support the same set of annotations on EJB3 stateless session beans as on <ulink url="http://www.jboss.org/community/wiki/JBossWS-UserGuide#Plain_old_Java_Object_POJO"># Plain old Java Object (POJO)</ulink> endpoints. EJB-2.1 endpoints are supported using the JAX-RPC progamming model.</para>
+		<para>The JAX-WS programming model support the same set of annotations on EJB3 stateless session beans as on <ulink url="http://www.jboss.org/community/wiki/JBossWS-UserGuide#Plain_old_Java_Object_POJO">Plain old Java Object (POJO)</ulink> endpoints. EJB-2.1 endpoints are supported using the JAX-RPC progamming model.</para>
 <programlisting role="JAVA">
 @Stateless
 @Remote(EJB3RemoteInterface.class)
@@ -367,7 +367,7 @@
 		</formalpara>
 <programlisting> <![CDATA[
   http://yourhost:8080/jbossws/services]]> </programlisting>
-		<para>It is also possible to generate the abstract contract offline using JbossWS tools. For details of that please see <ulink url="http://www.jboss.org/community/wiki/JBossWS-JAX-WSTools#TopDown_Using_wsconsume">#Top Down (Using wsconsume)</ulink></para>
+		<para>It is also possible to generate the abstract contract offline using JbossWS tools. For details of that please see <ulink url="http://www.jboss.org/community/wiki/JBossWS-JAX-WSTools#TopDown_Using_wsconsume">Top Down (Using wsconsume)</ulink></para>
 	</section>
 	<section>
 		<title>Endpoint Provider</title>
@@ -451,7 +451,7 @@
   
    ...
 }</programlisting>
-				<para>Section <ulink url="http://www.jboss.org/community/wiki/JBossWS-UserGuide#Dynamic_Proxy">#Dynamic Proxy</ulink> explains how to obtain a port from the service and how to invoke an operation on the port. If you need to work with the XML payload directly or with the XML representation of the entire SOAP message, have a look at <ulink url="http://www.jboss.org/community/wiki/JBossWS-UserGuide#Dispatch">#Dispatch</ulink>.</para>
+				<para>Section <ulink url="http://www.jboss.org/community/wiki/JBossWS-UserGuide#Dynamic_Proxy">Dynamic Proxy</ulink> explains how to obtain a port from the service and how to invoke an operation on the port. If you need to work with the XML payload directly or with the XML representation of the entire SOAP message, have a look at <ulink url="http://www.jboss.org/community/wiki/JBossWS-UserGuide#Dispatch">Dispatch</ulink>.</para>
 				<formalpara>
 					<title>Dynamic case</title>
 					<para>In the dynamic case, when nothing is generated, a web service client uses <literal>Service.create</literal> to create Service instances, the following code illustrates this process.</para>
@@ -676,7 +676,7 @@
 	</section>
 	<section>
 		<title>Common API</title>
-		<para>This sections describes concepts that apply equally to <ulink url="http://www.jboss.org/community/wiki/JBossWS-UserGuide#Web_Service_Endpoints">#Web Service Endpoints</ulink> and <ulink url="http://www.jboss.org/community/wiki/JBossWS-UserGuide#Web_Service_Clients">#Web Service Clients</ulink></para>
+		<para>This sections describes concepts that apply equally to <ulink url="http://www.jboss.org/community/wiki/JBossWS-UserGuide#Web_Service_Endpoints">Web Service Endpoints</ulink> and <ulink url="http://www.jboss.org/community/wiki/JBossWS-UserGuide#Web_Service_Clients">Web Service Clients</ulink></para>
 		<section>
 			<title>Handler Framework</title>
 			<para>The handler framework is implemented by a JAX-WS protocol binding in both client and server side runtimes. Proxies, and Dispatch instances, known collectively as binding providers, each use protocol bindings to bind their abstract functionality to specific protocols.</para>


