swagger-api/swagger-codegen

JAX-RS should have Apache CXF Interface gateway

Open

#714 建立於 2015年5月4日

在 GitHub 查看
 (7 留言) (0 反應) (0 負責人)HTML (12,701 star) (5,474 fork)batch import
General: SuggestionServer: Javahelp wanted

描述

From https://github.com/swagger-api/swagger-editor/issues/423

Generate Server - JAX-RS should have Apache CXF Interface gateway, while it should not have Implementation class by itself. This gives developers seamless ability to be able to generate Apache CXF based JAX-RS Service (rather than presently produced Jersey API based Implementation). Assume the application is to go through Agile cycle, and is supposed to have a contract change in future, providing interface in server code to be extended in a different place to write complete service implementation would keep the Server Interface API and Implementation independent.

貢獻者指南

技術棧
java
領域
backendapi
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
4
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
over 1 week
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Understanding of Swagger Codegen generator architectureFamiliarity with JAX RS annotationsKnowledge of Apache CXF configurationExperience with Mustache templates
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
25
研究方向
The issue requests a new Apache CXF Interface gateway for JAX RS server generation. Start by examining the existing JAX RS server code generator (e.g., JAXRSServerCodegen.java) and the corresponding Mustache templates in the modules/swagger codegen/src/main/resources/ directory. Understand how the Jersey based implementation is generated, then design a new generator class (e.g., CXFServerCodegen) that extends DefaultCodegen. Create new Mustache templates for CXF interface and implementation classes. The developer should review existing PRs or comments in the issue for any prior attempts or guidance. The goal is to generate interface and implementation files that leverage Apache CXF annotations and configuration.