Author: dasarath
Date: Sat Feb 25 20:41:15 2006
New Revision: 381052
URL: http://svn.apache.org/viewcvs?rev=381052&view=rev
Log: (empty)
Modified:
webservices/kandula/site/index.html
Modified: webservices/kandula/site/index.html
URL:
http://svn.apache.org/viewcvs/webservices/kandula/site/index.html?rev=381052&r1=381051&r2=381052&view=diff
==============================================================================
--- webservices/kandula/site/index.html (original)
+++ webservices/kandula/site/index.html Sat Feb 25 20:41:15 2006
@@ -1,112 +1,84 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";><html><head><title>Kandula
- Kandula - Apache Kandula</title><style type="text/css" media="all">
- @import url("./style/maven-base.css");
-
- @import
url("./style/maven-theme.css");</style><link rel="stylesheet"
href="./style/print.css" type="text/css" media="print"></link><meta
http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1"></meta></head><body class="composite"><div id="banner"><a
href="http://ws.apache.org/"; id="organizationLogo"><img alt="Apache Web
Services" src="http://ws.apache.org/images/project-logo.jpg";></img></a><a
href="http://ws.apache.org/ws-fx/kandula/"; id="projectLogo"><span>Apache
Kandula</span></a><div class="clear"><hr></hr></div></div><div
id="breadcrumbs"><div class="xleft">
- Last published: 14 June 2005
- | Doc for 0.1-SNAPSHOT</div><div class="xright"></div><div
class="clear"><hr></hr></div></div><div id="leftColumn"><div
id="navcolumn"><div id="menuKandula"><h5>Kandula</h5><ul><li class="none"><a
href="user-guide.html">User Guide</a></li><li class="none"><a
href="architecture-guide.html">Architecture Guide</a></li></ul></div><div
id="menuProject_Documentation"><h5>Project Documentation</h5><ul><li
class="none"><strong><a href="index.html">About Apache
Kandula</a></strong></li><li class="collapsed"><a
href="project-info.html">Project Info</a></li><li class="collapsed"><a
href="maven-reports.html">Project Reports</a></li><li class="none"><a
href="http://maven.apache.org/development-process.html"; class="externalLink"
title="External Link">Development Process</a></li></ul></div><a
href="http://maven.apache.org/"; title="Built by Maven" id="poweredBy"><img
alt="Built by Maven"
src="./images/logos/maven-button-1.png"></img></a></div></div>
-
-
-
- <div id="bodyColumn">
- <div class="contentBox">
- <div class="section">
- <a name="Apache_Kandula"></a>
- <h2>Apache Kandula</h2>
- <div class="subsection">
- <a name="Purpose"></a><h3>Purpose</h3>
- <p align="justify">
- Kandula will provide an open-source implementation of
WS-Coordination,
- WS-AtomicTransaction and WS-BusinessActivity based on Axis.
- The initial implementation will be in Java using Axis/Java.
- In addition to providing an implementation, a major focus of
- this project would be to ensure interoperability with other
- implementations of above specifications, particularly those
by Microsoft
- (.NET) and IBM.</p><p align="justify">
- </p><a name="Objectives"></a><h3>Objectives</h3><p
align="justify">The Kandula project has two main objectives:</p><div
align="justify">
- <ol type="1">
- <li>Provide an open source
- implementation for the web services coordination and transaction
management
- frameworks defined by WS-Coordination, WS-<span>AtomicTransaction and
WS-<span>BusinessActivity.</span></span></li>
- <li>Integrate existing open
- source JTA implementations (e.g. JOTM, JBoss,
- Geronimo, etc.) with the web services transaction management framework
so that
- J2EE web services and clients may take part in atomic transactions while
using
- JTA for transaction management</li>
- </ol>
- <p> </p>
-</div><a name="Overview"></a><h3>Overview</h3><p align="justify">Think of a
hypothetical web service that provides banking
-services. The service provides 2 operations: a credit
-operation and a debit
-operation. Now if the two operations are to be used to perform a monetary
-transfer between two accounts, it must be ensured that either both operations
-succeed or neither does. Under these circumstances, the web services
-coordination framework can be used to ensure the atomicity of operations. The
-sample code below shows how a standalone client may use the Kandula
implementation
-in this scenario-</p><p>
- <div class="source"><pre>public class ... implements SessionBean {
-private SessionContext ctx;
- public void setSessionContext(SessionContext ctx) {
- this.ctx= ctx;
- }
- public ... foo(....) {
- Bank bank= new BankServiceLocator().getBank();
- UserTransaction ut= ctx.getUserTransaction();
- ut.begin();
- try {
- bank.credit(1001, 10);
- bank.debit(1002, 10);
- }catch (Exception e) {
- ut.rollback();
- }
- ut.commit();
- }
-}
-</pre></div>
- </p><p align="justify"></p><p align="justify">The web services coordination
framework describes how web
-services may join in and participate in coordinated activities. It also
-stipulates how participants may reach collective agreement on the ultimate
-outcome of such activities.</p><p align="justify">Though the framework is
platform independent, participant
-services unavoidably need to use numerous incompatible, platform-specific
-technologies to perform transactional work. For instance, if the banking
service
-mentioned above is implemented in J2EE, its implementation would use JTA
-distributed transactions necessarily. Hence in the context of coordinated
-activities, the underlying JTA runtime is required to coordinate with an
-external coordinator to decide if and when to make any work performed as part
of
-such activities, persistent. The Kandula provides this capability by
integrating
-with existing transaction managers so that JTA distributed transactions
started
-locally may be coordinated by an external coordinator through the web services
-coordination framework.</p><p align="justify">Furthermore, the Kandula runtime
is also capable of implicitly
-propagating the local transaction context of a calling thread on web service
-invocations. This allows distributed transactions to be propagated across
-heterogeneous application domains. To illustrate this point consider how the
-same use case illustrated above would be implemented by a J2EE client.</p><p>
- <div class="source"><pre>
-public class ... implements SessionBean {
- private SessionContext ctx;
- public void setSessionContext(SessionContext ctx) {
- this.ctx= ctx;
- }
- public ... foo(....) {
- Bank bank= new BankServiceLocator().getBank();
- UserTransaction ut= ctx.getUserTransaction();
- ut.begin();
- try {
- bank.credit(1001, 10);
- bank.debit(1002, 10);
- }catch (Exception e) {
- ut.rollback();
- }
- ut.commit();
- }
-}</pre></div>
- </p><p align="justify">Notice that the component uses JTA to ensure
atomicity of
-operations. At runtime however, the transaction context of the calling thread
is
-propagated to the remote service using the web services coordination
-framework.</p><p align="justify"> </p></div>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title>Kandula - Kandula - Apache Kandula</title>
+ <style type="text/css" media="all">
[EMAIL PROTECTED] url("./style/maven-base.css");
-
-
-</div></div></div>
-
-
-<div class="clear"><hr></hr></div><div id="footer"><div class="xright">©
2004-2005, Apache Web Services</div><div
class="clear"><hr></hr></div></div></body></html>
\ No newline at end of file
[EMAIL PROTECTED] url("./style/maven-theme.css");</style>
+ <link rel="stylesheet" href="./style/print.css" type="text/css"
media="print">
+ <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+</head>
+<body class="composite">
+ <div id="banner">
+ <a href="http://ws.apache.org/"; id="organizationLogo">
+ <img alt="Apache Web Services"
src="http://ws.apache.org/images/project-logo.jpg";></a>
+ <div class="clear">
+ <hr>
+ </div>
+ </div>
+ <div id="breadcrumbs">
+ <div class="xleft">
+ Last published: 26th Feb 2006</div>
+ <div class="xright">
+ </div>
+ <div class="clear">
+ <hr>
+ </div>
+ </div>
+ <div id="leftColumn">
+ <div id="navcolumn">
+ <div id="menuKandula">
+ <h5>
+ Kandula</h5>
+ <ul>
+ <li class="none"><a href="user-guide.html">Kandula1</a>
</li>
+ <li class="none"><a href="user-guide.html">Kandula2</a>
</li>
+ </ul>
+ </div>
+ <a href="http://maven.apache.org/"; title="Built by Maven"
id="poweredBy">
+ <img alt="Built by Maven"
src="./images/logos/maven-button-1.png">
+ </a>
+ </div>
+ </div>
+ <div id="bodyColumn">
+ <div class="contentBox">
+ <div class="section">
+ <a name="Apache_Kandula"></a>
+ <h2>
+ Apache Kandula</h2>
+ <div class="subsection">
+ <h3>
+ Introduction</h3>
+ <p>
+ The Apche Kandula project implements WS-Coordination,
WS-AtomicTransaction and WS-BusinessActivity
+ protocols based on Apache Axis and Axis2. Further,
+ when deployed in a J2EE environment, Kandula
AtomicTransaction implementation together
+ with the J2EE transaction manager, allows JTA to be
used for coordinating and
+ participating in web services transactions. This
feature is a Kandula
+ extension to JSR 109.</p>
+ <p>
+ Presently Kandula implements WS-Coordination and
WS-AtomicTransaction protocols.
+ WS-BusinessActivity protocol will be available in the
near future. We also strive
+ to ensure the interoperability of our implementation
with other (often proprietory)
+ implementations of above specifications, particularly
those by Microsoft (.NET)
+ and IBM.</p>
+ <p>
+ Kandula project has 2 branches. Kandula1 branch runs
on Apache Axis 1.x.
+ Kandula2 branch (new) runs on Apache Axi2.</p>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div class="clear">
+ <hr>
+ </div>
+ <div id="footer">
+ <div class="xright">
+ © 2004-2005, Apache Web Services</div>
+ <div class="clear">
+ <hr>
+ </div>
+ </div>
+</body>
+</html>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
![http://ws.apache.org/images/project-logo.jpg"](http://ws.apache.org/images/project-logo.jpg"){kind=link}