I wonder if this requirement is perhaps a perfect fit for the feature I
suggested on the mailing list in December. See:
Basically it is about a SPI which allows extensions to modify the
annotation metadata discovered by the ResourceBuilder.
I'm currently still working on this. So unfortunately there isn't anything
you could experiment with yet. But I hope to find some time for it in the
2018-01-24 17:27 GMT+01:00 Martin Stefanko <mstefank(a)redhat.com>:
for my issue  I am facing a few problems with which I would be glad if
somebody could help. As resteasy contains resteasy-cdi module, I am able to
manually collect JAX-RS related annotations from stereotypes by listening
for the Weld CDI events. My problem is how to propagate this information to
the processing of the request in the resteasy-jaxrs module. As I discussed
with Alessio it would be better to keep all CDI related code in the
resteasy-cdi module so I am searching for a way to substitute my classes
from resteasy-cdi module to the resteasy-jaxrs module. This will need to go
as deep as ResourceBuilder class as that's where the annotations are
processed but I don't see any way how to move the execution of the request
Thank you for any ideas.
Associate Software Engineer
JBoss Sustaining Engineering Team
Red Hat Czech s.r.o.
resteasy-dev mailing list