Sunday Jan 16, 2011

Jabberwocky - Chuk's Jabber container for GlassFish


GlassFish now has Jabber container, courtesy of Chuk Munn Lee. In a two-part blog, Chuk describes his motivations and how you can get started with the software.

In part 1, Chuk discusses how building this as a first class citizen in GlassFish (as a container) simplifies writing Jabber components with the added benefit of using the application server lifecycle, management and monitoring "for free".

This work is based on igniterealtime's Tinder, a Java based XMPP library and part 2 of the series has all the details to get you started: how to install the container in GlassFish 3.0.1 (copy 2 files), how to install and configure an Openfire server, how to create and list xmpp configurations using GlassFish's asadmin to set subdomains and shared secret and finally, how to configure and deploy two .xar sample applications (with a standard "asadmin deploy" of course). You'll find the entire code on the Jabberwocky project.

You might recall another recently published GlassFish container: the Play Framework Container for GlassFish.
Writing GlassFish containers isn't hard!

Update: JAXenter has an interview with Chuk about Jabberwocky

Thursday Jul 31, 2008

Accenture Mini Talk on Dynamic Networks with JBI - using GlassFish and OpenESB

JavaOne Community Corner Podcast

An interesting mini talk on Dynamic Networks with JBI is now available in the JavaOne community corner podcasts.

Travis Chase from Accenture's National Security Services division details how GlassFish and OpenESB helped them develop a solution that decreases the network set-up time to run an exercise from weeks to minutes.

The team developed and contributed several components to the community to achieve this, including the XMPP, SIP and RSS binding components; plus they leveraged several others of the 30+ components available in the OpenESB community. The strong web service capabilities of GlassFish were used to define the business logic on the ESB.

If these components look familiar, we used the same RSS and XMPP components in the Project Fuji screencasts to show how quick and easy it is to route and filter messages between these systems.