Skip to main content

Jersey (JAX-RS) Resources URI mapping with @Path

In this guide, we will learn Jersey(JAX-RS) Resources and Sub Resources concepts as well as mapping of API HTTP URI using @Path annotation. Specifically, we will go through the following concepts and examples:

  1. Root Resources (Resources)
  2. Sub Resources
  3. HTTP URL mapping to Resources and Sub Resources using @Path annotation
  4. Deep dive @Path annotation
  5. Understand @PathParam annotation

We had tested or used the following tools and technologies in this project:

  1. Jersey (v 2.21)
  2. Gradle Build System (v 2.9)
  3. Spring Boot (v 1.3)
  4. Java (v 1.8)
  5. Eclipse IDE

This is a part of Jersey (JAX-RS) Restful Web Services Development Guides series. Please read Jersey + Spring Boot getting started guide._

Understand Resources & Sub Resources

In the real world we will be developing an API for either Resources or Non-Resources items. Usually, a standard API URL looks like the below for Resources:

Get a list of all humans - https://localhost:8080/humans

Get a specific human - https://localhost:8080/humans**/40200/**

Get a list of all addresses of a specific human - https://localhost:8080/humans**/40200/addresses/**

Get a specific address of a specific human - https://localhost:8080/humans**/40200/addresses/2/**

Note: Other than the bold part everything is base URI.

In the above examples, We are talking about Human Resources. Human Resources has relation with Address Resources. Or We may say Address Resources is Sub Resources of Human Resources. We may represent Address Resources as independent Resources as well as Sub Resources. When we design API for representing relationship data we opt for Sub Resources.

Tip: Resources like the Humans in the above example can also be called Root Resources.

Let's understand, how we can map Resources and Sub Resources to URI

Examples Resource & Sub Resource URI mapping using @Path

Resource class level URI mapping using @Path

Mapping /Humans

File: HumansResource.java

package in.geekmj.jersey.resource;

import javax.ws.rs.GET;
import javax.ws.rs.Path;
import javax.ws.rs.PathParam;
import javax.ws.rs.Produces;
import javax.ws.rs.core.Response;

@Path("Humans")
public class HumansResource {

	/**
	 * 
	 * @return Response
	 */
	@GET
	@Produces("text/plain")
	public Response getHumans() {

		return Response.accepted("Test /Human api called successfully.").build();
	}
}

Access URL https://localhost:8080/Humans

Test /human API called successfully.

Like @GET we can also use @POST, @PUT, and @DELETE.

Read URI Path Parameter using @PathParam

Mapping /humans/40200 or /humans/123445 or /humans/ and extracting humanId from path and using it in the method with the help of @PathParam annotation.

File: HumansResource.java

package in.geekmj.jersey.resource;

import javax.ws.rs.GET;
import javax.ws.rs.Path;
import javax.ws.rs.PathParam;
import javax.ws.rs.Produces;
import javax.ws.rs.core.Response;

@Path("humans")
public class HumansResource {

	@GET
	@Path("{humanId}")
	@Produces("text/plain")
	public Response getHuman(@PathParam("humanId") int humanId) {

		return Response.accepted("Test /human/" + humanId + " api called successfully.").build();
	}
}

Access URL https://localhost:8080/humans/40200

Test /human/40200 API called successfully.

Sub Resources URI Mapping using @Path at method level

Mapping /humans/123442/addresses

File: HumansResource.java

package in.geekmj.jersey.resource;

import javax.ws.rs.GET;
import javax.ws.rs.Path;
import javax.ws.rs.PathParam;
import javax.ws.rs.Produces;
import javax.ws.rs.core.Response;

@Path("humans")
public class HumansResource {

	@GET
	@Path("{humanId}/addresses")
	@Produces("text/plain")
	public Response getAddresses(@PathParam("humanId") int humanId) {

		return Response.accepted("Test /human/" + humanId + "/addresses api called successfully.").build();
	}
}

Access URL https://localhost:8080/humans/40200/addresses

Test /humans/40200/addresses API called successfully.

Read Sub Resource URI Path Parameter using @PathParam

Mapping /humans/123442/addresses/2

File: HumansResource.java

package in.geekmj.jersey.resource;

import javax.ws.rs.GET;
import javax.ws.rs.Path;
import javax.ws.rs.PathParam;
import javax.ws.rs.Produces;
import javax.ws.rs.core.Response;

