swagger-api/swagger-codegen

Create interfaces instead of abstract classes for JAX-RS

Open

#2,672 opened on Apr 21, 2016

View on GitHub
 (3 comments) (1 reaction) (0 assignees)HTML (12,701 stars) (5,474 forks)batch import
Enhancement: GeneralServer: Javahelp wanted

Description

The generated service api are based on abstract classes, not interface. We all know that abstract class is something to avoid in Java, and interface provides much more flexibility. So please make the generated codes interfaces instead of abstract classes

Contributor guide

Tech stack
javarest api
Domain
backendapi
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
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.
clear
Prerequisites
Javaswagger codegenJAX RS
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55
Research direction
Examine the swagger codegen template files, particularly those related to JAX RS server generation. Look for abstract class definitions and replace them with interface definitions, ensuring compatibility with the JAX RS specification. Review the existing comments in the issue for any additional requirements or constraints.