Re: WSDL file produces useless class when imported with WSDL.exe
From: Dino Chiesa [Microsoft] (dinoch_at_online.microsoft.com)
Date: 05/27/04
- Next message: Cheung, Jeffrey Jing-Yen: "COM object in webservice"
- Previous message: Arthur Nesterovsky: "re:ANN: Remote access to SourceSafe via web service."
- In reply to: RH: "WSDL file produces useless class when imported with WSDL.exe"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 27 May 2004 14:40:11 -0700
I can get it to work if I modify the wsdl in this way:
add these element definitions to the <types><xsd:schema> section
<xsd:element name="Request" type="FFE:UpdateTCSIncidentType" />
<xsd:element name="Response" type="FFE:UpdateTCSIncidentResponseType"
/>
Replace the messages definitions with these:
<message name="UpdateTCSIncident">
<part name="UpdateTCSIncident" element="FFE:Request" />
</message>
<message name="UpdateTCSIncidentResponse">
<part name="UpdateTCSIncidentResponse" element="FFE:Response" />
</message>
Maybe this will help?
-D
"RH" <anonymous@discussions.microsoft.com> wrote in message
news:9435AD2C-D4BD-48BE-B676-8059514AD37B@microsoft.com...
> I am having a problem with a WSDL file supplied by a client. When WSDL.exe
is used, the WSDL file (shown later) produces the following output class. As
you can see there are no methods. WSDL.exe does not raise any errors. There
either something wrong with the WSDL file or WSDL.exe. Anyone know what may
be wrong????
>
> The class generated with WSDL.exe.............................
>
>
//--------------------------------------------------------------------------
----
> // <autogenerated>
> // This code was generated by a tool.
> // Runtime Version: 1.1.4322.573
> //
> // Changes to this file may cause incorrect behavior and will be lost
if
> // the code is regenerated.
> // </autogenerated>
>
//--------------------------------------------------------------------------
----
>
> //
> // This source code was auto-generated by wsdl, Version=1.1.4322.573.
> //
> using System.Diagnostics;
> using System.Xml.Serialization;
> using System;
> using System.Web.Services.Protocols;
> using System.ComponentModel;
> using System.Web.Services;
>
>
> /// <remarks/>
> [System.Diagnostics.DebuggerStepThroughAttribute()]
> [System.ComponentModel.DesignerCategoryAttribute("code")]
> [System.Web.Services.WebServiceBindingAttribute(Name="FFEBinding",
Namespace="FFE")]
> public class FFEService :
System.Web.Services.Protocols.SoapHttpClientProtocol {
>
> /// <remarks/>
> public FFEService() {
> this.Url = "http://nslivdev1:8080/FFE";
> }
> }
>
>
> The WSDL file.............................
>
> <?xml version="1.0" encoding="UTF-8"?><definitions
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:FFE="FFE"
targetNamespace="FFE" name="FFE"><types><xsd:schema targetNamespace="FFE"
xmlns="FFE" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:SOAP-ENC="http://www.w3.org/2001/06/soap-encoding"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
elementFormDefault="qualified"><xsd:complexType
name="IncidentStcType"><xsd:all><xsd:element name="IncID"
type="xsd:string"/><xsd:element name="IncRef"
type="xsd:string"/><xsd:element name="SeqNum"
type="xsd:string"/><xsd:element name="FFEWorkId"
type="xsd:string"/><xsd:element name="LastUpdTime"
type="xsd:string"/></xsd:all></xsd:complexType><xsd:complexType
name="ResourceStcType"><xsd:all><xsd:element name="PayrollNum"
type="xsd:string"/><xsd:element name="ResID" type="xsd:string"/><xsd:element
name="FFEStatCode" type="xsd:string"/><xsd:element name="FFEStatName"
type="xsd:string"/><xsd:element name="ETA" type="xsd:string"/><xsd:element
name="ETR" type="xsd:string"/><xsd:element name="AOS"
type="xsd:string"/></xsd:all></xsd:complexType><xsd:complexType
name="NoteItemType"><xsd:all><xsd:element name="LogCatID"
type="xsd:string"/><xsd:element name="LogSubCatID"
type="xsd:string"/><xsd:element name="LogComment"
type="xsd:string"/></xsd:all></xsd:complexType><xsd:complexType
name="NotesType"><xsd:all><xsd:element name="Notes"
type="FFE:NoteItemType"/></xsd:all></xsd:complexType><xsd:complexType
name="UpdateTCSIncidentStcType"><xsd:all><xsd:element name="IncidentStc"
type="FFE:IncidentStcType"/><xsd:element name="ResourceStc"
type="FFE:ResourceStcType"/><xsd:element name="Notes"
type="FFE:NotesType"/></xsd:all></xsd:complexType><xsd:complexType
name="UpdateTCSIncidentType"><xsd:all><xsd:element
name="UpdateTCSIncidentStc"
type="FFE:UpdateTCSIncidentStcType"/></xsd:all></xsd:complexType><xsd:comple
xType name="UpdateTCSIncidentResponseStcType"><xsd:all><xsd:element
name="Status" type="xsd:int"/></xsd:all></xsd:complexType><xsd:complexType
name="UpdateTCSIncidentResponseType"><xsd:all><xsd:element
name="UpdateTCSIncidentResponseStc"
type="FFE:UpdateTCSIncidentResponseStcType"/></xsd:all></xsd:complexType></x
sd:schema></types><message name="UpdateTCSIncident"><part
name="UpdateTCSIncident"
type="FFE:UpdateTCSIncidentType"/></message><message
name="UpdateTCSIncidentResponse"><part name="UpdateTCSIncidentResponse"
type="FFE:UpdateTCSIncidentResponseType"/></message><portType
name="FFEPortType"><operation name="UpdateTCSIncident"><input
message="FFE:UpdateTCSIncident"/><output
message="FFE:UpdateTCSIncidentResponse"/></operation></portType><binding
name="FFEBinding" type="FFE:FFEPortType"><soap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/><operation
name="UpdateTCSIncident"><soap:operation
soapAction="http://nslivdev1:8080/FFE"/><input><soap:body
use="literal"/></input><output><soap:body
use="literal"/></output></operation></binding><service
name="FFEService"><port name="FFEPort"
binding="FFE:FFEBinding"><soap:address
location="http://nslivdev1:8080/FFE"/></port></service></definitions>
- Next message: Cheung, Jeffrey Jing-Yen: "COM object in webservice"
- Previous message: Arthur Nesterovsky: "re:ANN: Remote access to SourceSafe via web service."
- In reply to: RH: "WSDL file produces useless class when imported with WSDL.exe"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
