cxf-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r965703 - in /websites/production/cxf/content: cache/docs.pageCache docs/using-apache-htrace.data/image2015-9-16-21:9:56.png docs/using-apache-htrace.html
Date Thu, 17 Sep 2015 01:47:35 GMT
Author: buildbot
Date: Thu Sep 17 01:47:34 2015
New Revision: 965703

Log:
Production update by buildbot for cxf

Added:
    websites/production/cxf/content/docs/using-apache-htrace.data/image2015-9-16-21:9:56.png
  (with props)
Modified:
    websites/production/cxf/content/cache/docs.pageCache
    websites/production/cxf/content/docs/using-apache-htrace.html

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

Added: websites/production/cxf/content/docs/using-apache-htrace.data/image2015-9-16-21:9:56.png
==============================================================================
Binary file - no diff available.

Propchange: websites/production/cxf/content/docs/using-apache-htrace.data/image2015-9-16-21:9:56.png
------------------------------------------------------------------------------
    svn:mime-type = image/png

Modified: websites/production/cxf/content/docs/using-apache-htrace.html
==============================================================================
--- websites/production/cxf/content/docs/using-apache-htrace.html (original)
+++ websites/production/cxf/content/docs/using-apache-htrace.html Thu Sep 17 01:47:34 2015
@@ -117,11 +117,11 @@ Apache CXF -- Using Apache HTrace
            <!-- Content -->
            <div class="wiki-content">
 <div id="ConfluenceContent"><p><style type="text/css">/*<![CDATA[*/
-div.rbtoc1442368005830 {padding: 0px;}
-div.rbtoc1442368005830 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1442368005830 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1442454416442 {padding: 0px;}
+div.rbtoc1442454416442 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1442454416442 li {margin-left: 0px;padding-left: 0px;}
 
-/*]]>*/</style></p><div class="toc-macro rbtoc1442368005830">
+/*]]>*/</style></p><div class="toc-macro rbtoc1442454416442">
 <ul class="toc-indentation"><li><a shape="rect" href="#UsingApacheHTrace-Overview">Overview</a></li><li><a
shape="rect" href="#UsingApacheHTrace-DistributedTracinginNutshell">Distributed Tracing
in Nutshell</a></li><li><a shape="rect" href="#UsingApacheHTrace-DistributedTracinginApacheCXF">Distributed
Tracing in Apache CXF</a></li><li><a shape="rect" href="#UsingApacheHTrace-ConfiguringClientconfigure.client">Configuring
Client</a></li><li><a shape="rect" href="#UsingApacheHTrace-ConfiguringServerconfigure.server">Configuring
Server</a></li><li><a shape="rect" href="#UsingApacheHTrace-DistributedTracingInAction:UsageScenarios">Distributed
Tracing In Action: Usage Scenarios</a>
 <ul class="toc-indentation"><li><a shape="rect" href="#UsingApacheHTrace-Example#1:ClientandServerwithdefaultdistributedtracingconfigured">Example
#1: Client and Server with default distributed tracing configured</a></li><li><a
shape="rect" href="#UsingApacheHTrace-Example#2:ClientandServerwithnestedtrace">Example
#2: Client and Server with nested trace</a></li><li><a shape="rect" href="#UsingApacheHTrace-Example#3:ClientandServertracewithtimeline">Example
#3: Client and Server trace with timeline</a></li><li><a shape="rect"
href="#UsingApacheHTrace-Example#4:ClientandServerwithannotatedtrace(key/value)">Example
#4: Client and Server with annotated trace (key/value)</a></li><li><a
shape="rect" href="#UsingApacheHTrace-Example#5:ClientandServerwithparalleltrace(involvingthreadpools)">Example
#5: Client and Server with parallel trace (involving thread pools)</a></li><li><a
shape="rect" href="#UsingApacheHTrace-Example#6:ClientandServerwithasynchronousJAX-RSservice(server-side)">Exampl
 e #6: Client and Server with asynchronous JAX-RS service (server-side)</a></li><li><a
