[jboss-svn-commits] JBL Code SVN: r34478 - in labs/jbossesb/trunk/product/docs/Programmers_Guide/en-US: OOB-Actions and 1 other directory.

[jboss-svn-commits at lists.jboss.org]

Author: mageshbk at jboss.com
Date: 2010-08-03 07:13:16 -0400 (Tue, 03 Aug 2010)
New Revision: 34478

Modified:
   labs/jbossesb/trunk/product/docs/Programmers_Guide/en-US/OOB-Actions/OOB_Actions_webservices_SOAP.xml
   labs/jbossesb/trunk/product/docs/Programmers_Guide/en-US/Web_Services_Support.xml
Log:
[JBESB-3401] - Updated documentation about CXF support.

Modified: labs/jbossesb/trunk/product/docs/Programmers_Guide/en-US/OOB-Actions/OOB_Actions_webservices_SOAP.xml
===================================================================
--- labs/jbossesb/trunk/product/docs/Programmers_Guide/en-US/OOB-Actions/OOB_Actions_webservices_SOAP.xml	2010-08-03 10:26:06 UTC (rev 34477)
+++ labs/jbossesb/trunk/product/docs/Programmers_Guide/en-US/OOB-Actions/OOB_Actions_webservices_SOAP.xml	2010-08-03 11:13:16 UTC (rev 34478)
@@ -25,6 +25,11 @@
         means that these Services are invocable over any transport channel supported by 
         the ESB (http, ftp, jms etc.).
         </para>
+		<note>
+			<para>
+				SOAPProcessor supports both JBossWS-Native and JBossWS-CXF stacks.
+			</para>
+		</note>
 
         <section id="sect-webservicessoap-soapprocessor-action-configuration">
             <title>SOAPProcessor Action Configuration</title>
@@ -86,12 +91,13 @@
         <section id="sect-webservicessoap-esb-message-aware-webservice-endpoints">
             <title>"ESB Message Aware" Webservice Endpoints</title>
             <para>
-            Note that Webservice endpoints exposed via this action have direct access 
+            Note that JBossWS-Native Webservice endpoints exposed via this action have direct access 
             to the current JBossESB Message instance used to invoke this action's 
             process(Message) method. It can access the current Message instance via 
             the SOAPProcessor.getMessage() method and can change the Message instance 
-            via the SOAPProcessor.setMessage(Message) method. This means that Webservice 
-            endpoints exposed via this action are "ESB Message Aware".
+            via the SOAPProcessor.setMessage(Message) method. This means that JBossWS-Native Webservice 
+            endpoints exposed via this action are "ESB Message Aware". However, JBossWS-CXF 
+            Webservice endpoints are not "ESB Message Aware".
             </para>
         </section>
         

Modified: labs/jbossesb/trunk/product/docs/Programmers_Guide/en-US/Web_Services_Support.xml
===================================================================
--- labs/jbossesb/trunk/product/docs/Programmers_Guide/en-US/Web_Services_Support.xml	2010-08-03 10:26:06 UTC (rev 34477)
+++ labs/jbossesb/trunk/product/docs/Programmers_Guide/en-US/Web_Services_Support.xml	2010-08-03 11:13:16 UTC (rev 34478)
@@ -18,7 +18,8 @@
 		</title>
 	
 		<para>
-		    JBossESB has a number of Webservice based components for
+		    JBossESB supports both JBossWS-Native and JBossWS-CXF stacks.
+			JBossESB has a number of Webservice based components for
 		    exposing and invoking Webservice endpoints (i.e. SOAP onto the
 		    bus and SOAP off the bus):
 		</para>
@@ -38,6 +39,11 @@
                         Endpoints over any transport channel supported by
                         the ESB.
 					</para>					                    
+                    <caution>
+                        <para>
+                            JBossWS-CXF Endpoints are not "ESB Message Aware”.
+                        </para>
+                    </caution>
 				</listitem>				
 			
 				<listitem>
@@ -57,9 +63,7 @@
 
                 <para>
                     You can also find more information within the wiki
-                    pages shipped with the JBossESB documentation. At the
-                    moment JBossESB supports both JBossWS-Native and
-                    JbossWS-CXF stacks.
+                    pages shipped with the JBossESB documentation.
                 </para>
         </note>