468,309 Members | 1,078 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 468,309 developers. It's quick & easy.

Client code w/wsdl.exe

I use wsdl.exe to generate client code to call a web service. The actual web
service is generated with the BizTalk Web Services Publishing Wizard.

I'm not sure this is particular to the BizTalk code but the calls to web
methods pass parameters by ref so that I have to call it like:

XmlDocument doc = new XmlDocument();

doc.LoadXml(message);

XmlNode node = doc.DocumentElement.ParentNode;

ws.MyMethod(ref node);

I attempt to modify the generated client code so that the parameter is not
passed by ref and is instead returned as a response but I keep getting an
"object not referenced" error.

Is there a way to tell wsdl.exe to not generate a "ref" parameter?

Is the problem I describe just because this is calling a BizTalk web service
or have others seen this?

Mar 14 '07 #1
5 4721
"Nick K." <nk*****@msn.comwrote in message
news:uS**************@TK2MSFTNGP04.phx.gbl...
>I use wsdl.exe to generate client code to call a web service. The actual
web service is generated with the BizTalk Web Services Publishing Wizard.

I'm not sure this is particular to the BizTalk code but the calls to web
methods pass parameters by ref so that I have to call it like:

XmlDocument doc = new XmlDocument();

doc.LoadXml(message);

XmlNode node = doc.DocumentElement.ParentNode;

ws.MyMethod(ref node);

I attempt to modify the generated client code so that the parameter is not
passed by ref and is instead returned as a response but I keep getting an
"object not referenced" error.

Is there a way to tell wsdl.exe to not generate a "ref" parameter?

Is the problem I describe just because this is calling a BizTalk web
service or have others seen this?
If WSDL.EXE is generating a "ref" parameter, then the chances are that it
needs to be a "ref" parameter.

Have you taken a look into the WSDL file to see what it says about this
parameter?

John
Mar 14 '07 #2
I'm not sure I see anything so I will just show the entire wsdl, hopefully
someone can find something that will show me what to change in the wsdl to
change so that I not pass the parameter by ref:

<?xml version="1.0" encoding="utf-8" ?>

- <wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:tns="http://tempuri.org"
xmlns:s1="http://schemas.microsoft.com/BizTalk/2003/Any"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
targetNamespace="http://tempuri.org"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">

<wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">BizTalk
assembly "MyMethod, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=54556428737eb89f" published web service.</wsdl:documentation>

- <wsdl:types>

- <s:schema elementFormDefault="qualified"
targetNamespace="http://tempuri.org">

<s:import namespace="http://schemas.microsoft.com/BizTalk/2003/Any" />

- <s:element name="MyMethod">

- <s:complexType>

- <s:sequence>

<s:element minOccurs="0" maxOccurs="1" ref="s1:Root" />

</s:sequence>

</s:complexType>

</s:element>

- <s:element name="MyMethodResponse">

- <s:complexType>

- <s:sequence>

<s:element minOccurs="0" maxOccurs="1" ref="s1:Root" />

</s:sequence>

</s:complexType>

</s:element>

</s:schema>

- <s:schema elementFormDefault="qualified"
targetNamespace="http://schemas.microsoft.com/BizTalk/2003/Any">

- <s:element name="Root">

- <s:complexType mixed="true">

- <s:sequence>

<s:any />

</s:sequence>

</s:complexType>

</s:element>

</s:schema>

</wsdl:types>

- <wsdl:message name="MyMethodSoapIn">

<wsdl:part name="parameters" element="tns:MyMethod" />

</wsdl:message>

- <wsdl:message name="MyMethodSoapOut">

<wsdl:part name="parameters" element="tns:MyMethodResponse" />

</wsdl:message>

- <wsdl:portType name="TransportOrdersWSSoap">

- <wsdl:operation name="MyMethod">

<wsdl:input message="tns:MyMethodSoapIn" />

<wsdl:output message="tns:MyMethodSoapOut" />

</wsdl:operation>

</wsdl:portType>

- <wsdl:binding name="TransportOrdersWSSoap"
type="tns:TransportOrdersWSSoap">

<soap:binding transport="http://schemas.xmlsoap.org/soap/http" />

- <wsdl:operation name="MyMethod">

<soap:operation soapAction="http://tempuri.org/WebService_MyMethod/MyMethod"
style="document" />

- <wsdl:input>

<soap:body use="literal" />

</wsdl:input>

- <wsdl:output>

<soap:body use="literal" />

</wsdl:output>

</wsdl:operation>

</wsdl:binding>

- <wsdl:binding name="TransportOrdersWSSoap12"
type="tns:TransportOrdersWSSoap">

<soap12:binding transport="http://schemas.xmlsoap.org/soap/http" />

- <wsdl:operation name="MyMethod">

<soap12:operation
soapAction="http://tempuri.org/WebService_MyMethod/MyMethod"
style="document" />

