swagger-api/swagger-codegen

Model Mapping of 400/500 error code

Open

#2,602 opened on Apr 14, 2016

View on GitHub
 (7 comments) (10 reactions) (0 assignees)HTML (12,701 stars) (5,474 forks)batch import
Client: JavaEnhancement: FeatureIssue: Workaround availablehelp wanted

Description

I have generated java client for my rest api. I have specified models for error responses 400 and 500 also but always i get error back as APIException and whole json is copied as string in ApiException.

Has anybody faces this issue and happen to resolve it?

Contributor guide

Tech stack
javarest api
Domain
toolingapi
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Knowledge of JavaUnderstanding of Swagger/OpenAPI specFamiliarity with code generation templates
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Investigate how swagger codegen generates Java client code for error responses (e.g., looking at templates for Java API classes). Understand the current handling of 400 and 500 status codes and why the generated code uses generic ApiException instead of the modeled response classes. Consider examining the code generation logic for response mapping and any existing tests or examples. Reproduce the issue with a simple OpenAPI spec to identify the exact point in the template or generator code where the mapping fails.
Model Mapping of 400/500 error code · swagger-api/swagger-codegen#2602 | Good First Issue