Let us discuss in detail about REST web service.<\/p>\n
1. Introduction<\/h2>\n1.1 REST<\/h3>\n
REST is an architecture principle for data transmission based on Web-standards and HTTP protocol. In REST, there are resources which are hosted using REST server. Every resource will have a unique Id known as URI and can be modified and accessed using REST client.<\/p>\n
REST allows representation of resources in different formats like XML, JSON, Text, etc.<\/p>\n
1.2 HTTP Operations<\/h3>\n
As REST supports HTTP protocol it allows following operations on the resources.<\/p>\n
- \n
- GET – GET request is used for accessing a resource and it provides a representation of the resource in the desired format.<\/li>\n
- POST – POST request is used for updating of an existing resource. It is also used for the creation of the new resource. It supports resource representation in various formats.<\/li>\n
- PUT – PUT request is used for updating a resource by completely replacing the existing one. As per the definition, PUT request is idempotent.<\/li>\n
- DELETE – DELETE request is used for removing a resource.<\/li>\n<\/ul>\n
In REST web services also we have two different flavours of REST web services as mentioned below.<\/p>\n
- \n
- RESTful web service<\/li>\n
- RESTless web service<\/li>\n<\/ul>\n
We will discuss in detail about RESTful web services as part of the tutorial.<\/p>\n
1.3 RESTful Web Services and JAX-RS<\/h3>\n
RESTful web services are the ones that follow REST based architecture and are majorly used for websites. It’s simple and fast as it is not bounded by strict restriction and consumes less bandwidth.<\/p>\n
Java came up with programming specification for the creation of web service in accordance with REST architecture. The name for this API specification is JAX-RS which stands for Java API for RESTful Web Services. JAX-RS was part of Java SE 5 and became a permanent member of the Java family from Java EE 6. The current version of JAX-RS is version 2.1 and it was released in September 2017.<\/p>\n
2. Annotations<\/h2>\n
Let’s discuss the different annotations and specification which are supported by JAX-RS.<\/p>\n
- \n
@Path<\/code>:- It tells the relative path of the resource class or method.<\/li>\n@GET<\/code>:- The HTTP Get request, which is used to fetch the resource.<\/li>\n@PUT<\/code>:- The HTTP PUT request, which is used to create a resource.<\/li>\n@POST<\/code>:- HTTP POST request, which is used to create or update a resource.<\/li>\n@DELETE<\/code>:- HTTP DELETE request, which is used to delete a resource.<\/li>\n@HEAD<\/code>:- It is HTTP HEAD request, which is used to get status of method availability.<\/li>\n@Produces<\/code>:- This tells the type of HTTP Response that is generated from the web service. For example, APPLICATION\/XML, APPLICATION\/JSON etc.<\/li>\n@Consumes<\/code>:- This tells the type of HTTP Request that the web service can process. For example, APPLICATION\/XML can be used to send the request in XML format.<\/li>\n@PathParam<\/code>:- It binds the parameter passed to the method to a value in the path.<\/li>\n@QueryParam<\/code>:- This binds the parameter passed to the method to a query parameter in the path.<\/li>\n@HeaderParam<\/code>:- This binds the parameter passed to the method to an HTTP header.<\/li>\n@DefaultValue<\/code>:- It will assign a default value to a parameter that is passed to the method.<\/li>\n@Context<\/code>:- It is the context of the resource. For example, HTTPRequest as a context.<\/li>\n<\/ul>\n3. Jersey<\/h2>\n
3.1 What is Jersey<\/h3>\n
Jersey is an open source framework which is used for building RESTful web services. It is more than just the implementation of JAX-RS. Jersey provides its own APIs also in order to make web service creation more simple and useful. It also provides a number of SPIs to extend the framework based on developer’s needs.
<\/div> <\/div><\/p>\n3.2 Components of Jersey<\/h3>\n
Jersey is full of a lot of features and component. But, there are major four components of Jersey. They are as follows.<\/p>\n
- \n
- Core Server:-\u00a0<\/strong>It is used for building RESTful web services. The components consist of jersey-core, jersey-server and jsr311-api.<\/li>\n
- Core Client:-<\/strong>\u00a0\u00a0For interaction with web services we need a client to communicate between web services. The components consist\u00a0of jersey-client.<\/li>\n
- JAXB support:-\u00a0<\/strong>Jersey provides support for JAXB. It makes XML to object conversion easy. The component which performs this support is jersey-server.<\/li>\n
- JSON support:-\u00a0\u00a0<\/strong>Jersey provides support for JAXB. It makes JSON to object conversion easy. The component which performs this support is jersey-server.<\/li>\n
- Easy integration with Spring and Guice framework.<\/li>\n<\/ul>\n
These are some of the major components and features of Jersey. Now let’s discuss how to install Jersey.<\/p>\n
3.3 Jersey Installation<\/h3>\n
There are two ways of installing Jersey in your program. We can use Gradle or we can perform a direct installation from jersey website.<\/p>\n
Let’s look at both ways.<\/p>\n
3.3.1 Gradle<\/h4>\n
In case we are using Gradle then we have to add the following lines in the project-dependencies section.<\/p>\n
compile 'org.glassfish.jersey.containers:jersey-container-servlet-core:2.26'<\/code><\/p>\nPlease note that the name of the project has changed starting from version 2.26. All the earlier versions had the name only
jersey-container-servlet<\/code>.<\/p>\n3.3.2 Installation from Jersey Website<\/h4>\n
For installation of Jersey from its website, we can download the package available at the website which contains all the dependencies excluding the third party dependencies.<\/p>\n
You can download the package from this link<\/a>.<\/p>\n
After downloading the package extract the zip file and paste all the jars in the
WEB-INF\/lib<\/code> of your program. That’s all you are ready to use jersey now.<\/p>\n4. Tools and Technologies<\/h2>\n
Let us look at the technologies and tool used for building the program.<\/p>\n
- \n
- Eclipse\u00a0Oxygen.2 Release (4.7.2)<\/li>\n
- Java \u2013 version 9.0.4<\/li>\n
- Gradle \u2013 4.6<\/li>\n
- JAX-RS 2.1<\/li>\n
- Jersey-2.26<\/li>\n
- Tomcat 9.0<\/li>\n<\/ul>\n
5. Project Structure<\/h2>\n
Our project structure will look as shown in the below image.<\/p>\n
![\"\"](\"http:\/\/www.javacodegeeks.com\/wp-content\/uploads\/2018\/04\/ProjectStructure_JCG.jpg\")
<\/a>Project Structure for JAX-RS project<\/figcaption><\/figure><\/p>\n The project structure shown above is for plan implementation of JAX-RS where libraries will be downloaded from Jersey website. For projects with build.gradle and pom.xml the project structure will differ slightly.<\/p>\n
6. An objective of the program<\/h2>\n
As part of the program, we will try to create a simple web service using Jersey. Also, we will try to understand the configuration and setup that needs to be done in order to create a web service.<\/p>\n
6.1 Jars<\/h3>\n
Following is the list of Jars that will be part of folder
WEB-INF\/lib<\/code>.<\/p>\n![\"\"](\"http:\/\/www.javacodegeeks.com\/wp-content\/uploads\/2018\/04\/JarsforJaxrs_JCG.jpg\")
<\/a>Jars as part of the build for JAX-RS project<\/figcaption><\/figure><\/p>\n There are two ways to add the jars as part of the project. Both the ways are mentioned below.<\/p>\n
- \n
- Addition of Jar using build files:<\/strong> Jars can be added to the project using build file like build.gradle or pom.xml by providing the jars along with version as the dependencies.<\/li>\n
- Download from Jersey website:<\/strong> All the jars mentioned above are available as part of the Jersey package which can be downloaded and copy pasted at WEB-INF\/lib. Link<\/a> for downloading the Jars.<\/li>\n<\/ol>\n
5.2 Configuration for JAX-RS<\/h3>\n
In order to use JAX-RS, we have to register Jersey as the dispatcher servlet for REST requests. We have to modify to
web.xml<\/code> have the following lines.<\/p>\nWeb.xml for Jersey as Dispatcher servlet<\/em><\/span><\/p>\n
<?xml version = \"1.0\" encoding = \"UTF-8\"?> \r\n<web-app xmlns:xsi=\"http:\/\/www.w3.org\/2001\/XMLSchema-instance\"\r\n\txmlns=\"http:\/\/java.sun.com\/xml\/ns\/javaee\" xmlns:web=\"http:\/\/java.sun.com\/xml\/ns\/javaee\/web-app_2_5.xsd\"\r\n\txsi:schemaLocation=\"http:\/\/java.sun.com\/xml\/ns\/javaee http:\/\/java.sun.com\/xml\/ns\/javaee\/web-app_2_5.xsd\"\r\n\tid=\"WebApp_ID\" version=\"2.5\">\r\n\t<display-name>JAX-RS Application Demo<\/display-name>\r\n\t<servlet>\r\n\t\t<servlet-name>jersey-servlet<\/servlet-name>\r\n\t\t<servlet-class>org.glassfish.jersey.servlet.ServletContainer<\/servlet-class>\r\n\t\t<init-param>\r\n\t\t\t<param-name>jersey.config.server.provider.packages<\/param-name>\r\n\t\t\t<param-value>com.tutorial<\/param-value>\r\n\t\t<\/init-param>\r\n\t<\/servlet> \r\n\t<servlet-mapping>\r\n\t\t<servlet-name>jersey-servlet<\/servlet-name>\r\n\t\t<url-pattern>\/rest\/*<\/url-pattern>\r\n\t<\/servlet-mapping> \r\n<\/web-app><\/pre>\n
There are different tags as part of the
web.xml<\/code>\u00a0for a different purpose.display-name<\/code> is used only for the display purpose.init-param<\/code> tag is used for initialization. We have used a paramjersey.config.server.provider.packages<\/code> this parameter defines which package Jersey will look into for service classes. The package defined here should contain service classes.url-patter<\/code> this tag is used to define the URL pattern. By default, the start of the URL is going to be with the project name followed by the url-pattern defined at this tag.<\/p>\n6.3 Service class<\/h3>\n
The service class is responsible for processing the request. Once the request is received by the dispatcher servlet ( which in our case is Jersey), the request is transferred to the service class based on the URL path. The service class name is
HelloWorld.java<\/code><\/p>\nService class for the project<\/em><\/span><\/p>\n
package com.tutorial;\r\n\r\nimport javax.ws.rs.GET; \r\nimport javax.ws.rs.Path;\r\nimport javax.ws.rs.PathParam;\r\nimport javax.ws.rs.core.Response;\r\n\r\n@Path(\"\/hi\")\r\npublic class HelloWorld\r\n{\r\n @GET\r\n @Path(\"\/{name}\")\r\n public Response getMessage(@PathParam(\"name\") String name)\r\n {\r\n String outMsg = \"Hello \" + name + \"!\";\r\n return Response.status(200).entity(outMsg).build();\r\n }\r\n \r\n}<\/pre>\nIn the code above
@Path<\/code>\u00a0is defined for the URL path. So, the URL will contain the project name, the url-pattern defined as part of the web.xml and the attribute supported with the@Path<\/code> annotation. The request will be diverted to this class by the dispatcher servlet.@GET<\/code> defined the type of HTTP method. If it contains@Path<\/code> parameters with these{}<\/code> brackets then those parameters are known as@PathParam<\/code>. In our casename<\/code> is a path parameter. You can define path at service level as well as at the method level.<\/p>\n6.4 Run the Program<\/h3>\n
In order to run the program, a web server is needed to run the web-service. For our program, we have used Apache Tomcat.<\/p>\n
Let’s create a war file and deploy the war on the tomcat server. Also, we can integrate the tomcat server with Eclipse. Once the Tomcat server is integrated with Eclipse and the project war is deployed on the server, we will get the following screen.<\/p>\n
- Download from Jersey website:<\/strong> All the jars mentioned above are available as part of the Jersey package which can be downloaded and copy pasted at WEB-INF\/lib. Link<\/a> for downloading the Jars.<\/li>\n<\/ol>\n
- Addition of Jar using build files:<\/strong> Jars can be added to the project using build file like build.gradle or pom.xml by providing the jars along with version as the dependencies.<\/li>\n
- Core Client:-<\/strong>\u00a0\u00a0For interaction with web services we need a client to communicate between web services. The components consist\u00a0of jersey-client.<\/li>\n
![\"\"](\"http:\/\/www.javacodegeeks.com\/wp-content\/uploads\/2018\/04\/Tomcat_JCG.jpg\")
<\/a>![\"\"](\"http:\/\/www.javacodegeeks.com\/wp-content\/uploads\/2018\/04\/Webservice_Browser_JCG.jpg\")
<\/a>