swagger-api/swagger-codegen

Add AMQP transport

Open

#2,469 opened on Mar 30, 2016

View on GitHub
 (7 comments) (20 reactions) (0 assignees)HTML (12,701 stars) (5,474 forks)batch import
Enhancement: Featurehelp wanted

Description

This is just a sort of a crazy idea of using Swagger Spec for REST over AMQP protocol instead of HTTP. I do understand that this will require a huge amount of work, but I would love to at least have a discussion on this now. Who knows, maybe somebody will find it so useful, so they implement it (maybe even myself).

Extra keywords for search: RabbitMQ, ActiveMQ.

Related discussions:

Contributor guide

Tech stack
java
Domain
apibackend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
5
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
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.
unclear
Prerequisites
Understanding of Swagger/OpenAPIKnowledge of AMQP protocol
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
10
Research direction
This issue proposes adding AMQP transport to swagger codegen, but it's a broad idea without concrete specifications. To start, review the linked discussion in issue #144 and examine the current codebase structure, particularly the code generation modules for different transports. Investigate how the existing HTTP transport is implemented (e.g., in Java classes) and consider the feasibility of supporting AMQP. The issue requires deep understanding of both swagger codegen internals and AMQP protocols like RabbitMQ.