- <wsdl:input>

<soap12:body use="literal" />

</wsdl:input>

- <wsdl:output>

<soap12:body use="literal" />

</wsdl:output>

</wsdl:operation>

</wsdl:binding>

- <wsdl:service name="TransportOrdersWS">

<wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">BizTalk
assembly "MyMethod, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=54556428737eb89f" published web service.</wsdl:documentation>

- <wsdl:port name="TransportOrdersWSSoap"
binding="tns:TransportOrdersWSSoap">

<soap:address
location="http://localhost/TransportOrdersWS/TransportOrdersWS.asmx" />

</wsdl:port>

- <wsdl:port name="TransportOrdersWSSoap12"
binding="tns:TransportOrdersWSSoap12">

<soap12:address
location="http://localhost/TransportOrdersWS/TransportOrdersWS.asmx" />

</wsdl:port>

</wsdl:service>

</wsdl:definitions>

"John Saunders" <john.saunders at trizetto.comwrote in message
news:eW*************@TK2MSFTNGP05.phx.gbl...
"Nick K." <nk*****@msn.comwrote in message
news:uS**************@TK2MSFTNGP04.phx.gbl...
>>I use wsdl.exe to generate client code to call a web service. The actual
web service is generated with the BizTalk Web Services Publishing Wizard.

I'm not sure this is particular to the BizTalk code but the calls to web
methods pass parameters by ref so that I have to call it like:

XmlDocument doc = new XmlDocument();

doc.LoadXml(message);

XmlNode node = doc.DocumentElement.ParentNode;

ws.MyMethod(ref node);

I attempt to modify the generated client code so that the parameter is
not passed by ref and is instead returned as a response but I keep
getting an "object not referenced" error.

Is there a way to tell wsdl.exe to not generate a "ref" parameter?

Is the problem I describe just because this is calling a BizTalk web
service or have others seen this?

If WSDL.EXE is generating a "ref" parameter, then the chances are that it
needs to be a "ref" parameter.

Have you taken a look into the WSDL file to see what it says about this
parameter?

John


Mar 14 '07 #3
"Nick K." <nk*****@msn.comwrote in message
news:O2*************@TK2MSFTNGP02.phx.gbl...
I'm not sure I see anything so I will just show the entire wsdl, hopefully
someone can find something that will show me what to change in the wsdl to
change so that I not pass the parameter by ref:
You should not change the WSDL. It does not "belong" to you. It belongs to
BizTalk. It represents the contract that BizTalk is willing to enforce
between the world, and the BizTalk web service.

I looked at the WSDL (please don't paste from IE next time. The "-" signs
make it useless as an XML file). I suspect that the issue is that both the
input and output messages have a single part named "parameters", and that
both "parameters" have the same type. It is saying that "parameters" are
input and then "parameters" are output, which in .NET terms is "ref".

In other words, the server side isn't broken. Is there some reason you don't
want to use "ref"?

John
Mar 14 '07 #4
The lead that gave me the requirements for the web services did not define a
ref parameter. This web service would be called by others that I have no
clue as to their development environment. Would "ref" pose a problem in
environments other than Microsoft?

"John Saunders" <john.saunders at trizetto.comwrote in message
news:e6**************@TK2MSFTNGP03.phx.gbl...
"Nick K." <nk*****@msn.comwrote in message
news:O2*************@TK2MSFTNGP02.phx.gbl...
>I'm not sure I see anything so I will just show the entire wsdl,
hopefully someone can find something that will show me what to change in
the wsdl to change so that I not pass the parameter by ref:

You should not change the WSDL. It does not "belong" to you. It belongs to
BizTalk. It represents the contract that BizTalk is willing to enforce
between the world, and the BizTalk web service.

I looked at the WSDL (please don't paste from IE next time. The "-" signs
make it useless as an XML file). I suspect that the issue is that both the
input and output messages have a single part named "parameters", and that
both "parameters" have the same type. It is saying that "parameters" are
input and then "parameters" are output, which in .NET terms is "ref".

In other words, the server side isn't broken. Is there some reason you
don't want to use "ref"?

John


Mar 14 '07 #5
"Nick K." <nk*****@msn.comwrote in message
news:uk**************@TK2MSFTNGP03.phx.gbl...
The lead that gave me the requirements for the web services did not define
a ref parameter. This web service would be called by others that I have no
clue as to their development environment. Would "ref" pose a problem in
environments other than Microsoft?
No, "ref" won't cause a problem because there is no "ref" in the WSDL. Only
an operation with both input and output parameters having the same name and
type.

John
Mar 15 '07 #6

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

7 posts views Thread by Christian Wilhelm | last post: by
reply views Thread by jennifer.perkins | last post: by
reply views Thread by NPC403 | last post: by
reply views Thread by Teichintx | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.