Skip to main content

The Belgian Java User Group (BeJUG) Adopts JSR 356 (Java API for WebSocket)

Posted by editor on January 2, 2013 at 7:06 PM PST

The Belgian Java User Group (BeJUG) has decided to adopt JSR 356: Java API for WebSocket. In late November, Johan Vos posted a message to the Adopt-a-JSR Members mailing list stating some of the reasoning behind the group's decision to adopt this particular JSR:

Bejug plans to adopt JSR 356 - the Java API for WebSocket. We will create a dedicated page for this soon. This JSR currently has an early draft ready for review, so I think this might be a good time to start adopting it...

BeJUG has created the Adopt JSR-356: The Java API for WebSockets as the home page for organizing and documenting their efforts in bringing JSR 356 to completion. The group has already posted a bug to the WebSocket Spec JIRA -- which means BeJUG is already hard at work on testing the current rendition of JSR 356.

If you're not familiar with JSR 356 -- this is in part about web applications being able to readily update individual segments of the page. The age of reloading an entire page to get updated content is long gone. But now it's time to move beyond the current realm of spliced-together web pages to something that's more natively tuned for today's Web (and mobile) requirements. WebSockets aim to fill that need.

JSR 356 aims to cohesively integrate Java with the WebSockets API. Oracle submitted the JSR, and it's supported by SAP and RedHat. Danny Coward is the Spec Lead, and the expert group includes Jean-Francois Arcand, Fujitsu, Justin Lee, TmaxSoft, Inc., and Gregory John Wilkins. The request states:

There is a wide range of web applications that rely on timely updates from a central server like stock tickers, live maps, chat applications, collaborative online tools and multiplayer web-based games. WebSocket offers solution to the problems of latency, scalability and performance associated with HTTP based solutions like polling, long-polling and HTTP-streaming. There is a lot of interest in the Java developer community in creating web applications for the Java platform that utilize WebSocket. Given that the definition of WebSocket protocol is a proposed standard, and that the major web browsers either support, or plan to support it in their next major release, the time is right for a standard Java API for WebSocket.

The BeJUG Adopt JSR-356: The Java API for WebSockets page includes a Devoxx 2012 session by Jitendra Kotamraju about JSR 356. Here's the overview on Jitendra's session:

The family of HTML5 technologies has pushed the pendulum away from rich client technologies and toward ever-more-capable Web clients running on today's browsers. In particular, WebSocket brings new opportunities for efficient peer-to-peer communication, providing the basis for a new generation of interactive and "live" Web applications. This session examines the efforts under way to support WebSocket in the Java programming model, from its base-level integration in the Java Servlet and Java EE containers to a new, easy-to-use API and toolset that are destined to become part of the standard Java platform.

If you're interested in the Adopt-a-JSR effort, visit the Adopt-a-JSR home on Scroll down to see which Java User Groups are participating in which JSRs. Subscribe to an Adopt-a-JSR mailing list to stay in contact with the latest happenings in the Adopt-a-JSR effort.

If your primary interest is Java EE related JSRs, visit the GlassFish community's Adopt-a-JSR for Java EE 7 page.

And when you're ready to participate, go do it! Weblogs

Since my last blog post, Markus Karg posted a new blogs:


Our latest article from Manning Publications is What is SPARQL? by David Wood, Marsha Zaidman, Luke Ruth, and Michael Hausenblas, authors of the Manning book Linked Data.


Our current poll asks What do you know about Hadoop? Voting will be open until Friday, January 4.


Here are our latest Spotlights.

  • Heather VanCura - 2012 JCP Year in Review:

    A brief 2012 JCP Year in Review summary is below. The year was marked with many signs that point toward making the future Java: *JSR progress... *JCP.Next reform efforts moved forward... *Public EC Meetings... *JCP program recognized Active Spec Leads and Maintenance Leads... *Momentum and participation from JUGs... *Tenth Annual JCP Awards... *Participation in conferences around the world...

  • jaxenter - What will 2013 bring? Developers place their bets:

    Three prominent developers - Martijn Verburg, CTO at jClarity and co-leader of London Java Community; Andrey Breslav, Kotlin Project Lead at JetBrains, Inc.; and Ted Neward, Consultant and "The Dude of Software"- share personal highlights from 2012, and predictions for 2013...

Java News

Here are the stories we've recently featured in our Java News section: