Modifying WSDL Response Element

[Mike]

I have a web service being consume by a new client. The WebMethod they are
calling is called Process.

So in the WSDL I have has 2 elements, Process and ProcessResponse .

<s:schema elementFormDefa ult="qualified"
targetNamespace ="http://www.test.com/">
<s:import namespace="http ://www.test.com/" />
<s:element name="Process">
<s:complexTyp e>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" ref="s1:TPVRequ est" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="ProcessRe sponse">
<s:complexTyp e>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" ref="s1:Process Result" />
</s:sequence>
</s:complexType>
</s:element>
</s:schema>

My client wants the result of ProcessResponse , "ProcessRes ult" to be named
something else.

Inside my webservice how do I dictate what the result element is going to be
names?

I hope this makes sense to you guys :)

Thanks a lot in advance,

Mike

[erymuzuan]

You can save the generated wsdl, then change it accordingly, I would
recommend using XMLSpy or other WSDL authoring tool, then regenerate the
server stub using wsdl.exe /server, You'll have to disable the wsdl auto
generation, add "remove" the documentation in web.config

regards
erymuzuan mustapa

Mike wrote:

I have a web service being consume by a new client. The WebMethod they are
calling is called Process.

So in the WSDL I have has 2 elements, Process and ProcessResponse .

<s:schema elementFormDefa ult="qualified"
targetNamespace ="http://www.test.com/">
<s:import namespace="http ://www.test.com/" />
<s:element name="Process">
<s:complexTyp e>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" ref="s1:TPVRequ est" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="ProcessRe sponse">
<s:complexTyp e>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" ref="s1:Process Result" />
</s:sequence>
</s:complexType>
</s:element>
</s:schema>

My client wants the result of ProcessResponse , "ProcessRes ult" to be named
something else.

Inside my webservice how do I dictate what the result element is going to be
names?

I hope this makes sense to you guys :)

Thanks a lot in advance,

Mike

[Dino Chiesa [Microsoft]]

you can do all of that. but it is not required.
There are attributes that you can attach to your existing Webmethod and
webservice.

example: this sets the element name and namespace of both the request and
response .

[SoapDocumentMet hod
("",
RequestElementN ame="RequestEle ment",
ResponseElement Name="ResponseE lement",
RequestNamespac e="urn:MyReques tNamespace"
ResponseNamespa ce= "urn:MyResponse Namespace",
Use=System.Web. Services.Descri ption.SoapBindi ngUse.Literal,
ParameterStyle= System.Web.Serv ices.Protocols. SoapParameterSt yle.Wrapped)]

check the msdn doc on the SoapDocumentMet hodAttribute
http://msdn.microsoft.com/library/en...classtopic.asp

-Dino

"erymuzuan" <er*******@yaho o.com> wrote in message
news:eX******** *****@TK2MSFTNG P15.phx.gbl...

You can save the generated wsdl, then change it accordingly, I would
recommend using XMLSpy or other WSDL authoring tool, then regenerate the
server stub using wsdl.exe /server, You'll have to disable the wsdl auto
generation, add "remove" the documentation in web.config

regards
erymuzuan mustapa

Mike wrote:

I have a web service being consume by a new client. The WebMethod they
are calling is called Process.

So in the WSDL I have has 2 elements, Process and ProcessResponse .

<s:schema elementFormDefa ult="qualified"
targetNamespace ="http://www.test.com/">
<s:import namespace="http ://www.test.com/" />
<s:element name="Process">
<s:complexTyp e>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" ref="s1:TPVRequ est" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="ProcessRe sponse">
<s:complexTyp e>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" ref="s1:Process Result" />
</s:sequence>
</s:complexType>
</s:element>
</s:schema>

My client wants the result of ProcessResponse , "ProcessRes ult" to be
named something else.

Inside my webservice how do I dictate what the result element is going to
be names?

I hope this makes sense to you guys :)

Thanks a lot in advance,

Mike

[erymuzuan]

My recommendation is using WSDL 1st approach. but this may be out of
reach to certain people especially beginners to Web Services. So working
this mickey mouse way may help them to understand the process of
creating a lasting and good web services. especially the relationship
between schemas, messages and port types.

regards
erymuzuan mustap

Dino Chiesa [Microsoft] wrote:

you can do all of that. but it is not required.
There are attributes that you can attach to your existing Webmethod and
webservice.

example: this sets the element name and namespace of both the request and
response .

[SoapDocumentMet hod
("",
RequestElementN ame="RequestEle ment",
ResponseElement Name="ResponseE lement",
RequestNamespac e="urn:MyReques tNamespace"
ResponseNamespa ce= "urn:MyResponse Namespace",
Use=System.Web. Services.Descri ption.SoapBindi ngUse.Literal,
ParameterStyle= System.Web.Serv ices.Protocols. SoapParameterSt yle.Wrapped)]

