anchor.diff:  [source,java]
   ----
   @Inject
  -Tracer configuredTracer;
  +io.opentracing.Tracer configuredTracer;
   ----
   
   Access to the configured Tracer gives full access to opentracing.io functions.
   
  -Providing the Tracer object enables support for the more complex tracing requirements, such as when a Span is started in one method, and finished in another.
  +The Tracer object enables support for the more complex tracing requirements, such as when a Span is started in one method, and finished in another.
   
   Access to the Tracer also allows tags, logs and baggage to be added to Spans with, for example:
   [source,java]
  
positive.code: 
  ==== Tracer configuration
  An implementation of an io.opentracing.Tracer must be made available to each application. Each application will have its own Tracer instance.
  The Tracer must be configurable outside of the application to match the distributed tracing environment where the application is deployed. For example, it should be possible to take the exact same application and deploy it to an environment where Zipkin is in use, and to deploy the application to a different environment where Jaeger is in use, and the application should report Spans correctly in either environment.
  
  ==== Span extraction
  When a request arrives at a JAX-RS endpoint, an attempt is made to use the configured Tracer to extract a Span from the arriving request. If a Span is extracted, it is used as the parent Span for the new Span that is created for the endpoint.
  
negative.code: 
  The @Traced annotation has two optional arguments.
  
  * value=[true|false]. Defaults to true. If @Traced is specified at the Class level, then @Traced(false) is used to annotate specific methods to disable creation of a Span for those methods. By default all JAX-RS endpoint methods are traced. To disable Span creation of a specific JAX-RS endpoint, the @Traced(false) annotation can be used.
  +
  Even when the @Traced(false) annotation is used for a JAX-RS endpoint method, the upstream Spancontext will still be extracted if it exists. The extracted Spancontext will be used to create a current Span.
  
  * operationName=&lt;Name for the Span&gt;. Default is "". If the @Traced annotation finds the operationName as "", the operationName is assigned as <package name>.<Class name>.<method name>
  
  Example:
  