camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r846287 - in /websites/production/camel/content: book-component-appendix.html book-in-one-page.html cache/main.pageCache cxf.html
Date Sat, 12 Jan 2013 04:30:58 GMT
Author: buildbot
Date: Sat Jan 12 04:30:57 2013
New Revision: 846287

Log:
Production update by buildbot for camel

Modified:
    websites/production/camel/content/book-component-appendix.html
    websites/production/camel/content/book-in-one-page.html
    websites/production/camel/content/cache/main.pageCache
    websites/production/camel/content/cxf.html

Modified: websites/production/camel/content/book-component-appendix.html
==============================================================================
--- websites/production/camel/content/book-component-appendix.html (original)
+++ websites/production/camel/content/book-component-appendix.html Sat Jan 12 04:30:57 2013
@@ -1925,7 +1925,7 @@ cxf:bean:cxfEndpoint?wsdlURL=wsdl/hello_
 
 <div class="confluenceTableSmall"></div>
 <div class="table-wrap">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> DataFormat </th><th colspan="1" rowspan="1" class="confluenceTh">
Description </th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>POJO</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
POJOs (Plain old Java objects) are the Java parameters to the method being invoked on the
target server.  Both Protocol and Logical JAX-WS handlers are supported. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>PAYLOAD</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>PAYLOAD</tt> is the message
payload (the contents of the <tt>soap:body</tt>) after message configuration in
the CXF endpoint is applied.  Only Protocol JAX-WS handler is supported.  Logical JAX-WS handler
is not supported. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>MESSAGE</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>MESSAGE</tt> is the 
 raw message that is received from the transport layer. It is not suppose to touch or change
Stream, so you can't see any soap headers after the camel-cxf consumer and JAX-WS handler
is not supported. </td></tr></tbody></table>
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> DataFormat </th><th colspan="1" rowspan="1" class="confluenceTh">
Description </th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>POJO</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
POJOs (Plain old Java objects) are the Java parameters to the method being invoked on the
target server.  Both Protocol and Logical JAX-WS handlers are supported. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>PAYLOAD</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>PAYLOAD</tt> is the message
payload (the contents of the <tt>soap:body</tt>) after message configuration in
the CXF endpoint is applied.  Only Protocol JAX-WS handler is supported.  Logical JAX-WS handler
is not supported. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>MESSAGE</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>MESSAGE</tt> is the 
 raw message that is received from the transport layer. It is not suppose to touch or change
Stream, some of the CXF interceptor will be removed if you are using this kind of DataFormat
so you can't see any soap headers after the camel-cxf consumer and JAX-WS handler is not supported.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>CXF_MESSAGE</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> New in <b>Camel 2.8.2</b>,
<tt>CXF_MESSAGE</tt> is try to invoke the full feature of CXF interceptors by
turning the message from the transport layer into a raw SOAP message from the transport layer</td></tr></tbody></table>
 </div>
 
 

Modified: websites/production/camel/content/book-in-one-page.html
==============================================================================
--- websites/production/camel/content/book-in-one-page.html (original)
+++ websites/production/camel/content/book-in-one-page.html Sat Jan 12 04:30:57 2013
@@ -22107,7 +22107,7 @@ cxf:bean:cxfEndpoint?wsdlURL=wsdl/hello_
 
 <div class="confluenceTableSmall"></div>
 <div class="table-wrap">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> DataFormat </th><th colspan="1" rowspan="1" class="confluenceTh">
Description </th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>POJO</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
POJOs (Plain old Java objects) are the Java parameters to the method being invoked on the
target server.  Both Protocol and Logical JAX-WS handlers are supported. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>PAYLOAD</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>PAYLOAD</tt> is the message
payload (the contents of the <tt>soap:body</tt>) after message configuration in
the CXF endpoint is applied.  Only Protocol JAX-WS handler is supported.  Logical JAX-WS handler
is not supported. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>MESSAGE</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>MESSAGE</tt> is the 
 raw message that is received from the transport layer. It is not suppose to touch or change
Stream, so you can't see any soap headers after the camel-cxf consumer and JAX-WS handler
is not supported. </td></tr></tbody></table>
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> DataFormat </th><th colspan="1" rowspan="1" class="confluenceTh">
Description </th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>POJO</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
POJOs (Plain old Java objects) are the Java parameters to the method being invoked on the
target server.  Both Protocol and Logical JAX-WS handlers are supported. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>PAYLOAD</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>PAYLOAD</tt> is the message
payload (the contents of the <tt>soap:body</tt>) after message configuration in
the CXF endpoint is applied.  Only Protocol JAX-WS handler is supported.  Logical JAX-WS handler
is not supported. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>MESSAGE</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>MESSAGE</tt> is the 
 raw message that is received from the transport layer. It is not suppose to touch or change
Stream, some of the CXF interceptor will be removed if you are using this kind of DataFormat
so you can't see any soap headers after the camel-cxf consumer and JAX-WS handler is not supported.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>CXF_MESSAGE</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> New in <b>Camel 2.8.2</b>,
<tt>CXF_MESSAGE</tt> is try to invoke the full feature of CXF interceptors by
turning the message from the transport layer into a raw SOAP message from the transport layer</td></tr></tbody></table>
 </div>
 
 

Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/camel/content/cxf.html
==============================================================================
--- websites/production/camel/content/cxf.html (original)
+++ websites/production/camel/content/cxf.html Sat Jan 12 04:30:57 2013
@@ -134,7 +134,7 @@ cxf:bean:cxfEndpoint?wsdlURL=wsdl/hello_
 
 <div class="confluenceTableSmall"></div>
 <div class="table-wrap">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> DataFormat </th><th colspan="1" rowspan="1" class="confluenceTh">
Description </th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>POJO</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
POJOs (Plain old Java objects) are the Java parameters to the method being invoked on the
target server.  Both Protocol and Logical JAX-WS handlers are supported. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>PAYLOAD</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>PAYLOAD</tt> is the message
payload (the contents of the <tt>soap:body</tt>) after message configuration in
the CXF endpoint is applied.  Only Protocol JAX-WS handler is supported.  Logical JAX-WS handler
is not supported. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>MESSAGE</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>MESSAGE</tt> is the 
 raw message that is received from the transport layer. It is not suppose to touch or change
Stream, so you can't see any soap headers after the camel-cxf consumer and JAX-WS handler
is not supported. </td></tr></tbody></table>
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> DataFormat </th><th colspan="1" rowspan="1" class="confluenceTh">
Description </th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>POJO</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
POJOs (Plain old Java objects) are the Java parameters to the method being invoked on the
target server.  Both Protocol and Logical JAX-WS handlers are supported. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>PAYLOAD</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>PAYLOAD</tt> is the message
payload (the contents of the <tt>soap:body</tt>) after message configuration in
the CXF endpoint is applied.  Only Protocol JAX-WS handler is supported.  Logical JAX-WS handler
is not supported. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>MESSAGE</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>MESSAGE</tt> is the 
 raw message that is received from the transport layer. It is not suppose to touch or change
Stream, some of the CXF interceptor will be removed if you are using this kind of DataFormat
so you can't see any soap headers after the camel-cxf consumer and JAX-WS handler is not supported.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>CXF_MESSAGE</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> New in <b>Camel 2.8.2</b>,
<tt>CXF_MESSAGE</tt> is try to invoke the full feature of CXF interceptors by
turning the message from the transport layer into a raw SOAP message from the transport layer</td></tr></tbody></table>
 </div>
 
 



Mime
View raw message