@Path("humans")
public class HumansResource {

	@GET
	@Path("{humanId}/addresses/{addressId}")
	@Produces("text/plain")
	public Response getAddress(@PathParam("humanId") int humanId, @PathParam("addressId") int addressId) {

		return Response.accepted(
				"Test /human/" + humanId + "/addresses/addresses/" + addressId + " api called successfully.")
				.build();
	}
}

Access URL https://localhost:8080/humans/40200/addresses/2

Test /humans/40200/addresses/2 API called successfully.

Validate path parameter with Regular Expression in @Path

If we wanted to confirm the path parameter(s) value we may express the expected values using regular expression in @Path.

For e.g. if we wanted to only accept numbers for human id then we express that like @Path("humans/{humanId: [0-9]*}")

File: HumansResource.java

package in.geekmj.jersey.resource;

import javax.ws.rs.GET;
import javax.ws.rs.Path;
import javax.ws.rs.PathParam;
import javax.ws.rs.Produces;
import javax.ws.rs.core.Response;

@Path("humans")
public class HumansResource {

	@GET
	@Path("{humanId: \[0-9\]\*}")
	@Produces("text/plain")
	public Response getHuman(@PathParam("humanId") int humanId) {

		return Response.accepted("Test /human/" + humanId + " api called successfully.").build();
	}
}

Access URL https://localhost:8080/humans/40200

Test /human/40200 API called successfully.

If we access the URL https://localhost:8080/humans/40200abc ; It will give you an HTTP 404 error.

Tip: Default Regular Expression is {pathParam: [^/]+}. You can use any regular expression to confirm the Path Parameter values.

Another Tip: We are free to use or not use beginning / (forward slash) in URI. They don't make any difference.

Infographics to remember what we talked about in this guide (Read Employee as Human):

Jersey Resource SubResource @Path @PathParam

Download the Full Project

Follow Project On Github

Comments

Popular posts from this blog

Extend and reuse an existing AirByte destination connector

AirByte is an open-source ELT (Extract, Load, and Transformation) application. It heavily uses containerization for the deployment of its various components. On the local machine, we need docker to run it. AirByte has an impressive list of source and destination connectors available. One of my use case data destinations is the  ClickHouse data warehouse and its destination connector is not yet (2021-12-08) available. As per the documentation, It seems that creating a destination connector is a non-trivial job. It's a great idea to build an open-source ClickHouse destination connector. However, I tried avoiding the temptation to create one because of the required effort. AirByte has a  MySql destination connector available. ClickHouse provides a MySQL connector for access from any MySQL client. We need to configure Clickhouse to give support for the MySQL connector. Accessing ClickHouse from AirByte using its MySQL destination connector looks promising. However, when ...

Understanding Type Checking

A few examples of types in the context of programming language can be integer, float, character, string, array, etc.  When a program executes then data flow between instructions and values of specific types are assigned to a variable after some operation. It's important for the system to verify if the correct types are used as operands in operations. For e.g. In a sum operation, the expectation for operands to be of numeric type. The program's execution should fail in the case there is inconsistency. We can classify programming languages into two categories based as per their ability to cater to type safety: Dynamically Typed Language Statically Typed Language

Setting Clickhouse column data warehouse at Google Cloud Compute Engine VM

I didn't have a Google Cloud account associated with my email, so I signed up for one. It needs a valid Credit Card and mobile number to check if you are human. On successful sign up I get 300$ to spend within 3 months. Creating a free forever Google Cloud Compute Engine VM As per Google Cloud documentation you can have 1 non-preemptible e2-micro VM instance (1GB 2vCPU, 30GB Disk, etc.) per month free forever in some regions with some restrictions. I wanted the following stuff in my VM before I can install Clickhouse on to that: Ubuntu 20.x LTS SSH access from my machine Enabling SSH-based access to Google Compute Engine VM Step 1 Created an ssh private and public key on my mac using the following command ssh-keygen -t rsa -f ~/.ssh/gcloud-ssh-key -C mrityunjay -b 2048 Step 2 Copied the public key from the console using the following command: cat ~/.ssh/gcloud-ssh-key.pub output ssh-rsa <Gibrish :)> mrityunjay Step 3 I went to Google Cloud Console > Co...