Author: buildbot
Date: Tue Sep 16 03:47:39 2014
New Revision: 922345
Log:
Production update by buildbot for cxf
Modified:
websites/production/cxf/content/cache/docs.pageCache
websites/production/cxf/content/docs/soap-over-jms-10-support.html
Modified: websites/production/cxf/content/cache/docs.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/cxf/content/docs/soap-over-jms-10-support.html
==============================================================================
--- websites/production/cxf/content/docs/soap-over-jms-10-support.html
(original)
+++ websites/production/cxf/content/docs/soap-over-jms-10-support.html Tue Sep
16 03:47:39 2014
@@ -149,13 +149,8 @@ jms:queue:ExampleQueueName?timeToLive=10
</wsdl11:port>
</wsdl11:service>
]]></script>
-</div></div><p>If a property is specified at multiple levels, the setting at
the most granular level takes precedence (port first, then service, then
binding). In the above example, notice the timeToLive property — for the
quickPort port, the value will be 10ms (specified at the port level). For the
slowPort port, the value will be 100ms (specified at the service level). In
this example, the setting in the binding will always be overridden.</p><h2
id="SOAPoverJMS1.0support-WSDLUsage">WSDL Usage</h2><p>For this
example:</p><div class="code panel pdl" style="border-width: 1px;">
- <div class="codeHeader panelHeader pdl hide-border-bottom"
style="border-bottom-width: 1px;">
- <b class="code-title">Greeter Service with JMS transaport</b>
- <span class="collapse-source expand-control"><span
class="expand-control-icon icon"> </span><span
class="expand-control-text">Expand source</span></span>
- </div>
- <div class="codeContent panelContent pdl hide-toolbar">
- <script class="theme: Default; brush: xml; collapse: true; gutter: false"
type="syntaxhighlighter"><![CDATA[<wsdl:definitions
name="JMSGreeterService"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="http://cxf.apache.org/jms_greeter"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:x1="http://cxf.apache.org/jms_greeter/types"
xmlns:soapjms="http://www.w3.org/2010/soapjms/"
name="JMSGreeterService"
targetNamespace="http://cxf.apache.org/jms_greeter">
+</div></div><p>If a property is specified at multiple levels, the setting at
the most granular level takes precedence (port first, then service, then
binding). In the above example, notice the timeToLive property — for the
quickPort port, the value will be 10ms (specified at the port level). For the
slowPort port, the value will be 100ms (specified at the service level). In
this example, the setting in the binding will always be overridden.</p><h2
id="SOAPoverJMS1.0support-WSDLUsage">WSDL Usage</h2><p>For this
example:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Greeter
Service with JMS transaport</b></div><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[<wsdl:definitions
name="JMSGreeterService"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="http://cxf.apache.org/jms_greeter"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:x1="http://cxf.apache.org/jms_greeter/types"
xmlns:soapjms="http://www.w3.org/2010/soapjms/"
name="JMSGreeterService"
targetNamespace="http://cxf.apache.org/jms_greeter">
...
<wsdl:binding name="JMSGreeterPortBinding"
type="tns:JMSGreeterPortType">
<soap:binding style="document"
transport="http://www.w3.org/2010/soapjms/" />
@@ -184,10 +179,8 @@ jms:queue:ExampleQueueName?timeToLive=10
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
-]]>
- </script>
- </div>
-</div><ul><li>The transport URI (<a shape="rect" class="external-link"
href="http://www.w3.org/2010/soapjms/";
rel="nofollow">http://www.w3.org/2010/soapjms/</a>) is defined in the
<soap:binding>.</li><li>The jms: URI is defined in the
<soap:address></li><li>The extension properties are in the
<soap:binding></li></ul><h2
id="SOAPoverJMS1.0support-Defineserviceendpointorproxyinspringorblueprint">Define
service endpoint or proxy in spring or blueprint</h2><p>The JAXWS endpoint or
proxy can be defined like in the SOAP/HTTP case. Just use a jms: uri like
described above.</p><p>In CXF 3 it is possible to omit the jndi settings. Just
specify an endpoint like this:</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeHeader panelHeader pdl"
style="border-bottom-width: 1px;"><b>Endpoint in spring</b></div><div
class="codeContent panelContent pdl">
+]]></script>
+</div></div><ul><li>The transport URI (<a shape="rect" class="external-link"
href="http://www.w3.org/2010/soapjms/";
rel="nofollow">http://www.w3.org/2010/soapjms/</a>) is defined in the
<soap:binding>.</li><li>The jms: URI is defined in the
<soap:address></li><li>The extension properties are in the
<soap:binding></li></ul><h2
id="SOAPoverJMS1.0support-Defineserviceendpointorproxyinspringorblueprint">Define
service endpoint or proxy in spring or blueprint</h2><p>The JAXWS endpoint or
proxy can be defined like in the SOAP/HTTP case. Just use a jms: uri like
described above.</p><p>In CXF 3 it is possible to omit the jndi settings. Just
specify an endpoint like this:</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeHeader panelHeader pdl"
style="border-bottom-width: 1px;"><b>Endpoint in spring</b></div><div
class="codeContent panelContent pdl">
<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><