cxf-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [CONF] Apache CXF Documentation > Generic Tracing component
Date Tue, 22 Feb 2011 11:23:00 GMT
    <base href="">
            <link rel="stylesheet" href="/confluence/s/2036/9/1/_/styles/combined.css?spaceKey=CXF20DOC&amp;forWysiwyg=true"
<body style="background: white;" bgcolor="white" class="email-body">
<div id="pageContent">
<div id="notificationFormat">
<div class="wiki-content">
<div class="email">
    <h2><a href="">Generic
Tracing component</a></h2>
    <h4>Page <b>edited</b> by             <a href="">Christian
                         <h4>Changes (1)</h4>
<div id="page-diffs">
                    <table class="diff" cellpadding="0" cellspacing="0">
            <tr><td class="diff-added-lines" style="background-color: #dfd;">{gliffy:name=Tracing
Component|align=left|size=L|version=1} <br></td></tr>
            <tr><td class="diff-unchanged" >H1. Generic Tracing component <br>
            <tr><td class="diff-snipped" >...<br></td></tr>
    </div>                            <h4>Full Content</h4>
                    <div class="notificationGreySide">

<map name='GLIFFY_MAP_25202745_Tracing_Component'></map>
<table width="100%">
        <td align="left">
                <caption align="bottom">
                        <img style="border: none; width: 1411px; height: 510px;"

<p>H1. Generic Tracing component</p>

<p>The goal is to build a generic tracing and logging component with the following features</p>

<h2><a name="GenericTracingcomponent-Features"></a>Features</h2>

<ul class="alternate" type="square">
	<li>Asnychronous logging</li>

<p>The logging should be decoupled from the normal message flow so performance is not
degraded too much</p>

<ul class="alternate" type="square">
	<li>Persistent buffering</li>

<p>To achieve decoupling for larger messages it should be possible to store larger messages
on disk before they are send to the real tracing destination</p>

<ul class="alternate" type="square">
	<li>SPI for further processing of the message</li>

<p>There should be a well defined interface for the further processing of the traced
messages so it is for example possible to attach a remote logging server or a central monitoring

<ul class="alternate" type="square">
	<li>Support for correlation of request and responses</li>

<p>The tracing component should support correlation ids for exchanges so request and
response messages can later be combined again</p>

<h2><a name="GenericTracingcomponent-Design"></a>Design</h2>
        <div id="commentsSection" class="wiki-content pageSection">
        <div style="float: right;">
            <a href=""
class="grey">Change Notification Preferences</a>
        <a href="">View
        <a href="">View
        <a href=";showCommentArea=true#addcomment">Add

View raw message