check the msdn doc on the SoapDocumentMet hodAttribute
http://msdn.microsoft.com/library/en...classtopic.asp

-Dino

"erymuzuan" <er*******@yaho o.com> wrote in message
news:eX******** *****@TK2MSFTNG P15.phx.gbl...

You can save the generated wsdl, then change it accordingly, I would
recommend using XMLSpy or other WSDL authoring tool, then regenerate the
server stub using wsdl.exe /server, You'll have to disable the wsdl auto
generation, add "remove" the documentation in web.config

regards
erymuzuan mustapa

Mike wrote:

I have a web service being consume by a new client. The WebMethod they
are calling is called Process.

So in the WSDL I have has 2 elements, Process and ProcessResponse .

<s:schema elementFormDefa ult="qualified"
targetNamesp ace="http://www.test.com/">
<s:import namespace="http ://www.test.com/" />
<s:element name="Process">
<s:complexTyp e>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" ref="s1:TPVRequ est" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="ProcessRe sponse">
<s:complexTyp e>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" ref="s1:Process Result" />
</s:sequence>
</s:complexType>
</s:element>
</s:schema>

My client wants the result of ProcessResponse , "ProcessRes ult" to be
named something else.

Inside my webservice how do I dictate what the result element is going to
be names?

I hope this makes sense to you guys :)

Thanks a lot in advance,

Mike

[Dino Chiesa [Microsoft]]

Yes, I agree that "WSDL First" is preferred for interoperabilit y.
In this case, the SoapDocumentAtt ribute may be sufficient to do the job. We
are talking only about the response element here.

Either way works. The "WSDL First" approach is a bit of an uphill struggle
with the current set of tools. For example wsdl.exe /server generates an
abstract class. You might think to just inherit from this class and then
provide your concrete implementation, but this will not work, because the
..NET webservices runtime depends on the attributes being attached to the
class itself. The .NET runtime will not interrogate and utilize the
attributes on the generated class, if you inherit from it. So in effect you
must cut-and-paste all the attributes from the generated type into your
derived type. Or, alternatively, modify the generated file to remove the
"abstract" and provide implementations directly.

In short, you have to "fight the tools" in order to practice WSDL first,
today. So for this reason I recommend it for people who are comfortable
doing so, where interop is a key priority.

If it is just the substitution of one element name for another, then the use
of an inline attribute should be fine. And simpler.
-Dino

"erymuzuan" <er*******@yaho o.com> wrote in message
news:eM******** ******@tk2msftn gp13.phx.gbl...

My recommendation is using WSDL 1st approach. but this may be out of reach
to certain people especially beginners to Web Services. So working this
mickey mouse way may help them to understand the process of creating a
lasting and good web services. especially the relationship between
schemas, messages and port types.

regards
erymuzuan mustap

Dino Chiesa [Microsoft] wrote:

you can do all of that. but it is not required.
There are attributes that you can attach to your existing Webmethod and
webservice.

example: this sets the element name and namespace of both the request and
response .

[SoapDocumentMet hod
("",
RequestElementN ame="RequestEle ment",
ResponseElement Name="ResponseE lement",
RequestNamespac e="urn:MyReques tNamespace"
ResponseNamespa ce= "urn:MyResponse Namespace",
Use=System.Web. Services.Descri ption.SoapBindi ngUse.Literal,

ParameterStyle= System.Web.Serv ices.Protocols. SoapParameterSt yle.Wrapped)]

check the msdn doc on the SoapDocumentMet hodAttribute
http://msdn.microsoft.com/library/en...classtopic.asp

-Dino

"erymuzuan" <er*******@yaho o.com> wrote in message
news:eX******** *****@TK2MSFTNG P15.phx.gbl...

You can save the generated wsdl, then change it accordingly, I would
recommend using XMLSpy or other WSDL authoring tool, then regenerate the
server stub using wsdl.exe /server, You'll have to disable the wsdl auto
generation , add "remove" the documentation in web.config

regards
erymuzuan mustapa

Mike wrote:

I have a web service being consume by a new client. The WebMethod they
are calling is called Process.

So in the WSDL I have has 2 elements, Process and ProcessResponse .

<s:schema elementFormDefa ult="qualified"
targetNames pace="http://www.test.com/">
<s:import namespace="http ://www.test.com/" />
<s:element name="Process">
<s:complexTyp e>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" ref="s1:TPVRequ est" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="ProcessRe sponse">
<s:complexTyp e>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" ref="s1:Process Result" />
</s:sequence>
</s:complexType>
</s:element>
</s:schema>

My client wants the result of ProcessResponse , "ProcessRes ult" to be
named something else.

Inside my webservice how do I dictate what the result element is going
to be names?

I hope this makes sense to you guys :)

Thanks a lot in advance,

Mike