Web Services on Drugs

As I was trying to explain the difference between SOAPElement (a.k.a. XMLElement or Element in the java world) and Document, I got to realized that this know-how could be usefull when you need to access the content of the soap:header that is comming back from the service endpoint on the response. To illustrate this technique, I'll be using WS-Addessing and the .NET endpoint Microsoft exposes for testing purposes (http://131.107.72.15/WSAddressingCR_Service_WCF/WSAddressing10.svc). In my test scenario, the request looks like this <env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <env:Header> <wsa:Action xmlns:wsa="http://www.w3.org/2005/08/addressing">http://example.org/action/echoIn</wsa:Action> <wsa:ReplyTo xmlns:wsa="http://www.w3.org/2005/08/addressing"> <wsa:

This was my lunch plate, from koma-sushi in Menlo Park. I'll to see with my coach if this is a good lunch, based on my current exercise level [0 step/day] and my beer drinking exercise from the past days... I guess I really need to get the iPhone to have better picture quality.

I could not resist on this one... After seeing the PS3 vs WII ads on YouTube, I am getting used to the pattern. but the last " Get a Mac " clip on Surgery made my day. For me, the upgrade was not that painfull after all. just a few hours to scan and rescan the disk - I was using RC2, so it's one could expect as you move to the production release. Next week, I'll try to locate the anti-virus release of Symantec that's supported for Vista - it should be out by now. For me, the killer app on Vista remain the index on the outlook email that can be accessed from the start menu - Spotlight re-invented, just better. By the way, did you see the new iPhone, the phone re-invented, an ipod with a rotary wheel, like in the old days. When are we going to get iPod analog, for the vynil lovers?

I forgot to provide the answer on last quizz about invalid WSDL, and XML tips. The WSDL in question: http://www.rajkovic.org/ws/wsdl/bads/annotatedBank2.wsdl The issue: by mistake, I did reuse the same prefix for two namespace. The tns prefix is associated with 'http://ws.rajkovic.org/demo/annotatedBank' at the global scope (wsdl:definitions) and reused with 'http://ws.rajkovic.org/demo/annotatedBank/types' at the schema scope (xsd:schema element). In the wsdl:part, element="tns:create-account" references an element named {http://ws.rajkovic.org/demo/annotatedBank}create-account, which is not found. Based on the schema's targetNamespace, the QName (qualified name) of the element is {http://ws.rajkovic.org/demo/annotatedBank/types}create-account. There are two ways to fix this error: Uses the same targetNamespace URI (and tns prefix) for both WSDL and Schema elements. Keep It Simple as much as possible. Introduce a new prefixe in your wsdl:definition ele

As we get into 2007, it's time to take new resolutions, and make some predictions. Resolution: to post on this blog once a week, about Web Services and other rant. Prediction: 2007 will be the year of WS-*, the JAX-WS APIs and Java 6.0. Happy 2007 !!!