Why You Should Care About the Java EE Management API 2.0 (JSR 373)

In recent a GlassFish Community blog post, Reza Rahman comments that JSR 373 –  Java EE Management API 2 , has thus far sat in the shadow of other Java EE 8 initiatives. With the JSR now moving full steam ahead though, you can expect to hear a lot more about it going forward.

A modern counterpart to the J2EE Management specification (JSR 77), which was designed to manage various resources on an application server, JSR 383 is aiming to adopt REST as the de-facto interface for communicating with managed objects and providing functionals like exposing the CRUD operations on managed objects as RESTful interfaces.

As Abhishek Gupta notes in his whistle-stop tour of all things Java EE 8, JSR 373 will also leverage SSE to distribute events in response to changes in managed object states, and allow for deployment of Java EE applications using a REST interface.

To Rahman, it represents “one of the most interesting and useful parts of Java EE 8.” Whilst the success of JSR 77 was muted by factors like an overly “complex, abstract and cumbersome” API, Rahman writes that this new incarnation will be a new opportunity to take on the problem with a modern set of tools. In addition to REST, this will mean taking advantage of things like SEE and possibly WebSocket for event notification.

The interface should resemble the GlassFish REST management interface, which will mean that, from an industry standpoint, developers will be able to work, “with all Java EE 8 application servers using a uniform, predictable cross-platform API from all kinds of tools from simple HTTP command-line clients to Chef and Puppet.” It will be accessible both on cloud and on premise.

There’s already an expert group in place for this particular JSR, but you can subscribe to the JSR user alias to keep up with all the latest on this Java EE 8 effort. For the Java EE Management API 2.0, this alias is users at javaee-mgmt dot java dot net – head to the Java EE Management API 2.0 java.net project page to subscribe.

We also recommend checking out this featured Parleys presentation, where Arun Gupta outlines everything coming in Java EE 8 – including JSR 373 (skip ahead to 0:13:03 for this part) – and how it all links together. And, as ever, if you’d like to join this global push in the name of Java, you can always get involved in Adopt a JSR. Click here for a detailed account of what this entails, written by Mani Sarkar.

This story, "Why You Should Care About the Java EE Management API 2.0 (JSR 373)" was originally published by voxxed.com