-
Notifications
You must be signed in to change notification settings - Fork 40.8k
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
Javadoc of slice test annotations should describe more accurately which components are considered #41914
Comments
@Narkissus thanks for the sample.
I think that the word "scan" is missing in the Javadoc of this slice test for some reason. The intent is that component scanning will only pick up beans annotated with We'll get the Javadoc fixed. I've submitted a PR to your sample that fixes the test and provide more context. |
I've extended the scope of this issue as other slice tests suffer from the same problem. |
This commit harmonizes the phrasing that we use to describe what components are considered for scanning when a slice test is enabled. This makes the description of the default filter explicit, with an exhaustive description of the annotations and/or base classes. Closes spring-projectsgh-41914
Spring Boot version: 3.3.2
According to the javadoc on
org.springframework.boot.test.autoconfigure.webservices.server.WebServiceServerTest
annotation, it should configure the context in a way that webservice relevant beans are present - i.e. beans of typeEndpoint
andEndpointInterceptor
.During my testing I have noticed that the
EndpointInterceptor
types are absent from the application context during tests while using@WebServiceServerTest
.The current workaround is to import the configuration class where the
EndpointInterceptor
beans are defined.You can find a minimal reproducible example code at https://github.com/Narkissus/WebServiceServerTest-issue-example
The text was updated successfully, but these errors were encountered: