In 3.0.0-SNAPSHOT the `Docket` bean defined by spring `FactoryBean<Docket>` cannot take effect
See original GitHub issueI defined a Docket
through spring FactoryBean<Docket>
, but the default Docket
still used by swagger. After testing, setting the eagerInit
property of BeansOfTypeTargetSource
to true
can take effect normally. I don’t know if this is the reason.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
java - Swagger 2 Issue - Spring Boot - Stack Overflow
Searching about I tried to change versions to 2.8.0, 2.7.0, 3.0.0... also returns error. The application is an apirest with task list activities ......
Read more >Springfox Reference Documentation - GitHub Pages
Springfox works by examining an application, once, at runtime to infer API semantics based on spring configurations, class structure and various ...
Read more >Documenting REST API's | by Knoldus Inc. - Medium
We will use Spring-boot(v-2.2.x) as our API creation framework, ... In our configuration file we need to provide a Docket bean.
Read more >Setting Up Swagger 2 with a Spring REST API - Baeldung
After defining the Docket bean, its select() method returns an instance of ApiSelectorBuilder, which provides a way to control the endpoints ...
Read more >Spring Boot and Swagger - Documenting RESTful Services ...
This guide will help you use Swagger with Spring Boot to document your ... @Bean public Docket api() { return new Docket(DocumentationType.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
After rewriting my code can work normally, thank you very much.
Should I close this issue?
Thank you @wangxing-git for reporting back! Its awesome that its working now