shape="rect" href="#UsingApacheHTrace-Example#7:ClientandServerwithasynchronousinvocation(client-side)">Example
#7: Client and Server with asynchronous invocation (client-side)</a></li></ul>
 </li><li><a shape="rect" href="#UsingApacheHTrace-FutureWork">Future Work</a></li></ul>
@@ -278,7 +278,22 @@ public void getBooks(@Suspended final As
         }
     });
 }</pre>
-</div></div><p>The actual invocation of the request by the client (with
process name <strong><span class="label label-default service-filter-label service-tag-filtered">jaxrsclient/192.168.0.100</span></strong>)
and consequent invocation of the service on the server side (process name<strong> <span
class="label label-default service-filter-label">jaxrsserver/192.168.0.100</span></strong>)
is going to generate the following sample traces:</p><p><span class="confluence-embedded-file-wrapper
confluence-embedded-manual-size"><img class="confluence-embedded-image" height="250"
src="using-apache-htrace.data/image2015-9-15%2021:26:5.png"></span></p><h2
id="UsingApacheHTrace-Example#7:ClientandServerwithasynchronousinvocation(client-side)">Example
#7: Client and Server with asynchronous invocation (client-side)</h2><p>TODO</p><h1
id="UsingApacheHTrace-FutureWork">Future Work</h1><p>TODO</p></div>
+</div></div><p>The actual invocation of the request by the client (with
process name <strong><span class="label label-default service-filter-label service-tag-filtered">jaxrsclient/192.168.0.100</span></strong>)
and consequent invocation of the service on the server side (process name<strong> <span
class="label label-default service-filter-label">jaxrsserver/192.168.0.100</span></strong>)
is going to generate the following sample traces:</p><p><span class="confluence-embedded-file-wrapper
confluence-embedded-manual-size"><img class="confluence-embedded-image" height="250"
src="using-apache-htrace.data/image2015-9-15%2021:26:5.png"></span></p><h2
id="UsingApacheHTrace-Example#7:ClientandServerwithasynchronousinvocation(client-side)">Example
#7: Client and Server with asynchronous invocation (client-side)</h2><p>In this
example server-side implementation of the JAX-RS service is going to be the default one:</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeCont
 ent panelContent pdl">
+<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">@Produces(
{ MediaType.APPLICATION_JSON } )
+@GET
+public Collection&lt;Book&gt; getBooks() {
+    return Arrays.asList(
+        new Book("Apache CXF Web Service Development", "Naveen Balani, Rajeev Hathi")
+    );
+}</pre>
+</div></div><p>While the JAX-RS client&#160;implementation is going
to perform the asynchronous invocation:</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;">final
Future&lt;Response&gt; future = client
+    .target("http://localhost:8282/books")
+    .request()
+    .accept(MediaType.APPLICATION_JSON)
+    .async()
+    .get();</pre>
+</div></div><p>In this respect, there is no difference from the caller
prospective however a bit more work is going under the hood to transfer the active tracing
span from JAX-RS client request filter to client response filter as in general those are executed
in different threads (similarly to server-side asynchronous JAX-RS resource invocation). The
actual invocation of the request by the client (with process name <strong><span class="label
label-default service-filter-label service-tag-filtered">jaxrsclient/192.168.0.100</span></strong>)
and consequent invocation of the service on the server side (process name<strong> <span
class="label label-default service-filter-label">jaxrsserver/192.168.0.100</span></strong>)
is going to generate the following sample traces:</p><p><span class="confluence-embedded-file-wrapper
confluence-embedded-manual-size"><img class="confluence-embedded-image" height="250"
src="using-apache-htrace.data/image2015-9-16%2021:9:56.png"></span></p><h1
id="Using
 ApacheHTrace-FutureWork">Future Work</h1><p>TODO</p></div>
            </div>
            <!-- Content -->
          </td>



Mime
View raw message