This is a boiler-plate project to generate your own client library with Swagger. Its goal is to get you started with the basic plumbing so you can put in your own logic. It won't work without your changes applied.

The goal of Swagger™ is to define a standard, language-agnostic interface to REST APIs which allows both humans and computers to discover and understand the capabilities of the service without access to source code, documentation, or through network traffic inspection. When properly defined via Swagger, a consumer can understand and interact with the remote service with a minimal amount of implementation logic. Similar to what interfaces have done for lower-level programming, Swagger removes the guesswork in calling the service.

Check out OpenAPI-Spec for additional information about the Swagger project, including additional libraries with support for other languages and more.

At this point, you've likely generated a client setup. It will include something along these lines:

.
|- README.md    // this file
|- pom.xml      // build script
|-- src
|--- main
|---- java
|----- com.clouway.SitebricksGenerator.java // generator file
|---- resources
|----- sitebricks // template files
|----- META-INF
|------ services
|------- io.swagger.codegen.CodegenConfig

You will need to make changes in at least the following:

SitebricksGenerator.java

Templates in this folder:

src/main/resources/sitebricks

Once modified, you can run this:

mvn package

In your generator project. A single jar file will be produced in target. You can now use that with codegen:

java -cp /path/to/swagger-codegen-distribution:/path/to/your/jar io.swagger.codegen.Codegen -l sitebricks -o ./test

Now your templates are available to the client generator and you can write output values

The SitebricksGenerator.java has comments in it--lots of comments. There is no good substitute for reading the code more, though. See how the SitebricksGenerator implements CodegenConfig. That class has the signature of all values that can be overridden.

For the templates themselves, you have a number of values available to you for generation. You can execute the java command from above while passing different debug flags to show the object you have available during client generation:

# The following additional debug options are available for all codegen targets:
# -DdebugSwagger prints the OpenAPI Specification as interpreted by the codegen
# -DdebugModels prints models passed to the template engine
# -DdebugOperations prints operations passed to the template engine
# -DdebugSupportingFiles prints additional data passed to the template engine

java -DdebugOperations -cp /path/to/swagger-codegen-distribution:/path/to/your/jar io.swagger.codegen.Codegen -l sitebricks -o ./test

Will, for example, output the debug info for operations. You can use this info in the api.mustache file.

mlesikov:~/workspaces/idea/telcong.bss_DEV/core/src/main/java/com/clouway/telcong/bss/adapter/frontend/contacts/ttt

rm -rf sitebrickscodegen/out/petstore java -cp sitebrickscodegen/target/swagger-sitebricks-codegen-1.0.0.jar:swagger-codegen-cli.jar io.swagger.codegen.SwaggerCodegen generate -l sitebricks -i petstore.yaml -o sitebrickscodegen/out/petstore