> Ok, I've played a little more but I'm still at a loss. I > wrote a asp.net web service that works. My axis one still > doesn't. I've sniffed the traffic and here's what comes back: > ...
It sounds much worse I thought. What you said means I have nothing to play now with. You did all the job and it still doesn't work. > > You'll notice that the payload is the same. Well, it is > unless I'm missing something because I've been staring at it > for too long. The only differences are: > 1. The Microsoft <QueryResponse> has a default namespace of > urn:Microsoft.Search. Axis > names the namespace ns1 and prefixes it. > 2. Axis has an encoding style attribute that MS doesn't. Semantically both responces are the same but except for you mentioned about prefix difference there is also discrepancy in between return parameter tag name. Axis calls it QueryReturn and MS QueryResult. Since they both are described in corresponding WSDL correctly it mustn't influence on the situation but who knows? I have no idea what to test and if you read my previous post you'll get more confused. What MSOffice _really_ checks I don't know. Mysticism! Should we try asking on a MS forum? > Now, then, all of that being said, can anyone tell me why the > two bits of xml aren't functionally equivelent? > > Thanks! > > > >
