You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cxf.apache.org by dk...@apache.org on 2017/09/12 19:09:50 UTC
svn commit: r1018074 [10/31] - in /websites/production/cxf/content: ./
2008/04/28/ 2008/06/20/ 2008/10/23/ 2009/02/10/ 2009/08/04/ cache/ docs/
Modified: websites/production/cxf/content/docs/generic-tracing-component.html
==============================================================================
--- websites/production/cxf/content/docs/generic-tracing-component.html (original)
+++ websites/production/cxf/content/docs/generic-tracing-component.html Tue Sep 12 19:09:41 2017
@@ -129,13 +129,13 @@ The tracing should support a flow id tha
-<span class="gliffy-container" id="gliffy-container-25591961-1018" data-fullwidth="1411" data-ceoid="25202745" data-edit="${diagramEditLink.getLinkUrl()}" data-full="${diagramZoomLink.getLinkUrl()}" data-filename="Tracing Component">
+<span class="gliffy-container" id="gliffy-container-25591961-2925" data-fullwidth="1411" data-ceoid="25202745" data-edit="${diagramEditLink.getLinkUrl()}" data-full="${diagramZoomLink.getLinkUrl()}" data-filename="Tracing Component">
- <map id="gliffy-map-25591961-6603" name="gliffy-map-25591961-6603"></map>
+ <map id="gliffy-map-25591961-2530" name="gliffy-map-25591961-2530"></map>
- <img class="gliffy-image" id="gliffy-image-25591961-1018" width="1411" height="510" data-full-width="1411" data-full-height="510" src="https://cwiki.apache.org/confluence/download/attachments/25202745/Tracing%20Component.png?version=1&modificationDate=1298355725000&api=v2" alt="Tracing Component" usemap="#gliffy-map-25591961-6603">
+ <img class="gliffy-image" id="gliffy-image-25591961-2925" width="1411" height="510" data-full-width="1411" data-full-height="510" src="https://cwiki.apache.org/confluence/download/attachments/25202745/Tracing%20Component.png?version=1&modificationDate=1298355725000&api=v2" alt="Tracing Component" usemap="#gliffy-map-25591961-2530">
- <map class="gliffy-dynamic" id="gliffy-dynamic-map-25591961-1018" name="gliffy-dynamic-map-25591961-1018"></map>
+ <map class="gliffy-dynamic" id="gliffy-dynamic-map-25591961-2925" name="gliffy-dynamic-map-25591961-2925"></map>
</span>
@@ -146,13 +146,13 @@ The tracing should support a flow id tha
-<span class="gliffy-container" id="gliffy-container-25591966-6960" data-fullwidth="565" data-ceoid="25202745" data-edit="${diagramEditLink.getLinkUrl()}" data-full="${diagramZoomLink.getLinkUrl()}" data-filename="Design Flow id">
+<span class="gliffy-container" id="gliffy-container-25591966-8343" data-fullwidth="565" data-ceoid="25202745" data-edit="${diagramEditLink.getLinkUrl()}" data-full="${diagramZoomLink.getLinkUrl()}" data-filename="Design Flow id">
- <map id="gliffy-map-25591966-8364" name="gliffy-map-25591966-8364"></map>
+ <map id="gliffy-map-25591966-5625" name="gliffy-map-25591966-5625"></map>
- <img class="gliffy-image" id="gliffy-image-25591966-6960" width="565" height="276" data-full-width="565" data-full-height="276" src="https://cwiki.apache.org/confluence/download/attachments/25202745/Design%20Flow%20id.png?version=2&modificationDate=1298893753000&api=v2" alt="Design Flow id" usemap="#gliffy-map-25591966-8364">
+ <img class="gliffy-image" id="gliffy-image-25591966-8343" width="565" height="276" data-full-width="565" data-full-height="276" src="https://cwiki.apache.org/confluence/download/attachments/25202745/Design%20Flow%20id.png?version=2&modificationDate=1298893753000&api=v2" alt="Design Flow id" usemap="#gliffy-map-25591966-5625">
- <map class="gliffy-dynamic" id="gliffy-dynamic-map-25591966-6960" name="gliffy-dynamic-map-25591966-6960"></map>
+ <map class="gliffy-dynamic" id="gliffy-dynamic-map-25591966-8343" name="gliffy-dynamic-map-25591966-8343"></map>
</span>
</div>
Modified: websites/production/cxf/content/docs/how-do-i-develop-a-client.html
==============================================================================
--- websites/production/cxf/content/docs/how-do-i-develop-a-client.html (original)
+++ websites/production/cxf/content/docs/how-do-i-develop-a-client.html Tue Sep 12 19:09:41 2017
@@ -119,11 +119,11 @@ Apache CXF -- How do I develop a client?
<div id="ConfluenceContent"><p><br clear="none">
CXF provides you with many options to build clients for your services. This guide is meant to give you a quick overview of those options and help you orient yourself quickly with CXF.</p>
<style type="text/css">/*<![CDATA[*/
-div.rbtoc1435780114127 {padding: 0px;}
-div.rbtoc1435780114127 ul {list-style: disc;margin-left: 0px;padding-left: 20px;}
-div.rbtoc1435780114127 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1505242978610 {padding: 0px;}
+div.rbtoc1505242978610 ul {list-style: disc;margin-left: 0px;padding-left: 20px;}
+div.rbtoc1505242978610 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style><div class="toc-macro rbtoc1435780114127">
+/*]]>*/</style><div class="toc-macro rbtoc1505242978610">
<ul class="toc-indentation"><li><a shape="rect" href="#HowdoIdevelopaclient?-BuildingClients">Building Clients</a>
<ul class="toc-indentation"><li><a shape="rect" href="#HowdoIdevelopaclient?-WSDL2JavageneratedClient">WSDL2Java generated Client</a></li><li><a shape="rect" href="#HowdoIdevelopaclient?-JAX-WSProxy">JAX-WS Proxy</a></li><li><a shape="rect" href="#HowdoIdevelopaclient?-JAX-WSDispatchAPIs">JAX-WS Dispatch APIs</a></li><li><a shape="rect" href="#HowdoIdevelopaclient?-SimpleFrontendClientProxy">Simple Frontend Client Proxy</a></li><li><a shape="rect" href="#HowdoIdevelopaclient?-DynamicClient">Dynamic Client</a></li></ul>
</li></ul>
@@ -136,7 +136,7 @@ div.rbtoc1435780114127 li {margin-left:
<p>One of the most common scenarios is that where you have a service which you may or not manage and this service has a WSDL. In this case you'll often want to generate a client from the WSDL. This provides you with a strongly typed interface by which to interact with the service. Once you've generated a client, typical usage of it will look like so:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
HelloService service = new HelloService();
Hello client = service.getHelloHttpPort();
@@ -154,7 +154,7 @@ String result = client.sayHi("Joe");
<p>Instead of using a wsdl2java-generated stub client directly, you can use Service.create to create Service instances, the following code illustrates this process:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
import java.net.URL;
import javax.xml.ws.Service;
...
@@ -171,7 +171,7 @@ String result = client.greetMe("test");
<p>JAX-WS provides the "dispatch" mechanism which makes it easy to dynamically invoke services which you have not generated a client for. Using the Dispatch mechanism you can create messages (which can be JAXB objects, Source objects, or a SAAJMessage) and dispatch them to the server. A simple example might look like this:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
import java.net.URL;
import javax.xml.transform.Source;
import javax.xml.ws.Dispatch;
@@ -200,7 +200,7 @@ Source response = disp.invoke(request);
<p>CXF includes a Client interface which allows you to invoke operations and pass parameters for those operations. For instance:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
Client client = ....;
Object[] result = client.invoke("sayHi", "Dan");
</pre>
Modified: websites/production/cxf/content/docs/how-do-i-develop-a-service.html
==============================================================================
--- websites/production/cxf/content/docs/how-do-i-develop-a-service.html (original)
+++ websites/production/cxf/content/docs/how-do-i-develop-a-service.html Tue Sep 12 19:09:41 2017
@@ -117,14 +117,14 @@ Apache CXF -- How do I develop a service
<!-- Content -->
<div class="wiki-content">
<div id="ConfluenceContent"><p><br clear="none"> CXF provides you with many options to build services. This guide is meant to give you a quick overview of those options and help you orient yourself quickly with CXF.</p><p><style type="text/css">/*<![CDATA[*/
-div.rbtoc1435780232899 {padding: 0px;}
-div.rbtoc1435780232899 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1435780232899 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1505242948214 {padding: 0px;}
+div.rbtoc1505242948214 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1505242948214 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1435780232899">
+/*]]>*/</style></p><div class="toc-macro rbtoc1505242948214">
<ul class="toc-indentation"><li><a shape="rect" href="#HowdoIdevelopaservice?-DifferentTypesOfServices">Different Types Of Services</a></li><li><a shape="rect" href="#HowdoIdevelopaservice?-JAX-WSAnnotatedServicesfromJava">JAX-WS Annotated Services from Java</a></li><li><a shape="rect" href="#HowdoIdevelopaservice?-JAX-WSAnnotatedServicesfromWSDL">JAX-WS Annotated Services from WSDL</a></li><li><a shape="rect" href="#HowdoIdevelopaservice?-JAX-WSProviders">JAX-WS Providers</a></li><li><a shape="rect" href="#HowdoIdevelopaservice?-Javascript">Javascript</a></li></ul>
</div><h1 id="HowdoIdevelopaservice?-DifferentTypesOfServices">Different Types Of Services</h1><p>CXF support three major types of services:</p><ul><li>SOAP - this page summarizes the options for creating SOAP services.</li><li>REST-ful - REST support is described <a shape="rect" href="restful-services.html">here</a>.</li><li>CORBA</li></ul><h1 id="HowdoIdevelopaservice?-JAX-WSAnnotatedServicesfromJava">JAX-WS Annotated Services from Java</h1><p>The JAX-WS APIs include a set of <a shape="rect" class="external-link" href="https://jax-ws.java.net/nonav/2.2.8/docs/ch03.html#users-guide-annotations" rel="nofollow">annotations</a> which allow you to build services using annotated classes. These services are based on a single class which contains a set of operations.</p><p>Here's a simple example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">@WebService
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">@WebService
public class Hello {
public String sayHi(String name) {
return "Hello " + name;
@@ -132,7 +132,7 @@ public class Hello {
}
</pre>
</div></div><p>JAX-WS includes many more annotations as well such as:</p><ul><li>@WebMethod - allows you to customize the operation name, exclude the operation from inclusion in the service, etc</li><li>@WebParam - allows you to customize a parameter's name, namespace, direction (IN or OUT), etc</li><li>@WebResult - allows you to customize the return value of the web service call</li></ul><p>Data is marshalled from XML to Java and vice versa via the <a shape="rect" href="jaxb.html">JAXB data-binding</a>.</p><p>Services are publish via one of two means:</p><ul><li>The JAX-WS standard Endpoint APIs</li><li>CXF's XML configuration format - i.e. <jaxws:endpoint ... /></li></ul><p>More Information: <a shape="rect" href="a-simple-jax-ws-service.html">A simple JAX-WS service</a>, <a shape="rect" href="developing-a-service.html">Developing a JAX-WS Service</a> (goes into much more depth), <a shape="rect" href="writing-a-service-with-spring.html">Writing a service with Spring</a></p><h
1 id="HowdoIdevelopaservice?-JAX-WSAnnotatedServicesfromWSDL">JAX-WS Annotated Services from WSDL</h1><p>If you have existing WSDLs for your service or wish to write your WSDL first and then generate classes, CXF has many tools to help you do this.</p><p>The WSDL2Java tool will generate a JAX-WS annotated service and server stub from your WSDL. You can run it one of three ways:</p><ul><li><a shape="rect" href="wsdl-to-java.html">The command line</a></li><li><a shape="rect" href="using-cxf-with-maven.html">The Maven Plugin</a></li><li>With the WSDL2Java API</li></ul><p>Note that CXF generally restricts WSDL support to WSI-BP, not the full WSDL 1.1 specification.</p><p>There is also a <a shape="rect" href="simple-frontend.html">Simple Frontend</a> that allows you to create services without usage of Java annotations, using XML configuration files instead.</p><h1 id="HowdoIdevelopaservice?-JAX-WSProviders">JAX-WS Providers</h1><p>JAX-WS Providers allow you to create services which work
at the message level - as opposed to the operation level as with annotated classes. The have a single operation "invoke" which receives either the message payload (i.e. the SOAP Body) or the whole message itself (i.e. the SOAP Envelope).</p><p>Here's a simple example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">@WebServiceProvider
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">@WebServiceProvider
public class HelloProvider {
public Source invoke(Source request) {
return ....;
Modified: websites/production/cxf/content/docs/how-it-works.html
==============================================================================
--- websites/production/cxf/content/docs/how-it-works.html (original)
+++ websites/production/cxf/content/docs/how-it-works.html Tue Sep 12 19:09:41 2017
@@ -32,8 +32,8 @@
<link type="text/css" rel="stylesheet" href="/resources/highlighter/styles/shThemeCXF.css">
<script src='/resources/highlighter/scripts/shCore.js'></script>
-<script src='/resources/highlighter/scripts/shBrushJava.js'></script>
<script src='/resources/highlighter/scripts/shBrushXml.js'></script>
+<script src='/resources/highlighter/scripts/shBrushJava.js'></script>
<script>
SyntaxHighlighter.defaults['toolbar'] = false;
SyntaxHighlighter.all();
@@ -135,7 +135,7 @@ With xml element attachment in WSDL 1.1,
<p>PolicyAttachments are flexible w.r.t. the type of domain expressions. Domain expressions are used to identify entities such as endpoints, operations or messages with which a policy can be associated:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
<wsp:PolicyAttachment>
<wsp:AppliesTo>
<x:DomainExpression/> +
@@ -164,9 +164,9 @@ The effective policy for an endpoint is
The effective policy for an operation is the merge of the effective policies for the service subject, the endpoint subject and the operation subject.<br clear="none">
The effective policy for a (input | output | fault) message is the merge of the effective policies for the service subject, the endpoint subject, the operation subject and the message subject.</p>
-<p><img class="emoticon emoticon-information" src="https://cwiki.apache.org/confluence/s/en_GB/5982/f2b47fb3d636c8bc9fd0b11c0ec6d0ae18646be7.1/_/images/icons/emoticons/information.png" data-emoticon-name="information" alt="(info)"> <strong>Multiple sources</strong> can be used to apply policies to the same subject. In the case of an endpoint subject for example, its associated wsdl:port element can have multiple wsp:Policy child elements. Also, a separate document can contain wsp:PolicyAttachment elements in which the AppliesTo children identify the endpoint in question as the target subject. Both the Policies attached to the port element as well as those in the matching PolicyAttachment elements will then contribute to the effective policy of the endpoint subject.</p>
+<p><img class="emoticon emoticon-information" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/information.png" data-emoticon-name="information" alt="(info)"> <strong>Multiple sources</strong> can be used to apply policies to the same subject. In the case of an endpoint subject for example, its associated wsdl:port element can have multiple wsp:Policy child elements. Also, a separate document can contain wsp:PolicyAttachment elements in which the AppliesTo children identify the endpoint in question as the target subject. Both the Policies attached to the port element as well as those in the matching PolicyAttachment elements will then contribute to the effective policy of the endpoint subject.</p>
-<p><img class="emoticon emoticon-information" src="https://cwiki.apache.org/confluence/s/en_GB/5982/f2b47fb3d636c8bc9fd0b11c0ec6d0ae18646be7.1/_/images/icons/emoticons/information.png" data-emoticon-name="information" alt="(info)"> It is also important to keep in mind that the aggregation process described above makes it possible for an effective policy to have <strong>multiple assertion elements of the same type in one alternative</strong> (although this would not be considered the normal case). Different assertions of the same type within the same alternative do <strong><em>not</em></strong> overwrite each other. In fact, if used inappropriately, they may contradict each other. But it is also possible that they complement each other. Either way, the framewwork does not remove such duplicates and instead leaves it to the interceptors (or other Assertors) involved in the assertion process to decide if they can meaningfully deal with multiple assertions of the same type.</p>
+<p><img class="emoticon emoticon-information" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/information.png" data-emoticon-name="information" alt="(info)"> It is also important to keep in mind that the aggregation process described above makes it possible for an effective policy to have <strong>multiple assertion elements of the same type in one alternative</strong> (although this would not be considered the normal case). Different assertions of the same type within the same alternative do <strong><em>not</em></strong> overwrite each other. In fact, if used inappropriately, they may contradict each other. But it is also possible that they complement each other. Either way, the framewwork does not remove such duplicates and instead leaves it to the interceptors (or other Assertors) involved in the assertion process to decide if they can meaningfully deal with multiple assertions of the same type.</p>
<p>It is obvious that the above aggregation process can be quite resource intense. Effective policies for messages and endpoints are therefore cached by the framework for future reference. The entity that manages the cache of effective policies is the PolicyEngine. </p>
@@ -199,7 +199,7 @@ When the effective message policy is not
Given an assertion type that has attributes, and assuming there are two instances of assertions of this type, it is possible that the interceptor can assert one, but not the other. In any case, inability to support all assertions understood by the interceptor does not necessarily indicate a failure. As mentioned above in relation to pre-emptive interceptor installation, it is possible that the ones that cannot be supported do not in fact apply to the underlying message at all. <br clear="none">
Typically the interceptor would strive at supporting as many of these assertions as possible however, and to do so it may avail of the AssertionBuilder's capability to compute a compatible assertion. For example, by scheduling an acknowledgement to be sent in 3 seconds, an RM interceptor would support both of the following RMAssertions:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: xml; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
<wsrmp:RMAssertion xmlns:wsrmp="http://schemas.xmlsoap.org/ws/2005/02/rm/policy">
<wsrmp:AcknowledgementInterval Milliseconds="30000"/>
</wsrmp:RMAssertion>
Modified: websites/production/cxf/content/docs/how-to-define-policies.html
==============================================================================
--- websites/production/cxf/content/docs/how-to-define-policies.html (original)
+++ websites/production/cxf/content/docs/how-to-define-policies.html Tue Sep 12 19:09:41 2017
@@ -125,7 +125,7 @@ Apache CXF -- How to Define Policies
<h4 id="HowtoDefinePolicies-WSDLPolicyattachment">WSDL Policy attachment</h4>
<p>WS-Policies can be attached and referenced in WSDL elements. <a shape="rect" class="external-link" href="http://www.w3.org/TR/ws-policy-attach/" rel="nofollow">Web Services Policy 1.5 - Attachment </a> standard describes all possible alternatives. WS-Policies can be placed inside WSDL itself or referenced as external documents. CXF will automatically recognize, read and use policies defined or referenced in WSDL. Sample of attached policy is shown below:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: xml; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
<wsdl:definitions name="HelloWorld" targetNamespace="http://apache.org/hello_world_soap_http"
…
<wsdl:service name="SOAPService">
@@ -146,7 +146,7 @@ Apache CXF -- How to Define Policies
<p>It is possible to define policies directly in Spring configuration of client and service as jaxws feature. CXF will recognize and use configured WS-Policies:<br clear="none">
Client:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: xml; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:jaxws="http://cxf.apache.org/jaxws"
xmlns:cxf="http://cxf.apache.org/core"
@@ -175,7 +175,7 @@ http://cxf.apache.org/jaxws http://cxf.a
<p>Service:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: xml; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:jaxws="http://cxf.apache.org/jaxws"
xmlns:cxf="http://cxf.apache.org/core"
Modified: websites/production/cxf/content/docs/http-binding.html
==============================================================================
--- websites/production/cxf/content/docs/http-binding.html (original)
+++ websites/production/cxf/content/docs/http-binding.html Tue Sep 12 19:09:41 2017
@@ -32,8 +32,8 @@
<link type="text/css" rel="stylesheet" href="/resources/highlighter/styles/shThemeCXF.css">
<script src='/resources/highlighter/scripts/shCore.js'></script>
-<script src='/resources/highlighter/scripts/shBrushJava.js'></script>
<script src='/resources/highlighter/scripts/shBrushXml.js'></script>
+<script src='/resources/highlighter/scripts/shBrushJava.js'></script>
<script>
SyntaxHighlighter.defaults['toolbar'] = false;
SyntaxHighlighter.all();
@@ -125,7 +125,7 @@ Apache CXF -- HTTP Binding
<h1 id="HTTPBinding-Conventionbasedservices">Convention based services</h1>
<p>If you have a simple CRUD based Java class, CXF can try to build up a set of resources automatically for you with no annotations or configuration. This is best explained through an example. Lets take a look at a typical CRUD class:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
import javax.jws.WebService;
@WebService
@@ -148,7 +148,7 @@ public interface PeopleService {
<p>That's straightforward enough. We see "get", we map it to a GET operation. Then people is extracted from the operation name and turned into a simple URI. Accessing <a shape="rect" class="external-link" href="http://server/people" rel="nofollow">http://server/people</a> would result in a document like so:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: xml; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
<getPeople>
<Person>...</Person>
<Person>...</Person>
@@ -177,7 +177,7 @@ public interface PeopleService {
<h2 id="HTTPBinding-Configuringtheservice">Configuring the service</h2>
<p>You can create a service which uses the HTTP binding by using JaxWsFactoryBean:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
JaxWsServerFactoryBean sf = new JaxWsServerFactoryBean();
sf.setServiceClass(PeopleService.class);
sf.getServiceFactory().setWrapped(true);
@@ -201,7 +201,7 @@ Server svr = sf.create();
<p>Lets say I want to build an HTTP service that shares and manipulates customer data. The first thing I might want to do is create a URI that returns a document of all the customers in my database. With the JRA annotations this would be done like so:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
@Get
@HttpResource(location="/customers")
Collection<Customer> getCustomers();
@@ -213,7 +213,7 @@ Collection<Customer> getCustomers(
<p>Now lets say I want to pull down a specific customer, from /customers/ID:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
@Get
@HttpResource(location="/customers/{id}")
Customer getCustomers(GetCustomer getCustomer);
@@ -222,7 +222,7 @@ Customer getCustomers(GetCustomer getCus
<p>The major new concept in this example is URI templates. The GetCustomer object has a single property named "id":</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
public class GetCustomer {
String getId() { .. }
void setId(String id) { .. }
@@ -231,7 +231,7 @@ public class GetCustomer {
<p>The URI parameters get mapped to the XML document according to its schema and the WSDL 2 rules. So if you access the URL /customers/123 CXF will actually synthesize an incoming XML document like this:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: xml; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
<getCustomer><id>123</id></getCustomer>
</pre>
</div></div>
@@ -239,7 +239,7 @@ public class GetCustomer {
<p>The databinding layer will then convert this into the GetCustomer object. Lets move on to a more complex example - a PUT operation which updates the customer:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
@Put
@HttpResource(location="/customers/{id}")
Customer updateCustomer(Customer customer);
@@ -251,7 +251,7 @@ Customer updateCustomer(Customer custome
<p>For a final example, lets look at adding a customer:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
@Post
@HttpResource(location="/customers")
void addCustomer(Customer customer);
@@ -264,7 +264,7 @@ void addCustomer(Customer customer);
<p>To use multiple arguments, the @WebParam annotation has to be used to map the parameters of the url to the service parameters.<br clear="none">
For example:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
@Get
@HttpResource(location="/customers/{first}/{last}")
void findCustomer(@WebParam(name="first") String firstName, @WebParam(name="last") String lastName);
@@ -274,7 +274,7 @@ void findCustomer(@WebParam(name="first"
<h2 id="HTTPBinding-ConfiguringtheService">Configuring the Service</h2>
<p>Configuration for JRA style services is exactly the same as the convention based services. However, in this example, the service is not in "wrapped" mode. So the configuration is slightly different as we don't need to explicitly set the wrapped setting:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
JaxWsServerFactoryBean sf = new JaxWsServerFactoryBean();
sf.setServiceClass(CustomerService.class);
sf.setBindingFactory(new HttpBindingInfoFactoryBean());
@@ -290,7 +290,7 @@ Server svr = sf.create();
<h2 id="HTTPBinding-ConfiguringtheserviceincontainerwithSpringconfigurationfile.">Configuring the service in container with Spring configuration file.</h2>
<h3 id="HTTPBinding-web.xml">web.xml</h3>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: xml; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE web-app
@@ -327,7 +327,7 @@ Server svr = sf.create();
<h3 id="HTTPBinding-beans.xml">beans.xml</h3>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: xml; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -362,14 +362,14 @@ Server svr = sf.create();
<h1 id="HTTPBinding-Wrappedvs.UnwrappedMode">Wrapped vs. Unwrapped Mode</h1>
<p>In REST style services we can only send and receive one XML element. Wrapping is the process of wrapping the XML requests/responses with the operation names to allow multiple parameters to your operation. For instance, say we had an operation "Customer findCustomer(String name, String company)". It would not be valid to create an XML POST request like this:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: xml; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
<name>Dan</name>
<company>Acme Inc</company>
</pre>
</div></div>
<p>That has two root XML elements, which isn't allowed. Instead we would have to "wrap" the POST with the operation name:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: xml; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
<findCustomers>
<name>Dan</name>
<company>Acme Inc</company>
@@ -378,7 +378,7 @@ Server svr = sf.create();
</div></div>
<p>You may be wondering why don't we always turn on wrapping? Well wrapping creates uglier XML. Take this operation for instance: Collection<Customer> getCustomers(). The resulting XML would be:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: xml; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
<getCustomersResponse>
<Customers>
<Customer>..</Customer>
Modified: websites/production/cxf/content/docs/interceptors.html
==============================================================================
--- websites/production/cxf/content/docs/interceptors.html (original)
+++ websites/production/cxf/content/docs/interceptors.html Tue Sep 12 19:09:41 2017
@@ -32,8 +32,8 @@
<link type="text/css" rel="stylesheet" href="/resources/highlighter/styles/shThemeCXF.css">
<script src='/resources/highlighter/scripts/shCore.js'></script>
-<script src='/resources/highlighter/scripts/shBrushJava.js'></script>
<script src='/resources/highlighter/scripts/shBrushXml.js'></script>
+<script src='/resources/highlighter/scripts/shBrushJava.js'></script>
<script>
SyntaxHighlighter.defaults['toolbar'] = false;
SyntaxHighlighter.all();
@@ -118,7 +118,7 @@ Apache CXF -- Interceptors
<!-- Content -->
<div class="wiki-content">
<div id="ConfluenceContent"><h1 id="Interceptors-InterceptorsandPhases">Interceptors and Phases</h1><p>Interceptors are the fundamental processing unit inside CXF. When a service is invoked, an InterceptorChain is created and invoked. Each interceptor gets a chance to do what they want with the message. This can include reading it, transforming it, processing headers, validating the message, etc.</p><p>Interceptors are used with both CXF clients and CXF servers. When a CXF client invokes a CXF server, there is an outgoing interceptor chain for the client and an incoming chain for the server. When the server sends the response back to the client, there is an outgoing chain for the server and an incoming one for the client. Additionally, in the case of <a shape="rect" class="external-link" href="http://java.sun.com/j2ee/1.4/docs/api/javax/xml/soap/SOAPFault.html" rel="nofollow">SOAPFaults</a>, a CXF web service will create a separate outbound error handling chain and the client will c
reate an inbound error handling chain.</p><p>Some examples of interceptors inside CXF include:</p><ul><li>SoapActionInterceptor - Processes the SOAPAction header and selects an operation if it's set.</li><li>StaxInInterceptor - Creates a Stax XMLStreamReader from the transport input stream.</li><li>Attachment(In/Out)Interceptor - Turns a multipart/related message into a series of attachments.</li></ul><p>InterceptorChains are divided up into Phases. The phase that each interceptor runs in is declared in the interceptor's constructor. Each phase may contain many interceptors. On the incoming chains, you'll have the following phases:</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Phase</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Functions</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>RECEIVE</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Transport level process
ing</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>(PRE/USER/POST)_STREAM</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Stream level processing/transformations</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>READ</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>This is where header reading typically occurs.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>(PRE/USER/POST)_PROTOCOL</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Protocol processing, such as JAX-WS SOAP handlers</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>UNMARSHAL</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Unmarshalling of the request</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>(PRE/USER/POST)_LOGICAL</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Processing of the umarshalled request</p></td></tr><tr><td colspan="1" rowspan="1" class="confl
uenceTd"><p>PRE_INVOKE</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Pre invocation actions</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>INVOKE</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Invocation of the service</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>POST_INVOKE</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Invocation of the outgoing chain if there is one</p></td></tr></tbody></table></div><p>On the outgoing chain there are the following phases:</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Phase</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Functions</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>SETUP</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Any set up for the following phases</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>(PRE/USER/
POST)_LOGICAL</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Processing of objects about to marshalled</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>PREPARE_SEND</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Opening of the connection</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>PRE_STREAM</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>PRE_PROTOCOL</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Misc protocol actions.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>WRITE</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Writing of the protocol message, such as the SOAP Envelope.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>MARSHAL</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Marshalling of the objects</p></td></tr><tr><td colspan="1" rowspan="
1" class="confluenceTd"><p>(USER/POST)_PROTOCOL</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Processing of the protocol message.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>(USER/POST)_STREAM</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Processing of the byte level message</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>SEND</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr></tbody></table></div><p>After the SEND phase, there are a bunch of "*_ENDING" phases that are symmetrical to the above phases to allow the interceptors to cleanup and close anything that they had opened or started in the above phases:</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Phase</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Functions</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>SEND_ENDING<
/p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>POST_STREAM_ENDING</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>USER_STREAM_ENDING</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>POST_PROTOCOL_ENDING</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>USER_PROTOCOL_ENDING</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>MARSHAL_ENDING</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>WRITE_ENDING</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></t
d></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>PRE_PROTOCOL_ENDING</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>PRE_STREAM_ENDING</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>PREPARE_SEND_ENDING</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>POST_LOGICAL_ENDING</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>USER_LOGICAL_ENDING</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>PRE_LOGICAL_ENDING</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>S
ETUP_ENDING</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Usually results in all the streams being closed and the final data being sent on the wire.</p></td></tr></tbody></table></div><h1 id="Interceptors-InterceptorProviders">InterceptorProviders</h1><p>Several different components inside CXF may provide interceptors to an InterceptorChain. These implement the InterceptorProvider interface:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">public interface InterceptorProvider {
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">public interface InterceptorProvider {
List<Interceptor> getInInterceptors();
@@ -130,11 +130,11 @@ Apache CXF -- Interceptors
}
</pre>
</div></div><p>To add an interceptor to an interceptor chain, you'll want to add it to one of the Interceptor Providers.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">MyInterceptor interceptor = new MyInterceptor();
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">MyInterceptor interceptor = new MyInterceptor();
provider.getInInterceptors().add(interceptor);
</pre>
</div></div><p>Some InterceptorProviders inside CXF are:</p><ul><li>Client</li><li>Endpoint</li><li>Service</li><li>Bus</li><li>Binding</li></ul><h1 id="Interceptors-WritingandconfiguringanInterceptor">Writing and configuring an Interceptor</h1><p>The CXF distribution is shipped with a demo called <a shape="rect" class="external-link" href="http://svn.apache.org/viewvc/cxf/trunk/distribution/src/main/release/samples/configuration_interceptor/">configuration_interceptor </a> which shows how to develop a user interceptor and configure the interceptor into its interceptor chain.</p><h2 id="Interceptors-WritinganInterceptor">Writing an Interceptor</h2><p>Writing an interceptor is relatively simple. Your interceptor needs to extend from either the AbstractPhaseInterceptor or one of its <a shape="rect" class="external-link" href="http://tinyurl.com/3bkho8" rel="nofollow">many subclasses</a> such as AbstractSoapInterceptor. Extending from AbstractPhaseInterceptor allows your interceptor to
access the methods of the <a shape="rect" class="external-link" href="http://tinyurl.com/24gj28" rel="nofollow">Message</a> interface. For example, AttachmentInInterceptor is used in CXF to turn a multipart/related message into a series of attachments. It looks like below:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">import java.io.IOException;
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">import java.io.IOException;
import org.apache.cxf.attachment.AttachmentDeserializer;
import org.apache.cxf.message.Message;
@@ -163,7 +163,7 @@ public class AttachmentInInterceptor ext
}
</pre>
</div></div><p>Extending from sub-classes of AbstractPhaseInterceptor allows your interceptor to access more specific information than those in the Message interface. One of the sub-classes of AbstractPhaseInterceptor is <a shape="rect" class="external-link" href="http://tinyurl.com/2xqyg6" rel="nofollow">AbstractSoapInterceptor</a>. Extending from this class allows your interceptor to access the SOAP header and version information of the <a shape="rect" class="external-link" href="http://tinyurl.com/2gxj2c" rel="nofollow">SoapMessage class</a>. For example, SoapActionInInterceptor is used in CXF to parse the SOAP action, as a simplified version of it shows below:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">import java.util.Collection;
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">import java.util.Collection;
import java.util.List;
import java.util.Map;
@@ -236,7 +236,7 @@ public class SoapActionInInterceptor ext
}
</pre>
</div></div><p>Note that you will need to specify the phase that the interceptor will be included in. This is done in the interceptor's constructor:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">public class MyInterceptor extends AbstractSoapInterceptor {
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">public class MyInterceptor extends AbstractSoapInterceptor {
public MyInterceptor() {
super(Phase.USER_PROTOCOL);
}
@@ -244,7 +244,7 @@ public class SoapActionInInterceptor ext
}
</pre>
</div></div><p>You can also express that you would like the interceptor to run before/after certain other interceptors defined in the same phase:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">public class MyInterceptor extends AbstractSoapInterceptor {
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">public class MyInterceptor extends AbstractSoapInterceptor {
public MyInterceptor() {
super(Phase.USER_PROTOCOL);
@@ -258,7 +258,7 @@ public class SoapActionInInterceptor ext
}
</pre>
</div></div><p>You can add your interceptors into the interceptor chain either programmatically or through configuration.</p><h2 id="Interceptors-Addinginterceptorsprogrammatically">Adding interceptors programmatically</h2><p>To add this to your server, you'll want to get access to the Server object (see <a shape="rect" href="server-service-and-client-factorybeans.html">here</a> for more info):</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">import org.apache.cxf.endpoint.Server;
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">import org.apache.cxf.endpoint.Server;
import org.apache.cxf.frontend.ServerFactoryBean;
...
@@ -268,7 +268,7 @@ Server server = serverFactoryBean.create
server.getEndpoint().getInInterceptor().add(myInterceptor);
</pre>
</div></div><p>On the Client side the process is very similar:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">import org.apache.cxf.endpoint.Client;
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">import org.apache.cxf.endpoint.Client;
import org.apache.cxf.frontend.ClientProxy;
...
@@ -284,7 +284,7 @@ cxfClient.getInInterceptors().add(myInte
client.doSomething();
</pre>
</div></div><p>You can also use annotation to add the interceptors from the SEI or service class. When CXF create the server or client, CXF will add the interceptor according with the annotation.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">@org.apache.cxf.interceptor.InInterceptors (interceptors = {"com.example.Test1Interceptor" })
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">@org.apache.cxf.interceptor.InInterceptors (interceptors = {"com.example.Test1Interceptor" })
@org.apache.cxf.interceptor.InFaultInterceptors (interceptors = {"com.example.Test2Interceptor" })
@org.apache.cxf.interceptor.OutInterceptors (interceptors = {"com.example.Test1Interceptor" })
@org.apache.cxf.interceptor.InFaultInterceptors (interceptors = {"com.example.Test2Interceptor","com.example.Test3Intercetpor" })
@@ -298,7 +298,7 @@ public class SayHiImplementation impleme
}
</pre>
</div></div><h2 id="Interceptors-Addinginterceptorsthroughconfiguration">Adding interceptors through configuration</h2><p>The <a shape="rect" href="configuration.html">configuration file</a> page provides examples on using configuration files to add interceptors.</p><p>Adding MyInterceptor to the bus:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: xml; gutter: false; theme: Default" style="font-size:12px;"><beans xmlns="http://www.springframework.org/schema/beans"
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;"><beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:cxf="http://cxf.apache.org/core"
xsi:schemaLocation="
@@ -321,7 +321,7 @@ http://cxf.apache.org/core http://cxf.ap
</pre>
</div></div><p>For embedded Jetty-based web services, the configuration file can be declared by starting the service with the -Dcxf.config.file=server.xml option. See the <a shape="rect" class="external-link" href="http://tinyurl.com/2c9fuf" rel="nofollow">server configuration</a> section on the configuration file page for information on specifying the file for servlet WAR file-based web service implementations.</p><p>Adding MyInterceptor to your client:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: xml; gutter: false; theme: Default" style="font-size:12px;"><beans xmlns="http://www.springframework.org/schema/beans"
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;"><beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:http="http://cxf.apache.org/transports/http/configuration"
xsi:schemaLocation="http://cxf.apache.org/transports/http/configuration http://cxf.apache.org/schemas/configuration/http-conf.xsd
Modified: websites/production/cxf/content/docs/invokers.html
==============================================================================
--- websites/production/cxf/content/docs/invokers.html (original)
+++ websites/production/cxf/content/docs/invokers.html Tue Sep 12 19:09:41 2017
@@ -32,6 +32,7 @@
<link type="text/css" rel="stylesheet" href="/resources/highlighter/styles/shThemeCXF.css">
<script src='/resources/highlighter/scripts/shCore.js'></script>
+<script src='/resources/highlighter/scripts/shBrushBash.js'></script>
<script src='/resources/highlighter/scripts/shBrushJava.js'></script>
<script>
SyntaxHighlighter.defaults['toolbar'] = false;
@@ -120,7 +121,7 @@ Apache CXF -- Invokers
<p>CXF does provide a number of bundled invokers to handle simple cases. One of these simple cases is when it is desirable to have a singleton for the service object. In this case, you would like to provide a single object instance that should be used for all service invocations. The provided BeanInvoker covers this functionality, and would be used as follows:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
Service service = ...;
service.setInvoker(new BeanInvoker(new MyCustomBean(someParams)));
</pre>
@@ -128,7 +129,7 @@ service.setInvoker(new BeanInvoker(new M
<p>You can access the underlying Service object in two ways. If you've created your service using a ServerFactoryBean, this will yield a Server object which can be used to gain access to the Service:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
ServerFactoryBean factory = new ServerFactoryBean();
....
Server server = factory.create()
@@ -137,7 +138,7 @@ Service service = server.getEndpoint().g
</div></div>
<p>If you've created a JAX-WS Endpoint object, you can access the Service like this:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
EndpointImpl endpoint = (EndpointImpl) Endpoint.publish("http://host/service", new MyService());
....
Server server = endpoint.getServer();
@@ -149,7 +150,7 @@ Service service = server.getEndpoint().g
<p>The invoker implementation is as follows:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
public class EJBInvoker extends AbstractInvoker
{
private EJBHome home;
@@ -182,14 +183,14 @@ public class EJBInvoker extends Abstract
</div></div>
<p>Invokers, once defined, need to be registered with the Service. Once a handle onto a Service object has been obtained, the example invoker above can be registered on the binding like this:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
Service ejbService = ....;
ejbService.setInvoker(new EJBInvoker(ejbHome));
</pre>
</div></div>
<p>If you are using an EJB3 container you can use the following invoker, which is just a simplified version of the above:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
public class EJB3Invoker extends AbstractInvoker {
private Object ejb;
@@ -207,7 +208,7 @@ public class EJB3Invoker extends Abstrac
<h2 id="Invokers-Executors">Executors</h2>
<p>In addition to providing your own Invokers, you can also supply Executors for your service. Executors are a way to control scheduling for your service. To supply your own executor for a service just do:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
Service service = ....; // look up the service from CXF, or create it
service.setExecutor(new MyExecutor());
</pre>
Modified: websites/production/cxf/content/docs/java-to-ws.html
==============================================================================
--- websites/production/cxf/content/docs/java-to-ws.html (original)
+++ websites/production/cxf/content/docs/java-to-ws.html Tue Sep 12 19:09:41 2017
@@ -163,7 +163,7 @@ Apache CXF -- Java to WS
<p>The java2ws command can be wrapped inside an Ant target as shown below:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: xml; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
<?xml version="1.0"?>
<project name="cxf java2ws" basedir=".">
<property name="cxf.home" location ="/usr/myapps/cxf-trunk"/>
Modified: websites/production/cxf/content/docs/java-to-wsdl.html
==============================================================================
--- websites/production/cxf/content/docs/java-to-wsdl.html (original)
+++ websites/production/cxf/content/docs/java-to-wsdl.html Tue Sep 12 19:09:41 2017
@@ -32,8 +32,9 @@
<link type="text/css" rel="stylesheet" href="/resources/highlighter/styles/shThemeCXF.css">
<script src='/resources/highlighter/scripts/shCore.js'></script>
-<script src='/resources/highlighter/scripts/shBrushJava.js'></script>
+<script src='/resources/highlighter/scripts/shBrushBash.js'></script>
<script src='/resources/highlighter/scripts/shBrushXml.js'></script>
+<script src='/resources/highlighter/scripts/shBrushJava.js'></script>
<script>
SyntaxHighlighter.defaults['toolbar'] = false;
SyntaxHighlighter.all();
@@ -119,7 +120,7 @@ Apache CXF -- Java to WSDL
<div class="wiki-content">
<div id="ConfluenceContent"><h2 id="JavatoWSDL-Synopsis">Synopsis</h2>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
java2wsdl [-?|-help|-h][-o <output-file>][-cp <class-path>][-soap12][-t <target-namespace>][-servicenam <seservice-name>][-v][-verbose|-quiet][-s <source-directory>]
[-classdir <compile-classes-directory>][-portname <port-name>][-createxsdimports][-d <output-directory>] { classname }
</pre>
@@ -156,7 +157,7 @@ java2wsdl [-?|-help|-h][-o <output-fi
<p>The java2wsdl command can be wrapped inside an Ant target as shown below:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: xml; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
<?xml version="1.0"?>
<project name="cxf java2wsdl" basedir=".">
<property name="cxf.home" location ="/usr/myapps/cxf-2.0.1"/>
Modified: websites/production/cxf/content/docs/javascript-client-code.html
==============================================================================
--- websites/production/cxf/content/docs/javascript-client-code.html (original)
+++ websites/production/cxf/content/docs/javascript-client-code.html Tue Sep 12 19:09:41 2017
@@ -132,7 +132,7 @@ Apache CXF -- JavaScript Client Code
<p>The Schema code generates one object for each 'bean' used in your service. This code is organized by XML Schema. The code for each schema starts with a comment like:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: javascript; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
//
// Definitions for schema: http://apache.org/hello_world_soap_http/types
// file:/home/benson/cxf/trunk/distribution/src/main/release/samples/js_browser_client/wsdl/hello_world.wsdl#types1
@@ -145,7 +145,7 @@ Apache CXF -- JavaScript Client Code
<p>A typical JavaScript class for a type looks like:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: javascript; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
function apache_org_hello_world_soap_http_types_sayHiResponse () {
this._responseType = '';
}
@@ -167,7 +167,7 @@ apache_org_hello_world_soap_http_types_s
<p>The code for a service starts with a comment, followed by a constructor for the per-service object:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: javascript; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
// Javascript for {http://apache.org/hello_world_soap_http}Greeter
function apache_org_hello_world_soap_http_Greeter () {
@@ -222,7 +222,7 @@ fault information as a third parameter t
<p>The present author finds that, at least for JAX-WS, BARE has a lot to recommend it, as it avoids surprising interactions between JAX-WS and JAXB. </p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: javascript; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
function errorCallback(httpStatus, httpStatusText)
{
@@ -257,7 +257,7 @@ function compliantTest(url)
<p>The following function calls a Document/Literal/Bare method. The bare parameter element is declared as:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: xml; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
<element name="acceptAny1">
<complexType>
<sequence>
@@ -287,7 +287,7 @@ defined in the WSDL's schemas. To constr
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: javascript; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
function testAny1ToServerChalk(url)
{
var service = new cxf_apache_org_jstest_any_AcceptAny();
@@ -322,7 +322,7 @@ org_apache_cxf_any_holder. However, the
'false'. CXF may be enhanced to support passing non-described elements to JavaScript at a later time. </p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: javascript; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
function testAny1ToServerRaw(url)
{
var service = new cxf_apache_org_jstest_any_AcceptAny();
Modified: websites/production/cxf/content/docs/javascript-client-samples.html
==============================================================================
--- websites/production/cxf/content/docs/javascript-client-samples.html (original)
+++ websites/production/cxf/content/docs/javascript-client-samples.html Tue Sep 12 19:09:41 2017
@@ -119,7 +119,7 @@ Apache CXF -- JavaScript Client Samples
<div id="ConfluenceContent"><p>So far, there is one sample in the distribution. This sample, called js_browser_client_simple, provides an HTML user interface to the tiny hello_world service also present in the wsdl_first sample. The HTML page for the sample is here. This gives a flavor of an HTML page invoking a web service via the CXF JavaScript client generator.</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: html; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
<!-- Generate and retrieve a JavaScript client for the server. -->
<script type="text/javascript" src="/SoapContext/SoapPort?js"></script>
<script type="text/javascript">
Modified: websites/production/cxf/content/docs/javascript.html
==============================================================================
--- websites/production/cxf/content/docs/javascript.html (original)
+++ websites/production/cxf/content/docs/javascript.html Tue Sep 12 19:09:41 2017
@@ -32,6 +32,7 @@
<link type="text/css" rel="stylesheet" href="/resources/highlighter/styles/shThemeCXF.css">
<script src='/resources/highlighter/scripts/shCore.js'></script>
+<script src='/resources/highlighter/scripts/shBrushBash.js'></script>
<script src='/resources/highlighter/scripts/shBrushJava.js'></script>
<script>
SyntaxHighlighter.defaults['toolbar'] = false;
@@ -148,7 +149,7 @@ Apache CXF -- JavaScript
<p><span class="confluence-anchor-link" id="JavaScript-ex1"></span></p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Example 1:JavaScript Metadata</b></div><div class="codeContent panelContent pdl">
-<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
var WebServiceProvider1 = {
'wsdlLocation': 'file:./wsdl/hello_world.wsdl',
'serviceName': 'SOAPService1',
@@ -166,7 +167,7 @@ var WebServiceProvider1 = {
<p><span class="confluence-anchor-link" id="JavaScript-ex2"></span></p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Example 2:JavaScript Service Implementation</b></div><div class="codeContent panelContent pdl">
-<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
WebServiceProvider.invoke = function(document) {
var ns4 = "http://apache.org/hello_world_soap_http/types";
var list = document.getElementsByTagNameNS(ns4, "requestType");
@@ -190,7 +191,7 @@ WebServiceProvider.invoke = function(doc
<p><span class="confluence-anchor-link" id="JavaScript-ex3"></span></p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Example 3:E4X Service Implementation</b></div><div class="codeContent panelContent pdl">
-<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
var SOAP_ENV = new Namespace('SOAP-ENV',
'http://schemas.xmlsoap.org/soap/envelope/');
var xs = new Namespace('xs', 'http://www.w3.org/2001/XMLSchema');