Hi Hannes,
I was thinking the testsuite sample could be reused in the below mentioned scenario which I am trying to achieve. I was reading http://ws.apache.org/kandula/1/ws-at--how_to_use.html " This sample application demostrates how to use Kandula to initiate and terminate transactions using the WS-AtomicTransaction protocol. It also demostrates the behaviour of Kandula under a number of failure scenarios. Note that we use pseudo XAResouces instead of actual applications such as Databases, Messaging etc. to simplify the testing process. Hence the application explicitly enlists all XAResources used in operations. This would not be the case with real applications however. The container would normally takecare of this for you, transparently." So in this case, the container would the was app server and that would take care of the transactions. I have generated the stubs using axis wsdl2java form the web service wsdl. But what I am not sure is how to use the Kandula in this specific case. Please let me know. Thanking you in advance. Regards, Anshuk Pal Chaudhuri -----Original Message----- From: Pal Chaudhuri, Anshuk (Cognizant) Sent: Wednesday, July 09, 2008 1:04 PM To: 'Hannes Erven'; [email protected] Subject: RE: Issues while compiling src code Hi Hannes, Thanks for your input. I did try out using the atomic transaction that comes with the IBM WAS 6.0. The web service would insert some values in a database. The web service client was built using the stubs generated by the IBM SOAP Engine WSDL2Java and configured in such a way so that it would send atomic transaction details in the soap envelope. So, I tested a good scenario and the values got inserted in the table. While testing the error scenario, in the web service after the part of the which does the insertion, I threw a runtime exception explicitly and when I checked the tables, the values were not inserted. Now I intend to do a similar scenario using Apache Kandula at the client side. The same web service (deployed on WAS) would be used, but the client would now send the soap request using apache Kandula and the necessary transaction details (within the soap header) would be sent. I did have a look at the documentation, but I am not exactly sure what needs to be done. Can you help/guide me in testing the above. Thanking you in advance. 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.
