Mark has announced the Availability of Fuji M7. This new release features Many Additions including support for Enterprise Integration Patterns (EIP - website, Wikipedia). Supported patterns include: Message Filter, Split, Content-Based Routing, Aggregate and Wire Tap The Screencasts page does not yet include examples for the new features, but Mark hints that they are on their way. Also see previous entries tagged Fuji

Lots of exciting developments in the GlassFish ESB world; hot on the heels of the GlassFish ESB v2 release candidate with its enterprise features and commercial support we're also showing that we have more big plans for the evolution of this platform. With Milestone 3 of Project Fuji we give you the keys to test drive some of the platform enhancements we're working on for GlassFish ESB.next and allow you to be an active participant in driving the direction.

If you haven't been following Project Fuji closely you might be interested to know that there is both an "evolutionary" and "revolutionary" side; Adapters and Containers from v2 also are used in Fuji, and applications built in v2 deploy and run on Fuji. Where we're innovating is in looking at the productivity in every layer; ensuring we are tops in flexibility, agility and ease of use.

Milestone 3 of Project Fuji introduces a (dare I say very cool) web based tooling option for composing services.

Check out the Fuji Milestone 3 Screencast which shows how to use simple drag and drop in a browser to easily build the same scenario that was built in Milestone 2 via the domain specific language "IFL" for composing services.

It's worth noting that the web tooling builds on top of the domain specific language and hence round tripping is easy; you can for example check out the project built in the browser from subversion and edit it in your IDE of choice, just as shown in milestone 2.

This gets us one step closer to the mantra of Fuji: Productivity through flexibility, agility, and ease of use.

• In terms of flexibility this expands your tooling choices
• For agility you might notice the "automatically save and deploy" option which is one step towards our goal of making it very light weight to develop, test and correct your application as you go along
• For ease of use the simple way of visually modeling enterprise integration patterns and simple properties dialogs go a long way

Many of you may have seen the cool things Fuji Milestone 1 did, with its web based tooling option and the simple but powerful way of defining services and linking them together. For Milestone 1 we deliberately chose some contemporary technologies such as RSS and XMPP, which left some folks wondering: how does this apply to the more classic integration scenarios?

Fear not, for Milestone 2 we have chosen a classic scenario and show you how quick and easy it is to solve it with the powerful, but simple to use capabilities in Fuji.

Don't just take our word for it, watch the Fuji Milestone 2 Screencast with Keith driving it. Then Download Milestone 2 and take it for a spin by getting a simple jar file and give us feedback! There actually are more features that we couldn't fit in a single screencast, so watch this space.

For a highlight of the features such as added enterprise integration patterns and interceptors leveraging OSGi capabilities see the Milestone 2 page. Also have a look at Andi's entry on Fuji Milestone 2, which includes further background info.

We also re-vamped the landing page for Fuji, have a look at our fancy schmancy portal page for Fuji https://fuji.dev.java.net, it should have all the links to explore further information, screencasts etc.

Note that tomorrow (October 22, 2008, 9am PT) we'll have a live meeting and webcast to demo and discuss Fuji in the OpenESB Innovation Series meeting, come and participate.

Srinivasan Chikkala reports that support for Apache Camel has been added to OpenESB via the Camel Service Engine (SE) and shows how to use it in this screencast.

Apache Camel can be used for routing and mediation rules and adds one more option for defining the interactions between services to OpenESB by using a Java domain specific language (DSL), Spring based XML configuration, or the (work in progress) Scala DSL.

Louis took the new capability for a test drive with a detailed "how-to" write-up and his impressions in his quest to replicate the demo scenario shown in the Project Fuji preview at JavaOne this year.

The standards based pluggability of OpenESB allows this new component to leverage and be combined with any of the other 30+ components now part of the OpenESB community.