...

It is also worth to mention the way Apache CXF attaches the description to spans. With regards to the client integration, the description becomes a full URL being invoked prefixed by HTTP method, for example: GET http://localhost:8282/books. On the server side integration, the description becomes a relative JAX-RS resource path prefixed by HTTP method, f.e.: GET books, POST book/123

Configuring Client

// TODO

Configuring Server

// TODO

Distributed Tracing In Action: Usage Scenarios

Example #1: Client and Server with default distributed tracing configured

Example #2: Client and Server with nested trace

Example #3: Client and Server trace with annotations

Example #4: Client and Server with binary annotations (key/value)

Example #5: Client and Server with parallel trace (involving thread pools)

Example #6: Client and Server with asynchronous JAX-RS service (server-side)

Example #7: Client and Server with asynchronous invocation (client-side)

Distributed Tracing with OpenZipkin Brave and JAX-WS support

// TODO

Migrating from brave-cxf3

// TODO