-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make @Traced inherited #188
Comments
Did you mean adding
and |
Exactly. Since @Traced is not an @inherited annotation, the target class
doesn't contain it at runtime, and so the interceptor doesn't apply.
El mar., 24 mar. 2020 18:20, Felix Wong <[email protected]> escribió:
… Did you mean adding @Traced in the following
@stereotype
@retention(RUNTIME)
@target(TYPE)
@RequestScoped
@Traced
public @interface Service {
}
public class ThingOne {
@service
public void someService() {
// do something
}
}
and someService() is not traced.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#188 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAQC44D235Z5RWQEHLF5CT3RJDTVBANCNFSM4LQ4T67Q>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Excuse me if this has been already discussed.
I usually create a CDI stereotype which ressembles the
@Stateless
EJB annotation and can be used on all business classes:I'd like to add the
@Traced
annotation to it in order to get automatic OpenTracing support, but sadly the annotations isn't inherited, so it doesn't work.Did you have any reason not to make
@Traced
inheritable? I can provide a PR for it if you think it's a good idea. In the meantime, I'll simulate the behaviour with a CDI extension adding the annotation to the all beans that use my stereotype.The text was updated successfully, but these errors were encountered: