Hi Jack,
> In http://ws.apache.org/kandula/, it said: " Presently, the implementation > only supports atomic > transaction coordination type. Business activities will be supported in > future.", so calling two > methods distributed at two machine, as illustrated following, is not > supported yet, isn's it ? Atomic Transaction / Business Activity refers only to the semantic of the transaction. http://www.ibm.com/developerworks/library/ws-comproto/ gives an overview of these transaction protocol types (skip the BTP part ;-]) As for Kandula, you can - even today - add an unlimited number of participants, distributed onto as many machines as you like, to both atomic and business activity contexts. (Business activities are not yet supported in the code, but the framework for participant registration is the same.) The kandula.context has to refer - as Dasarath wrote - to your running *local* Kandula services so that remote participants know where to send messages for you. Even a standalone application that uses Kandula needs to run a small standlone web server to receive SOAP messages from transaction participants. (AFAIK is a standalone web server included somewhere in the distribution...) Georg Hicker and I offered to implement the WS-BusinessActivity protocol modules for Kandula (we're doing this for our diploma thesis). Currently we seem to be in a similar situation as you are: we are trying to set everything up and complete some simple test cases before doing real work. I guess Summer 2006 is a good time to check back on WS-BusinessActivitiy availability status in Kandula. -hannes --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
