Derek's Blog: Water Hazzard

It's been a while since I last posted anything...I've been busy climbing Fuji (metaphorically, I physically climbed Fuji-san many years ago) the project name for OpenESB v3. Andi Egloff presented a demo in the Java One Technical General Session that displayed some of the features that we have been working for a little over the balance of this calendar year.

I worked in a bunch of areas:

• EIP infrastructure
• Change EIP execution from using interceptors to being light-weight components
• Allow EIP based routes to be treated as a normal JBI services
• Specific EIP instance implementation
• Tee - as basic as they get
• Scatter/Gather - much higher complexity level. Reused the Broadcast and Aggregate EIP constructs to get the desired affect.
• Content Based Routing - the first steps. Allows for regex, XPath and NormalizedMessage headers to be queried and selected. Allow the rule set to be dynamically changed by storing the rules is in a file. 
• Tracing/Monitoring infrastructure
• Instrumented the NormalizedMessageRouter to signal tracing events for the 4 basic primitives: before send, after send, before accept and after accept. Implemented a simple text based logger that has been used for simple debugging.
• Kirill Sorokin & Alexander Permyakov are using this to enhance the WebUI with message tracing/replay mechanism

We are still on a tight schedule to round out the feature set and complete backward compatibility with OpenESB v2.  Watch our progress here...

 

Fuji, the OpenESB V3 development playground, has hit its Milestone 2 release.

For a quick preview watch the screencast. For more a more in depth look, check out the source code and the Milestone 2 demo. 

Besides a few fixes and some design collaboration on interceptors my main contribution to this release is the Proxy bundle.

The Proxy bundle allows a component in one Fuji instance on one machine to communicate with another component in another Fuji instance on a different machine. The Normalized Message Router (NMR) only deals with a single JVM instance. Usually SOAP/HTTP is used to span machines. The Proxy bundle is a JBI component that extends the NMR bus across JVM's using a light weight protocol.

Shoal/GMS is the basis for the first transport implementation for the Proxy bundle. It provides group awareness and messaging.

More detailed information about the Proxy bundle can be found here.

Also, checkout a presentation I gave at recent OpenEsb Innovation Series