Showing posts from January, 2007

Access to SOAP Header from response payload

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 (

In my test scenario, the request looks like this
<env:Envelope xmlns:env="" xmlns:xsd="" xmlns:xsi="">
<wsa:Action xmlns:wsa=""></wsa:Action>
<wsa:ReplyTo xmlns:wsa="">

Did I hear Raw Food ?

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.

Upgrading to Vista today ...

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?

Invalid WSDL - and the answer is ...

I forgot to provide the answer on last quizz about invalid WSDL, and XML tips.

The WSDL in question:

The issue: by mistake, I did reuse the same prefix for two namespace. The tns prefix is associated with ''
at the global scope (wsdl:definitions) and reused with ''
at the schema scope (xsd:schema element).

In the wsdl:part, element="tns:create-account" references an element named {}create-account, which is not found. Based on the schema's targetNamespace, the QName (qualified name) of the element is {}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 element (xm…

Happy New Year

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 !!!