incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Incubator Wiki] Update of "OdeProposal" by AlanCabrera
Date Tue, 14 Feb 2006 07:25:33 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Incubator Wiki" for change notification.

The following page has been changed by AlanCabrera:
http://wiki.apache.org/incubator/OdeProposal

New page:
= PROJECT PROPOSAL =

Ode - Orchestration Director Engine 

"A lyric poem of some length, usually of a serious or meditative nature and 
having an elevated style and formal stanzaic structure". - American Heritage Dictionary

We are proposing an orchestration service that implements the WSBPEL 
specification. The implementation will also support Message/Event to process 
correlation

The project proposal includes development of an orchestration engine 
abstraction to standard externally defined interfaces/bindings. The interface 
implementations and/or bindings will enable the orchestration service to be 
plugged into various service bus or component architectures. 

= RATIONALE =

For a complete SOA stack, course-grained, long lived, service orchestration is 
an important aspect of service interaction.  WSBPEL is the standard description 
language for describing this level of service interaction.  While there is a 
lot of ongoing effort in Apache towards solving the assembly and bus 
architecture issues of SOA, the higher level orchestration integration aspect 
could be better served.

= INITIAL SOURCE =

The initial source for Ode originates from a Sybase donation that generically 
implements a superset of the academically recognized workflow patterns that are 
a superset of WSBPEL yet adhere to specific WSBPEL v1.1 language constructs. 
The initial source contribution does not require any WSBPEL extensions and is 
opaque with respect to the orchestration process context types.

The initial source fully implements the BPEL v1.1 specification however there are some things
to do:

 1. Implement specific service bus plug-ins.
 1. Implement a non-J2EE persistence mechanism for stateful processes running outside a J2EE
container.
 1. Port to BPEL 2.0 once the specification is public.

= RESOURCES TO BE CREATED =

 * SVN Repository
 * Jira
 * Mailing Lists
 * Official Build Systems


= ALIGNMENT =

We propose growing the Apache SOA stack through integration with Serivce Mix, Axis,
Tuscany, Celtix, etc ... 

The proposed implementation will solely focus on service orchestration. We will 
implement the appropriate plug-in points for a specific ESB or component 
architecture. This would include exposing BPEL definitions as a service, enable 
the consumption of services by a BPEL process and exposure of BPEL management 
services.

= AVOIDING THE WARNING SIGNS =

== Orphaned products: ==

The core of the donated code is used within a commercially viable product and 
receives constant feedback.  The project will be actively supported both by the 
current committers and those in the community actively seeking to leverage 
orchestration with the SOA stack.   The BPEL 2.0 specification is a diverse and 
active community and we anticipate continued interest in the orchestration of 
Web Services and integration with other Apache projects. 

The Eclipse foundation has formed a BPEL tooling project (http://www.eclipse.org/bpel/) 
that will help visualize service orchestration and add to service orchestration interest.

== Inexperience with open source: ==

Many of the current committers have experience working with open source projects and communities
and the leaders of this project are long time ASF contributors. We do not expect any difficulty
in executing under normal meritocracy rules.

== Homogenous developers: ==

There are developers from various companies: Sybase, IBM, LogicBlaze...

== No ties to other Apache products: ==

We are anticipating that the service orchestration engine will be used within 
a larger SOA stack (i.e. ServiceMix, Tuscany, Synapse). To that end we will 
actively work with other projects to define and implement the appropriate 
plug-in points/bindings/abstractions orchestration

For QoS features the Ode project will leverage Geronimo backbones (transaction 
management, security, threading).

= Initial COMMITTERS =

 * Alan Cabrera (Simula Labs), adc@apache.org - Member of Geronimo PMC and Directory Committer
 * Hiram Chirino (LogicBlaze), chirino@apache.org - Member of Geronimo PMC
 * Rob Davies (LogicBlaze)
 * Guillaume Nodet (LogicBlaze)
 * Dain Sundstrom (IBM) dain@apache.org - Member of Geronimo PMC and JDO Committer

 
= PROPOSED APACHE SPONSOR =

The Apache Geronimo PMC has voted to accept this project into the Apache Geronimo project
upon successful incubation.

= MENTORS =

 * James Strachan

---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org


Mime
View raw message