[Ws Wiki] Update of "FrontPage/ws-kandula/kandula2" by thilinagunarathne

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

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

The following page has been changed by thilinagunarathne:
http://wiki.apache.org/ws/FrontPage/ws-kandula/kandula2

New page:
= Kandula2 =

Proposal for Kandula2, a web services  project for implementing WS-Coordination, WS-Atomic Transaction & WS-Business Activity on top of Axis2.

== Rationale ==

The target of Kandula project was to implement WS-Coordination, WS-Atomic Transaction & WS-Business Activity for Axis 1.x. Kandula implementation lacks the mandatory asynchronous support due to axis 1.x not supporting one way messaging.Since Axis2 is about to make 1.0 release we believe it is the time to start working on a Kandula implementation for it using it's asynchronous support.

This implementation will have a simple participant implementation, which will be indepedent of the participants backend transaction implementation, and a initiator implementation which will use simple axis server to host services needed for the asynchronous communication.

=== Proposed Coordinator Architecture (WS-AT only) ===

Kandula2 coordinator implementation will be an stateless coordinator with a context hierachy.

http://people.apache.org/~thilina/images/kandula2Coordinator.jpg

 * The core of the coordinator will be independent of Axis2.
 * All the logic needed for transaction processing will be in stateless coordinators, which makes the implementation much more scalable.
 * Data Binding layer will provide the extensibility to plugging code generated using diffrent data binding tools.
 * Storage layer will take care of storing the contexts through out the life span of the transaction. This will be either Axis2 service context or a choice of a user (even a database).


=== Proposed Participant Architecture (WS-AT) ===
This will be a simple standalone participant impl which can be used with any native transaction implementation.

http://people.apache.org/~thilina/images/participant.jpg

 * The user needs to provide implementations of the 2PhaseCommit interface to each and every  operations he wish to provide transactional support.
 * Transaction handler will take care of registering with the coordinator when receving a application message with a coordination context.


=== Proposed Initiator Architecture ===

This will use Simple Axis Server to host the services needed for the asynchronous messaging. 


This implementation will be followed by the WS-Business Activity Implementation, which will have a architecture similar to above.

http://people.apache.org/~thilina/sourcecode/kandula2/Kandula2.rar contains an initial code base (There are some problems with generated code for wsdl's)