Interoperability

The other day I posted asking anyone for any additional information regarding the syntax of the policy file that you can create with IBM WSTK Version 3.3 to sign, encrypt, add a username Token, etc. to a SoapHeader on an outgoing Soap from a java client so that you can interoperate with .Net following the WS-Security specification put together by Microsoft, IBM and Verisign. Didn't get any. That's ok.

Frustrated, I searched for another avenue and I came across BEA Worshop Version 8.1. It was awesome. I downloaded it, installed it, created a project, imported my WSDL, and called my web service following an implemented security policy in like 3.5 hours. So if others out there are interested in checking out the interoperability for themselves, I recommend Workshop. You will actually notice some high-level similarities b/w Visual Studio and Workshop.

Note: If the documentation on how to put together the policy file with WSTK (renamed to ETTK in August) was right in front of my nose, my humblest apologies. I do believe interoperability is important, so please set me straight. Seriously.