Is your feature request related to a problem? Please describe.
Currently, only the javax namespaced jaxws is instrumented (javax.jws-api 1.1 and javax jaxws-api 2.0).
After apps migrate to the equivalent jakarta namespaced artifacts, they lose their instrumentation, since the equivalent jakarta namespaces are not currently instrumented.
Describe the solution you'd like
I would like new instrumentation for the jakarta namespaced jakarta.jws-api 3.0 and jakarta.xml.ws-api-3.0 to behave similar to the existing javax namespaced javax.jws-api 1.1 and javax jaxws-api 2.0
Describe alternatives you've considered
No alternatives, other than apps staying in the javax namespace.
Additional context
Associated maven coordinates of related artifacts
| javax |
jakarta |
javax.jws:javax.jws-api:1.1 |
jakarta.jws:jakarta.jws-api:3.0.0 |
javax.xml.ws:jaxws-api:2.0 |
jakarta.xml.ws:jakarta.xml.ws-api:3.0.0 |
Is your feature request related to a problem? Please describe.
Currently, only the javax namespaced jaxws is instrumented (javax.jws-api 1.1 and javax jaxws-api 2.0).
After apps migrate to the equivalent jakarta namespaced artifacts, they lose their instrumentation, since the equivalent jakarta namespaces are not currently instrumented.
Describe the solution you'd like
I would like new instrumentation for the jakarta namespaced jakarta.jws-api 3.0 and jakarta.xml.ws-api-3.0 to behave similar to the existing javax namespaced javax.jws-api 1.1 and javax jaxws-api 2.0
Describe alternatives you've considered
No alternatives, other than apps staying in the javax namespace.
Additional context
Associated maven coordinates of related artifacts
javax.jws:javax.jws-api:1.1jakarta.jws:jakarta.jws-api:3.0.0javax.xml.ws:jaxws-api:2.0jakarta.xml.ws:jakarta.xml.ws-api:3.0.0