swagger-api / swagger-api/swagger-codegen
Not a managed type
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
Description
When using swagger codegen for spring language, the model which i created fails to run because of Not a managed type issue
Swagger-codegen version
2.3.1
Error in console
An exception occurred while running. null: InvocationTargetException: Error creating bean wit
h name 'projectService': Unsatisfied dependency expressed through field 'projectRepository'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'projectRepository': I
nvocation of init method failed; nested exception is java.lang.IllegalArgumentException: Not a managed type: class com.sap.dlm.codepipes.model.Project
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 with the generated com.sap.dlm.codepipes.model.Project model and projectRepository named in the stack trace, then inspect how the Spring generator handles these classes. Reproduce the startup failure and trace the generated model and repository setup. Done means the generated application starts without the “Not a managed type” exception.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100