Add support for jax-ws method annotated with @WebMethod not declared by super-interfaces#3850
Merged
JonasKunz merged 2 commits intoelastic:mainfrom Nov 18, 2024
Merged
Conversation
…by super-interfaces
Contributor
Author
|
User reporting this issue confirmed that this PR fixes it. |
jackshirazi
approved these changes
Oct 29, 2024
Contributor
Author
|
run docs-build |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
#2667 added support for capturing the JAX-WS transaction names for methods which were inherited from an
@WebServiceinterface and do not have the@WebMethodannotation. It looks like this change accidentally removed the ability of instrumenting methods with@WebMethodwhich do not come from an interface.Checklist