Sunday Aug 24, 2008

... Saving Money with JavaCAPS, From NB to GF, Mural Tutorial, EJB Performance

A compilation of today's news of interest:

Radio Receiver Icon

From Kevin and Mark - The recent Price Increate on Oracle Fusion has lead to a new conversion offer for Java CAPS (our SOA product built on GlassFish Server and OpenESB). Check Kevin's and OnTheRecord, these videos (beware! auto-run) and InfoWorld and TheRegister.

Alexis noticed a common thread in several comments in the USER alias for GlassFish Server and explains How Configuration on NetBeans may differ from that of your deployment GlassFish Server; and what to do about it.

Thanks to Swen-Helge for a pointer to this Mural/MDM tutorial.

From Adam a report on Informal Performance of Remote EJB. Adam has a number of entries at his blog arguing for EJB 3(.x) as lightweight component.

Tuesday Aug 19, 2008

... OpenJDK in Debian, Wotif and OpenMQ, New Bloggers, Wonderland 0.4, Solaris Features

A compilation of today's news of interest:

Radio Receiver Icon

From Barton, confirmation that OpenJDK is in Debian (in Lenny). That makes Fedora, Ubuntu, OpenSUSE and Debian; OpenJDK is also available for RedHat and CentOS. Not bad!

New Sun bloggers: Jacob has started writing about Ruby and Rails as a new engineer in the GLassFish Scripting team, and Michael will provide his Experiences in OpenESB from interactions with its customers. Welcome to both!

Wotif.COM is now a Formal GlassFish Reference, including its use of OpenMQ.

From the WonderBlog an announcement of the Release of Wonderland 0.4.

Joerg has two new multi-part series on Solaris, one covers CacheFS, the other the JumpStart Enterprise Toolkit.

Monday Jun 16, 2008

Java CAPS 6 Released - Press Reactions


Java CAPS 6 was Announced Last Week. It includes the ESB Suite and the Master Data Management Suite (MDM). Several Sun folks have already commented about it, including: Prakash, Jorge, Alexis (very nice, but in french), and Kevin (with PR assessment).

The launch of Java CAPS 6 is important on its own and also because the ESB Suite includes the OpenESB engine and several of its components (including BPEL SE, HTTP BC, Java EE SE, IEP) - see New Beginnings and Differences. Although the release is not yet actually available outside of an EA program, you can find the Documentation online.

Reaction from the press has been positive, including:

Information Week
The Register
Redmond Mag
Application Development Trends

Several of the Java CAPS/OpenESB engineers keep regular blogs and we will start covering them here. MDM is based on Mural and deserves a separate entry/entries.

Saturday May 24, 2008

Java CAPS 6 Almost Out; OpenESB Goes Enterprise


The code freeze for Java CAPS 6 was this last wednesday, and Fred Marked the Occasion. JavaCAPS 6 uses GlassFish (v2), adds JBI support and incorporates OpenESB elements.

JavaCAPS 6 is the latest in a road towards an Enterprise Quality, Easy-to-Use, OpenSource Integration platform. Check Eric's great History Recap.

The road does not end, though, there are more OpenESB components getting ready and there is Fuji and more beyond that. See my Introduction to these projects and Jason's Detailed Description between JavaCAPS and OpenESB.

Sunday May 18, 2008

OpenESB or Java CAPS ... or Fuji or GlassFish ESB


OpenESB, Java CAPS, Fuji, GlassFish ESB... how do they relate to each other?

Jason takes a crack at the Differences between Java CAPS and OpenESB. As he himself points out, some of the timing details are still settling down and we might add additional support offerings, but at the least we will do what he describes.

OpenESB itself is re-parenting into the overall GlassFish umbrella, with shared principles and increased synergies and Fuji is the core of its next version, exploiting the OSGi modularity. Fuji got a very positive response during JavaOne. We have a few Fuji-related entries piled in the TheAquarium draft list and Andi will be joining TA to cover this area.

GlassFish ESB is the bundling of OpenESB with GlassFish, with support from Sun. describes itself as a "community", but I think the activity is mostly going to happen within the "OpenESB" aliases and forums. We rushed some of the description material for JavaOne but since then I've been in internal follow-ups with the key stakeholders and I think we are all in agreement about this.