-
Notifications
You must be signed in to change notification settings - Fork 312
JAX-WS WebService and WebServiceProvider instrumentation #2473
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
Conversation
...ws-annotations-1/src/main/java/datadog/trace/instrumentation/jaxws1/WebServiceDecorator.java
Outdated
Show resolved
Hide resolved
...otations-1/src/main/java/datadog/trace/instrumentation/jaxws1/WebServiceInstrumentation.java
Outdated
Show resolved
Hide resolved
...otations-1/src/main/java/datadog/trace/instrumentation/jaxws1/WebServiceInstrumentation.java
Show resolved
Hide resolved
...ations-2/src/main/java/datadog/trace/instrumentation/jaxws2/WebServiceProviderDecorator.java
Outdated
Show resolved
Hide resolved
...-2/src/main/java/datadog/trace/instrumentation/jaxws2/WebServiceProviderInstrumentation.java
Outdated
Show resolved
Hide resolved
Given the complexity of the matching, and SOAP being a relatively rare format these days, I think the quickest path to getting this merged without impacting non-SOAP users would be to disable this by default and have SOAP users opt in. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. You can combine the instrumentation if you want or leave separate. (I'm ok either way.)
Instruments endpoints annotated with
@WebService
(JAX-WS 1.x) and@WebServiceProvider
(JAX-WS 2.x)This support is turned off by default, but can be enabled with
-Ddd.integration.jax-ws.enabled=true
or by setting