swagger-api / swagger-api/swagger-codegen
Help Needed [JAXRS-CXF-CLIENT] Support for JSON-B / JSR-367 Annoations
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
Description
Support for JSR-367 Annotations instead of Jackson
Swagger-codegen version
2.4.6-SNAPSHOT
Suggest a fix/enhancement
I need an apache-cxf-client with jsonb instead of jackson annotations. I made a branch for it: https://github.com/dve/swagger-codegen/tree/jsonb
and the created result is not complete yet, but I know what to do. But I'm stuck with the options part - the test fails but I don't know how to handle it correct.
Can someone guide me please?
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 reporter's jsonb branch and the apache-cxf-client generator output, then investigate the options test they say is failing. Done means the client uses JSON-B/JSR-367 annotations instead of Jackson and the options test passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100