Glassfish Debugging, Caching, HATEOAS, RESTEasy

See how to debug an app on Glassfish: Glassfish Application Debug IntelliJ Tutorial

Another JAX-RS implementation except Jersey JBoss: http://www.jboss.org/resteasy

Uses the same API and package javax.ws.rs.*

Simple dependencies with JSON for Maven:

<dependencies>
	<dependency>
		<groupId>org.jboss.resteasy</groupId>
		<artifactId>resteasy-jaxrs</artifactId>
		<version>2.2.1.GA</version>
	</dependency>

	<dependency>
		<groupId>org.jboss.resteasy</groupId>
		<artifactId>resteasy-jackson-provider</artifactId>
		<version>2.2.1.GA</version>
	</dependency>
</dependencies>

<repositories>
	<repository>
		<id>JBOSS_NEXUS</id>
		<url>http://repository.jboss.org/nexus/content/groups/public</url>
	</repository>
</repositories>

• Client-Server
• Stateless
• Cacheable
• Layered system
• Code on demand (optional)
• Uniform interface

Talk on the topic given by doc. Ing. Tomáš Vitvar, Ph.D (FIT): HATEOAS-Vitvar

Defines caching setting for client, proxy

• private proxy can't cache, client can
• public both client and proxy can cache
• no-cache should not be cached
• no-store cache should not be persistent
• no-transform no data transformation (compression)
• max-age cache validity
• s-maxage cache validity for proxy

Response header, defines when the resource was last modified.

Request header, defines that the resource returns ok (200), if modified since the given date, 304 otherwise.

Response header, defines the tag (hash) of the returned resource.

Request header, defines, that the resource should be returned if the tag was modified, otherwise returns 304

caching.zip

Lze možné tyto caching headers použít i pro Concurrency Control?

Request header (for Last-Modified response header) - if holds, 200 / 204, otherwise 412 Precondition Failed

Request header (for ETag response header) - if holds, 200 / 204, otherwise 412 Precondition Failed

Hypertext as the Engine for Application State

• How is the state of the stateful application stored?
• How can we achieve the same behavior in stateless application?

HATEOAS - using links and headers we can store the state of the application.

Download the RESTEasy project: HATEOAS

Resources:

• POST /orders Creates a new order and returns URI of the order in the Location header
• GET /orders/id Returns an order with given ID
• POST /orders/id {“name”:“car”} Creates a new item in the order
• GET /orders/id/itemId Returns an item of the order with given ID
• PUT /orders/id/itemId {“name”:“car”} Modifies the item in the order
• DELETE /orders/id/itemId Deletes item of the order with given ID.