Index Changes
Page Difference

Difference between version and version     

Back to Fuji Milestone 2, or Fuji Milestone 2 Info


At line 3 removed 2 lines.
[{TableOfContents}]
At line 9 changed 1 line.
* [Download the Milestone 2 Distribution|https://open-esb.dev.java.net/Downloads.html]
* [Download the Milestone 2 Distribution|http://download.java.net/jbi/binaries/fuji/main/milestone/fuji-M2-felix.jar]
At line 12 changed 12 lines.
!! Goals
The goals of this milestone include:
* Demonstrate the use of dynamic service composition in service development, deployment, and administration.
* Demonstrate how Fuji is capable of handling "classic" integration scenarios.
* Highlight flexibility in composition model (interceptors) and runtime architecture (distributed NMR)
!! Focus Areas
! Reactive Runtime
Reactive Runtime refers to the ability of the runtime to react to changes to deployed service artifacts and their associated configuration settings. This is very similar to "hot deploy" and "directory-based deploy" in traditional application server environments, but it extends this model in a number of important areas. First, the 'refresh' of the application is a controlled life cycle event, not an ad hoc measure where a new app class loader is created and the old app class loader is orphaned. Second, configuration details outside the scope of a service artifact (e.g. service wiring) are also eligible for dynamic update.
\\
!! Highlights
! Enhanced support for [Enterprise Integration Patterns|http://enterpriseintegrationpatterns.com/]
* [Split|FujiEIPSplit]
* [Aggregate|FujiEIPAggregate]
* [Message Filter|FujiEIPMessageFilter]
At line 25 changed 9 lines.
Interceptors provide a mechanism by which integration developers can 'inject' code into the message exchange path between components. This is desirable for addressing cross-cutting concerns as well as piecework integration code that does not belong in application code (e.g. adding a protocol header before a message is sent).
! Classic Integration
While the primary goal of Fuji is to explore new technology directions for our platform, we must not lose sight of the bread and butter use cases that the majority of our users actually exercise. The focus of the this deliverable is to prove that Fuji is up to the task of implementing class integration scenarios. There are three broad categories in this area:
* ''Patterns'': Integration patterns refer to the process by which adapters, integration logic, and messaging take place in an integration environment. A good yardstick for support of integration patterns is the number of Enterprise Integration Patterns supported directly by the platform.
* ''Connectivity'': The connectivity category refers to the range of services (typically hosted through binding components and service engines) available to be used in Fuji. We need to get classic/popular adapters up and running in Fuji in order to demonstrate how it can be used directly in the 'real world' of customer environments.
* ''Complexity'': Fuji needs to be tested in complex scenarios involving multiple patterns and components to determine how the ease-of-use features scale up.
! Distributed Runtime
Creating a distributed NMR implementation provides a number of unique benefits to customers in how they partition components and provision applications in their ESB. The primary deliverable here is a 'proxy bundle' which federates the service address space between ESB instances and allows for transparent, distributed communication. Another important deliverable is education to users on the relationship of this approach to our clustering support.
New interceptor support which allows cross-cutting concerns such as logging, auditing, and security (to name a few) to be addressed in a modular fashion. Services can be enriched with additional functionality without changing the service implementation. More information can be found on the [Interceptors page|FujiInterceptorsInfo].
! Improved Tooling
Lots and lots of new NetBeans support to make developers more productive. Great new editing features for IFL and service configuration.
! More Distribution Options
Introduction of a "proxy" bundle which allows the ESB to extended through a distributed message bus. Learn more on the [Distributed JBI|FujiDJBI] page.
! Reactive Runtime
The platform detects application changes and automatically refreshes the deployed version of an application with updates. See the [ReactiveRuntime|FujiReactiveRuntime] page for more information.
! More service types
* Database
* SMTP
* FTP
* HL7
! IFL language enhancements
* Nested route definitions
* Support for inline and external configuration
* Added EIP keywords: split, aggregate, filter
G'day, Anonymous Guest

JSPWiki v2.4.100
[RSS]
« Home Index Changes Prefs
This page (revision-26) was last changed on 21-Nov-08 09:52 AM, -0800 by MarkWhite