Anshuk, Have a look at:
http://131.107.72.15/ilab/TX/WCFInteropPlugFest_TX.doc The interopIBM example was written to carry out these interop tests. So you will find the code useful. Thanks, -- dasarath -----Original Message----- Hi, Thanks Dasarath for your input. Yeah, I am digging more into the interoperability issues. I would definitely be interested in submitting a document on the R&D work that I am currently doing in Web Services Transaction. What I am currently testing is the both way interoperability.ie. Client à Kandula WS Client (within the axis and Tomcat container) à IBM InsertOne WS (within the IBM WAS container) à InsertTwo Web Service using Kandula (within axis and tomcat) As discussed earlier, the IBM WS would insert a record in a table in the database and the InsertTwo Kandula WS would insert one more record in a different table. The above mentioned grey highlighted part is working fine, i.e. Kandula Client and IBM WS Web Service. But when the IBM WS (now becomes client for the next web service) is trying to invoke the InsertTwo Kandula WS (the highlighted red part), there is an issue. This issues is more of IBM problem (I am not sure whether you were talking this IBM issue earlier or not J J) , because the transaction framework of IBM while sending the transaction context details in the SOAP Request Header sends CoordinationContextType instead of the CoordinationContext (which should be as per the actual specification) , and eventually the transaction handler by kandula is not able to understand the same. I am not sure why exactly IBM has done this kind of an implementation which is not strictly adhering to standards. To this, there is a workaround, which I read at http://opensource.sys-con.com/read/314083.htm, part of which states that "Sometimes, vendors provide service packs or refresh packs to overcome discrepancies in the released version of the product. These packs might bring in changes in the supported specifications. These changes might break the existing interoperability or enable interoperability where it was absent earlier. For example, IBM WebSphere Application Server (WAS) 6.0 supports the element <CoordinationContextType> for WS-AT, but when the refresh pack 6.0.2.9 is applied over it, the supported element changes to <CoordinationContext>. You should analyze all such changes in the refresh packs before deciding to apply these packs." So I am currently trying to update the same with 6.0.2.9 refresh pack, not sure how successful it would really be. Let's see. Regards, Anshuk Pal Chaudhuri -----Original Message----- From: Dasarath Weeratunge [mailto:[EMAIL PROTECTED] Sent: Friday, July 18, 2008 7:52 PM To: Pal Chaudhuri, Anshuk (Cognizant) Cc: [email protected] Subject: RE: Issues while compiling src code Quoting [EMAIL PROTECTED]: --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
