#java ee 7

New in JMS 2.0 . . .

This post lists ALL of the new APIs (interfaces/classes/annotations etc.) introduced in JMS 2.0 (part of the Java EE 7 platform). These have been categorized as follows

API simplification

Ease of use

Exception Handling

Miscellaneous

Here is a quick summary along with some code snippets

API simplification JMSContext

Simpler abstraction on top of Connection and Session objects which eliminates the…

In this post, let’s explore the less talked about Web Socket Client API and how to leverage it within a Java EE 7 container itself

Web Socket Server API rules

The server side API of JSR 356(Web Socket API for Java) is most commonly used for building Web Socket endpoint implementations. More often than not, from a client perspective, the standard JavaScript Web Socket API is leveraged by the HTML5…

In this post….

Whirlwind tour of EJB timers

Working with EJB timers on the fly via simple REST interface with a sample implementation

The EJB @Schedule annotation comes in handy in case you need to create timers automatically. One can use cron-like expression to configure the appropriate schedule. If you need more flexibility, the good old TimerService works like a charm.

Quick background

The Tim…

This post of for those who are thinking about real world a.k.a production use of Java EE 7 . Please note that this list is courtesy two major sources –  JavaOne Conference (2014) talk delivered by Arun Gupta (check out the entire talk here) and Adam Bien’s blogs

http://www.slideshare.net/arungupta1/lessons-learned-from-realworld-deployments-of-java-ee-7-at-javaone-2014

  Let’s check them out……..

Handling time outs in Async JAX-RS requests

JAX-RS 2.0 provides support for asynchronous programming paradigm, both on client as well as on the server end. This post which highlights the time out feature while executing asynchronous REST requests on server side using the JAX-RS (2.0) API

Without diving into too many details here is a quick overview. In order to execute a method in asynchronous fashion, you just

need to specify an instance…

Thought of experimenting with a simple Java EE 7 prototype application involving JAX-RS (REST), WebSockets and CDI.

The idea was to use a REST end point as a ‘feed’ for a web socket end point which would in turn ‘push’ data to all connected clients

JAX-RS end point which receives data (possibly in real time) from other sources as an input to the web socket end point

Use CDI Events as the glue b/w…