Undefined Value Parameters -- asp.net webservices

asp.net webservices : Undefined Value Parameters

jeff NO[at]SPAM cumpsty.co.uk
2/19/2007 6:39:23 AM

I have a web service, which I have written. It is being called By a
client who used Apache Axis version: 1.2alpha.

When I place a breakpoint in the web method, my parameter is
identified as "<undefined value>".

I thought it might have been the SoapParameterStyle settings but I
have tried all options.

Does anyone have any ideas?

Thanks

jeff NO[at]SPAM cumpsty.co.uk
2/19/2007 7:34:21 AM

Can anyone tell me what the difference between these is... (apart from
the obvious). THanks.

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/
envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<...>
</soapenv:Body>
</soapenv:Envelope>

and

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:wsa="http://
schemas.xmlsoap.org/ws/2004/03/addressing" xmlns:wsse="http://
docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-
secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/
oasis-200401-wss-wssecurity-utility-1.0.xsd">
<soap:Header>
<...>
</soap:Header>
<soap:Body>
<...>
</soap:Body>
</soap:Envelope>

John Saunders
2/19/2007 2:21:43 PM

[quoted text, click to view]

The only differences in what you showed us is that one has a header and one
does not.

All of the other namespace declarations are irrelevant in the context you
provided us, because they are not used. Perhaps the difference lies in the
part you didn't show us.

BTW, it appears that you are aware that the most likely cause of "undefined
value" is a difference in namespace between what your service expects and
what's being sent.

John

jeff NO[at]SPAM cumpsty.co.uk
2/20/2007 12:50:06 AM

Thanks for the reply.

What I am thinking is that one uses "<Soap:" and the other
"<Soapenv:".

Would I be correct in thinking that one is Soap 1.1, and the other is
Soap1.2?

How can I tell my web service that it will be called using the 1.2
syntax?

jeff NO[at]SPAM cumpsty.co.uk
2/20/2007 4:33:13 AM

OK. Thanks.

Any idea of what this error means?

<soap:Body>
<soap:Fault>
<faultcode>soap:Server</faultcode>
<faultstring>Server was unable to process request. --> Item
has already been added. Key in dictionary:
&quot;CheckDeliverRequest&quot; Key being added:
&quot;CheckDeliverRequest&quot;</faultstring>
<detail />
</soap:Fault>
</soap:Body>

I get it whenever I try to name the parameter in my web method to be
the same as the matching element in the soap message.

John Saunders
2/20/2007 1:41:39 PM

[quoted text, click to view]

Is "CheckDeliverRequest" a method in your code?

John

John Saunders
2/20/2007 1:42:23 PM

[quoted text, click to view]

No. The prefix doesn't matter in any way. The only thing that matters is
what namespace the prefix maps to. In both cases, it was the same namespace.

John

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about asp.net webservices

View Other Months
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008

home · blog · groups

Questions? Comments? Contact the dn