Forwarding to the list :-)
---------- Forwarded message ----------
From: Alessio Soldano <asoldano(a)redhat.com>
Date: Wed, Sep 27, 2017 at 10:24 PM
Subject: Re: [resteasy-dev] SPI to add JAX-RS annotations dynamically
To: Christian Kaltepoth <christian(a)kaltepoth.de>
On Wed, Sep 27, 2017 at 9:19 PM, Christian Kaltepoth <christian(a)kaltepoth.de
> sorry for the delayed response. I agree that if some SPI would allow to
> modify the builders, it should be done before the resource is registered in
> the resource factory. Do you think such a SPI would be useful for others?
Probably yes, but your scenario might even be enough to justify it.
I would be happy to contribute some code if it improves portability between
> RESTEasy and the MVC RI.
Sure, feel free to work on that and send a PR.
> Thanks for pointing me to the resteasy-cdi integration. I'll have a deeper
> look at it in the next days.
OK, good, I hope that can offer some idea for integrating.
we are working on TCK for Microprofile OpenTracing. Basically it is
distributed tracing for jaxrs (for those who don't know).
We had an interesting discussion whether jaxrs client is thread safe or
not, because spec does not mention it.
Can somebody explain it? Is it only implementation specific?
I am looking at microprofile-opentracing integration for Wildfly Swarm.
Briefly, it is a distributed tracing for JAX-RS both server and client.
Issue  describes what is necessary. But I will repeat here:
1. register server jax-rs filters (no problem, server features are
2. use servlet filter to finish the span and log any exception to the span
- because jax-rs filters do not capture exceptions
1. register tracing filters
2. use OpenTracing-aware ExecutorService - it's needed for async API to
correctly propagate parent.
(3.) TCK is not defined yet. However, if they want to create spans for
UnknownHostException then we cannot use jax-rs client filters because they
are not executed. Network attempt happens before the filter when the
exception is thrown. To solve this we have to implement tracing in
resteasy or supply apache HC with tracing filters enabled (it also has some
The biggest issue is with client because we need
`ClientBuilder.newBuilder()` to return client/builder with enabled tracing.
Red Hat Česká republika <https://www.redhat.com/>
Purkyňova 115 TPB-B 612 00 Brno