Hi Hannes, As discussed earlier, I was able to run the testsuite1 sample using Kandula.
I did have a good look at the specifications as you mentioned. I also read the following: http://www.ibm.com/developerworks/library/ws-wstx1/ http://www-128.ibm.com/developerworks/library/ws-wstx2/ which actually gives a good understanding about the how the activation, registration and coordination service are invoked. But this was specific to IBM related product. I was trying to align the same flow with Kandula as per the coordination services are concerned. Regards, Anshuk Pal Chaudhuri -----Original Message----- From: Hannes Erven [mailto:[EMAIL PROTECTED] Sent: Sunday, June 29, 2008 4:37 AM To: [email protected] Cc: Pal Chaudhuri, Anshuk (Cognizant) Subject: Re: Issues while compiling src code Hi Anshuk, > What I am not clear is the flow how exactly the client creates the > co-ordination context and so on. I'm not sure what you are exactly looking for and what you already know or have read. As a general starting point, I suggest you have a look at the WS-Coordination specification and also WS-AtomicTransaction or WS-BusinessActivity, whatever transaction type you are interested in. In the source code, at the Kandula server it all starts at org.apache.kandula.coordinator.CoordinationService#createCoordinationCon text , this is where the call from the client is received. From there, the actual transaction coordinator object is created depending on the requested type of transaction. If you have further questions or need reading tips, please reply with more details what you are interested in. Best regards and thank you for your interest in Kandula, -hannes This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorised review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
