swagger-api / swagger-api/swagger-core
OpenApi not generated when resourceClasses used
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 7.5k
- Forks
- 2.3k
- Avg merge
- 18h 1m
- Merged PRs (30d)
- 10
Description
Hi,
I use jax-rs to create my api. It runs on weblogic server. when I use openapi.configuration.resourcePackages param with corresponding packages as param value works perfectly. However, when I use openapi.configuration.resourceClasses or jersey.config.server.provider.classnames params with corresponding classes as param value, it does not create openapi. Instead this json is given when I go to **/v1/openapi
{
"openapi" : "3.0.1"
}
More interesting situation is that openapi is generated with classes on my local windows machine, but it does not work on remote linux server. What may be the problem?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the openapi.configuration.resourcePackages and openapi.configuration.resourceClasses settings, along with jersey.config.server.provider.classnames, between the working Windows setup and the remote Linux server. Inspect the /v1/openapi response and configuration inputs; done means the generated document includes the registered resource classes and their API paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, openapi
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100