A WS-Addressing namespace issue

At a customer’s integration solution, we’re trying to make a SOAP-request from a message flow. The web service has been created using WSE 3.0 (Web Service Enhancements) and requires WS-Addressing. We added a web service invoking sub flow by creating a project using the WSDL. Then we created a proper policy set, a UserName token and a matching binding. Using the Axis TCP Monitor we were able to get the input and output to and from the request.

Even though everything seemed to fit, we got an error message back from the service:

After digging around on a number of blogs, forums and Information Centers, we found the issue: The WS-Addressing namespace. WSE 3.0 sets the WSA-ns to:
http://schemas.xmlsoap.org/ws/2004/08/addressing

while WMB 6.1 uses:
http://www.w3.org/2005/08/addressing

Since the WS-Addressing feature cannot be configured we decided to contact the developer of the web service to see if he can change the namespace (or perhaps remove WSA altogether). As a last resort we’d probably have to download Axis (which is used by WMB when communicating with web services) and change the namespace constant. An update is soon to come..

Embedding jetty

For the Zystems component Testline, a testing utility used to run system tests on integrations, I’ve begun developing a Http server pod (point of delivery). After a few hints from my colleagues I began working on connecting Testline with the Jetty server. It was real easy to embed, the site has a wiki where, amongst a couple of tutorials, one can find:

http://docs.codehaus.org/display/JETTY/Embedding+Jetty

Now all I have to do is to specify how the integration will communicate with the server. We’ve been talking a lot about creating a web service pod as well, probably using axis.

Speaking of web services; I’ve been working my ¤%£ off implementing WS-Security at a client. It’s a little tricky but we’ll fix it soon. My first project for Zystems is working out really well. The people I work with really know what they’re doing!