Director of Customer Engagement - Loves technology and almost everything related to computing. Wants to help you write better software. Follow at @brianfernandes.
Let’s say you have an advanced backend system, for which you wish to develop a modern Angular frontend, or, perhaps it’s not your backend, but something public like Facebook, and you want to develop a site using some of its exposed APIs. Of course, you want to do this with minimal effort … how do you pull this off? Enter Swagger!
This article will walk you through the key steps required to connect an existing Java EE backend, which already exposes RESTful services, to an Angular frontend. Once you understand how these dots are connected, you can follow similar steps for other backends, or public APIs too.
Would you rather learn how to do this visually instead of reading this article? If yes, jump ahead to the Webinar we presented on this subject last week.
To connect our existing backend to an Angular frontend, we’re going to perform the following steps:
Generate a Swagger/OpenAPI specification file for your backend
Generate frontend code from the Swagger specification file
Create an Angular App to use the generated code
Generating a Swagger Specification File for Your Java EE Backend
Note that we’re starting with an application that already exposes RESTful web services through JAX-RS. If your application does not already do this, you must first create services which expose data that the frontend needs to function – this is beyond the scope of this article.
You can follow along with this project or your own.
Add Swagger dependencies To our project, we’re adding swagger-core, swagger-jaxrs and swagger-annotations which are libraries that cover the annotations we’re going to add to our code, interaction with JAX-RS, and generation of the Swagger specification file. If you’re using Maven, the dependencies look like this:
Add @Api annotations to resources What we want to do here is identify our REST resources which we wish to expose further with Swagger, and annotate them with the @Api (io.swagger.annotations.Api) annotation.
See the following screenshot for an example:
We must do this for all resources that we want exposed.
Note: There are several other annotations that will allow you to document and customize the specification file generated, among other things. Please see this document for more details.
Add specification generation code
In the root of your application (or any other appropriate place) add the following code to generate the Swagger specification file. Note that the URLs I’ve used are specific to our demo application.
Generating Frontend Code from the Swagger Specification File
In this part we’ll take the swagger specification file generated in the previous section, and generate some code that we can use in our Angular frontend. We’ll use the Swagger Code Generator to generate this code.
Do check if a more recent version is available before downloading.
From the command line, execute the following command: java -jar swagger-codegen-cli-2.2.3.jar generate -i http://localhost:8080/applicationPetstore/rest/swagger.json -l typescript-angular2
Note that we are pointing to the same Swagger specification we obtained in the last section.
The output of this command is a number of TypeScript files, including models and API code. The models in the model folder are a representation of your RESTful resources in TypeScript. The API code in the api folder is responsible for actually making the calls to the exposed endpoints, and dealing with the responses returned.
Create an Angular App to Use the Generated Code
With Angular IDE or MyEclipse, creating an Angular application is easy, even if you don’t have Node, NPM or the Angular CLI installed – we’ll download everything for you as part of the project creation process.
Following are a few highlights, covering Angular project creation, as well as key pieces of code. The code below can be found in this project.
Observe the following snippets of code which use the generated Category model as well as the CategoryApi class to display a list of categories. Of course, this code is specific to the Swagger specification file that we fed into the Swagger code generator.
IDEs Used: Angular IDE: Optimized for developers to make the most of Angular, advanced validation, content assist, debugging and more. MyEclipse: A single Java IDE that includes the best tools for the full stack developer to create a dynamic frontend along with a powerful backend.
2017 CI 8 Keeps Adding to the Treasure Chest Good news - our new release is out the door! For Angular IDE and Webclipse, we give you access to a brand new Eclipse experience with our DevStyle Preview. MyEclipse includes some key bug fixes in the Spring / Maven project area, and a new version of the Eclipse Buildship toolset, for improved Gradle support. Across these products, we’ve now added ...
Editors vs IDEs — What’s Best for You? Life is full of choices and dilemmas, and for a developer one of the greatest queries is whether to use a text editor or an Integrated Development Environment (IDE). Of course, using the latter provides for a much more complete experience, and yet, it might not be an absolute must in all situations. But how can one decide? There is a plethora of ...
Enhanced Code Navigation Made Possible with Webcli... Update: Webclipse has now been transformed into CodeMix.There are more reasons to love our Webclipse -- navigating through your Eclipse code is like sailing on a calm, blue sea. Minimap, Breadcrumb Navigation and Project Explorer+ are your unwavering beacons that show you the way to your files and source code, while DevSearch is the compass that wi...
Building Applications with Angular Material Angular Material is a set of high-quality UI components developed by the Angular team, based on the Google Material design specification. These components help us to build applications with an attractive, yet familiar UI, giving users a consistent experience across devices.In this Angular tutorial, you will learn how to set up material design in yo...