473,546 Members | 2,196 Online
Bytes | Software Development & Data Engineering Community
+ Post

Home Posts Topics Members FAQ

WSDL Generation Error

I have run into a problem generating the class file via the WSDL utility. I
have a WSDL file that was generated by XMLSpy and is able to be read by the
Java code utility, but I get the following error from the WSDL utility.

Error: Unable to import binding 'REMSOAPHttpsBi nding' from namespace
'http://www.fnfis.com/services/Services-Common/REM/20040109/v1.0'. - The
operation 'REMCorporation BPOOrder' on portType 'REMInterface' from namespace
'http://www.fnfis.com/services/Services-Common/REM/20040109/v1.0' had the
following syntax error: The operation has no matching binding. Check if the
operation, input and output names in the Binding section match with the
corresponding names in the PortType section.

<message name="REMReques tSOAPIn">
<part name="REMReques tPart" element="ns:Pla ceBPOOrderREM"/>
</message>
<message name="REMReques tSOAPInMSPMARKU pdate">
<part name="REMReques tPart" element="ns:Pla ceBPOOrderREMMS PMARKUpdate"/>
</message>
<message name="REMReques tSOAPInMSPAPR1U pdate">
<part name="REMReques tPart" element="ns:Pla ceBPOOrderREMMS PAPR1Update"/>
</message>
<message name="REMRespon seSOAPOut">
<part name="REMRespon sePart" element="ns:Pla ceBPOOrderREMRe sponse"/>
</message>
<portType name="REMInterf ace">
<operation name="REMCorpor ationBPOOrder">
<input name="REMReques tIn" message="tns:RE MRequestSOAPIn"/>
<output name="REMRespon seOut" message="tns:RE MResponseSOAPOu t"/>
</operation>
<operation name="REMCorpor ationBPOOrderWi thMSPMarkUpdate ">
<input name="REMReques tIn" message="tns:RE MRequestSOAPInM SPMARKUpdate"/>
<output name="REMRespon seOut" message="tns:RE MResponseSOAPOu t"/>
</operation>
<operation name="REMCorpor ationBPOOrderWi thMSPAPR1Update ">
<input name="REMReques tIn" message="tns:RE MRequestSOAPInM SPAPR1Update"/>
<output name="REMRespon seOut" message="tns:RE MResponseSOAPOu t"/>
</operation>
</portType>

I did find that if I take the “name” attribute out from the input elements
that the WSDL utility works perfectly

<portType name="REMInterf ace">
<operation name="REMCorpor ationBPOOrder">
<input message="tns:RE MRequestSOAPIn"/>
<output message="tns:RE MResponseSOAPOu t"/>
</operation>
<operation name="REMCorpor ationBPOOrderWi thMSPMarkUpdate ">
<input message="tns:RE MRequestSOAPInM SPMARKUpdate"/>
<output message="tns:RE MResponseSOAPOu t"/>
</operation>
<operation name="REMCorpor ationBPOOrderWi thMSPAPR1Update ">
<input message="tns:RE MRequestSOAPInM SPAPR1Update"/>
<output message="tns:RE MResponseSOAPOu t"/>
</operation>
</portType>
Is this a bug in the WSDL utility or is our WSDL file poorly generated and
that Java simply ignores the additional name attribute and the WSDL utility
throws an error when seeing it.

I am trying to settle an argument if this is a WDSL utility bug versus a
poorly generated WSDL file.

Thanks
Scott
Jun 1 '06 #1
13 3406
>I have run into a problem generating the class file via the WSDL utility.
I
have a WSDL file that was generated by XMLSpy and is able to be read by
the
Java code utility, but I get the following error from the WSDL utility.

Error: Unable to import binding 'REMSOAPHttpsBi nding' from namespace


Can you post the complete WSDL?
Seems like some wsdl-soap-bindings missing.

--
Happy Hacking,
Gaurav Vaish
http://www.mastergaurav.org
http://webservices.edujini.in
-------------------
Jun 1 '06 #2
The site indicates that the post is to large and they have a limit of 30000
characters. The WSDL file is about 40K in size.

I will be posting the WSDL file is two parts.

Part 1

<?xml version="1.0" encoding="UTF-8"?>
<!-- edited with XMLSPY v2004 rel. 3 U (http://www.xmlspy.com) by Carol
Turner (Fidelity Information Services) -->
<!-- last edited 6/14/2005 3:11 PM -->
<definitions xmlns="http://schemas.xmlsoap .org/wsdl/"
xmlns:soap="htt p://schemas.xmlsoap .org/wsdl/soap/"
xmlns:http="htt p://schemas.xmlsoap .org/wsdl/http/"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:tns="http ://www.fnfis.com/services/Services-Common/REM/20040109/v1.0"
xmlns:ns="http://www.fnfis.com/services/Services-Common"
targetNamespace ="http://www.fnfis.com/services/Services-Common/REM/20040109/v1.0">
<types>
<xs:schema xmlns="http://www.fnfis.com/services/Services-Common"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
targetNamespace ="http://www.fnfis.com/services/Services-Common"
elementFormDefa ult="unqualifie d" attributeFormDe fault="unqualif ied"
version="1.0">
<xs:complexTy pe name="PropertyC ontact__Type">
<xs:complexCont ent>
<xs:extension base="Contact__ Type">
<xs:sequence>
<xs:element name="Type" type="Party__Ty pe"/>
</xs:sequence>
</xs:extension>
</xs:complexConte nt>
</xs:complexType>
<xs:complexTy pe name="GeneralCo ntact__Type">
<xs:sequence>
<xs:element name="Name" type="Name__Typ e"/>
<xs:element name="HomeNumbe r" type="Telephone Number__Type"/>
<xs:element name="WorkNumbe r" type="Telephone Number__Type"/>
<xs:element name="FaxNumber " type="Telephone Number__Type" minOccurs="0"/>
<xs:element name="MobileNum ber" type="Telephone Number__Type"
minOccurs="0"/>
<xs:element name="EmailAddr ess" type="EmailAddr ess__Type" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
<xs:complexTy pe name="Address__ Type">
<xs:sequence>
<xs:element name="StreetAdd ress" type="StreetAdd ress__Type"/>
<xs:element name="StreetAdd ress2" type="StreetAdd ress__Type"
minOccurs="0"/>
<xs:element name="City" type="City__Typ e"/>
<xs:element name="County" type="County__T ype" minOccurs="0"/>
<xs:element name="State" type="StateAbbr eviation__Type"/>
<xs:element name="PostalCod e" type="PostalCod e__Type"/>
</xs:sequence>
</xs:complexType>
<xs:simpleTyp e name="PostalCod e__Type">
<xs:restricti on base="xs:string ">
<xs:pattern value="\d{5}(-\d{4})?"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleTyp e name="StateAbbr eviation__Type" >
<xs:restricti on base="xs:string ">
<xs:pattern value="[A-Z]{2}"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleTyp e name="Telephone Number__Type">
<xs:restricti on base="xs:string ">
<xs:pattern value="\d{3} \d{3}-\d{4}"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleTyp e name="UnparsedN ame__Type">
<xs:restricti on base="xs:string ">
<xs:maxLength value="90"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleTyp e name="EmailAddr ess__Type">
<xs:restricti on base="xs:string ">
<xs:pattern value="\w([\-._]*\w)*@\w[\-._\w]*\w\.\w{2,3}"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleTyp e name="Party__Ty pe">
<xs:restricti on base="xs:string ">
<xs:enumerati on value="APP">
<xs:annotatio n>
<xs:documentati on>Applicant</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
<xs:enumerati on value="ATNY">
<xs:annotatio n>
<xs:documentati on>Attorney</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
<xs:enumerati on value="BLDR">
<xs:annotatio n>
<xs:documentati on>Builder</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
<xs:enumerati on value="BORR">
<xs:annotatio n>
<xs:documentati on>Buyer/Borrower</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
<xs:enumerati on value="BYAGNT">
<xs:annotatio n>
<xs:documentati on>Buying Agent</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
<xs:enumerati on value="COAPP">
<xs:annotatio n>
<xs:documentati on>Co Applicant</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
<xs:enumerati on value="LEND">
<xs:annotatio n>
<xs:documentati on>Lender</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
<xs:enumerati on value="LOANOFF" >
<xs:annotatio n>
<xs:documentati on>Loan Officer</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
<xs:enumerati on value="LOANPRO" >
<xs:annotatio n>
<xs:documentati on>Loan Processor</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
<xs:enumerati on value="LSAGNT">
<xs:annotatio n>
<xs:documentati on>Listing Agent</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
<xs:enumerati on value="MORT">
<xs:annotatio n>
<xs:documentati on>Mortgage Broker</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
<xs:enumerati on value="REAL">
<xs:annotatio n>
<xs:documentati on>Realtor</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
<xs:enumerati on value="SELL">
<xs:annotatio n>
<xs:documentati on>Seller/Owner</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
<xs:enumerati on value="PROP">
<xs:annotatio n>
<xs:documentati on>Property Contact</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
<xs:complexTy pe name="Name__Typ e">
<xs:sequence>
<xs:element name="FirstName ">
<xs:simpleTyp e>
<xs:restricti on base="xs:string ">
<xs:maxLength value="30"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="MiddleNam e" minOccurs="0">
<xs:simpleTyp e>
<xs:restricti on base="xs:string ">
<xs:maxLength value="30"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="LastName" >
<xs:simpleTyp e>
<xs:restricti on base="xs:string ">
<xs:maxLength value="30"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
</xs:sequence>
</xs:complexType>
<xs:complexTy pe name="LiteConta ct__Type">
<xs:sequence>
<xs:element name="UnparsedN ame" type="UnparsedN ame__Type"/>
<xs:element name="WorkNumbe r" type="Telephone Number__Type"/>
</xs:sequence>
</xs:complexType>
<xs:simpleTyp e name="SSN__Type ">
<xs:restricti on base="xs:string ">
<xs:pattern value="(\d{2}-\d{7})|(\d{3}-\d{2}-\d{4})"/>
</xs:restriction>
</xs:simpleType>
<xs:complexTy pe name="TypedCont act__Type">
<xs:complexCont ent>
<xs:extension base="Contact__ Type">
<xs:sequence>
<xs:element name="Type" type="Party__Ty pe"/>
</xs:sequence>
</xs:extension>
</xs:complexConte nt>
</xs:complexType>
<xs:complexTy pe name="Contact__ Type">
<xs:complexCont ent>
<xs:extension base="GeneralCo ntact__Type">
<xs:sequence>
<xs:element name="SSNTaxIde ntifier" type="SSN__Type " minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexConte nt>
</xs:complexType>
<xs:complexTy pe name="ParsedStr eetAddress__Typ e">
<xs:sequence>
<xs:element name="HouseNumb er" type="xs:string "/>
<xs:element name="PrefixDir ection" type="xs:string " minOccurs="0"/>
<xs:element name="StreetNam e" type="xs:string "/>
<xs:element name="StreetTyp e" type="xs:string " minOccurs="0"/>
<xs:element name="SuffixDir ection" type="xs:string " minOccurs="0"/>
<xs:element name="Unit" type="xs:string " minOccurs="0"/>
</xs:sequence>
</xs:complexType>
<xs:complexTy pe name="ParsedAdd ress__Type">
<xs:complexCont ent>
<xs:extension base="ParsedStr eetAddress__Typ e">
<xs:sequence>
<xs:element name="City">
<xs:simpleTyp e>
<xs:restricti on base="xs:string ">
<xs:maxLength value="30"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="County" minOccurs="0">
<xs:simpleTyp e>
<xs:restricti on base="xs:string ">
<xs:maxLength value="30"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="State" type="StateAbbr eviation__Type"/>
<xs:element name="PostalCod e" type="PostalCod e__Type"/>
</xs:sequence>
</xs:extension>
</xs:complexConte nt>
</xs:complexType>
<xs:simpleTyp e name="City__Typ e">
<xs:restricti on base="xs:string ">
<xs:maxLength value="30"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleTyp e name="County__T ype">
<xs:restricti on base="xs:string ">
<xs:maxLength value="30"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleTyp e name="Amount__T ype">
<xs:restricti on base="xs:decima l">
<xs:fractionDig its value="2"/>
<xs:totalDigi ts value="15"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleTyp e name="StreetAdd ress__Type">
<xs:restricti on base="xs:string ">
<xs:maxLength value="60"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleTyp e name="Reference Number__Type">
<xs:restricti on base="xs:string ">
<xs:maxLength value="30"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleTyp e name="PINAPNNum ber__Type">
<xs:restricti on base="xs:string ">
<xs:maxLength value="30"/>
</xs:restriction>
</xs:simpleType>
<xs:complexTy pe name="RequestCo ntext__Type">
<xs:annotatio n>
<xs:documentati on>This RequestContext element for which this is a type
will be used to carry general meta-information about a message for
authentication/tracking/auditing and reconciling requests to responses.
Additional information pertaining to the locale of the client and the
region(prod/test) of the mainframe environment to use can be specified
here.</xs:documentatio n>
</xs:annotation>
<xs:sequence>
<xs:element name="Correlati onId" type="xs:string " minOccurs="0">
<xs:annotatio n>
<xs:documentati on>
<!-- The client generates this ID for their own tracking/auditing.
Allows the client to co-relate a response with a request for request-response
reconciliation-->
</xs:documentatio n>
</xs:annotation>
</xs:element>
<xs:element name="UserCompa ny" type="xs:string ">
<xs:annotatio n>
<xs:documentati on>
<!-- Identifier assigned by Fidelity and stored in the message by
the client. Fidelity uses this identifier for authorization and routing. If
specified, it must match the authenticated user company specified by the X509
certificate. The clients will require to send this information until such
time as the infrastructure is able to extract this information out of the
certificate. -->
</xs:documentatio n>
</xs:annotation>
</xs:element>
<xs:element name="UserId" type="xs:string ">
<xs:annotatio n>
<xs:documentati on>A system-level or user-level userid that Fidelity
uses to authorize the request. This userid must be authenticated by the user
company (the client application); it is not authenticated by Fidelity.
</xs:documentatio n>
</xs:annotation>
</xs:element>
<xs:element name="Credentia ls" minOccurs="0">
<xs:annotatio n>
<xs:documentati on>This element allows the client to specify a stored
configuraton for the infrastructure to use to retrieve credentials for the
request, or allows the client to provide explicit credentials. If none are
specified, then the infrastructure determines the credentials for the request
based on the UserCompany, Provider. and UserId. </xs:documentatio n>
</xs:annotation>
<xs:complexType >
<xs:sequence>
<xs:element name="Registere dCredential" type="xs:string "
minOccurs="0" maxOccurs="unbo unded">
<xs:annotatio n>
<xs:documentati on>This element will be used to specify an existing
authentication configuration. </xs:documentatio n>
</xs:annotation>
</xs:element>
<xs:element name="MSPCreden tialList" minOccurs="0">
<xs:complexType >
<xs:sequence>
<xs:element name="SystemId" type="xs:string " minOccurs="0">
<xs:annotatio n>
<xs:documentati on>Indicates the region to which the credentials
apply (e.g. "test" vs "prod"). Default is production</xs:documentatio n>
</xs:annotation>
</xs:element>
<xs:element name="MSPCreden tial" type="MSPSystem Credential__Typ e"
minOccurs="0" maxOccurs="unbo unded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="Applicati onId" minOccurs="0">
<xs:annotatio n>
<xs:documentati on>For requests originating in internal Fidelity
applications, this identifies the internal application making the request,
for tracking/auditing RPC usage. </xs:documentatio n>
</xs:annotation>
<xs:simpleTyp e>
<xs:restricti on base="xs:string ">
<xs:minLength value="3"/>
<xs:maxLength value="8"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="Channel" type="Channel__ Type" minOccurs="0">
<xs:annotatio n>
<xs:documentati on>For requests originating in internal Fidelity
applications, this identifies the channel from which the request originated
(WEB, CSR, or VRU). Currently, used only by PHD</xs:documentatio n>
</xs:annotation>
</xs:element>
<xs:element name="Originato r" type="xs:string " minOccurs="0">
<xs:annotatio n>
<xs:documentati on>Client-provided text used only for
auditing/tracking. From a client perspective, this refers to the originator
of the request for the client.</xs:documentatio n>
</xs:annotation>
</xs:element>
<xs:element name="Provider" type="xs:string ">
<xs:annotatio n>
<xs:documentati on>Specifies the system or company providing the
Service operation specified in the request. The Provider is a mandatory
element and does not indicate the MSP client number for the
request.</xs:documentatio n>
</xs:annotation>
</xs:element>
<xs:element name="Locale" type="LocaleInf o__Type" minOccurs="0">
<xs:annotatio n>
<xs:documentati on>specifies the client locale. Default is
en_US</xs:documentatio n>
</xs:annotation>
</xs:element>
<xs:element name="Reference Data" type="xs:anyTyp e" minOccurs="0">
<xs:annotatio n>
<xs:documentati on>The client can provide arbitrary structured data in
this element, to have the data logged for tracking/auditing, or to have the
data echoed in the response. e.g. datetime the request was sent
etc.</xs:documentatio n>
</xs:annotation>
</xs:element>
<xs:element name="EchoReque stContextFlag" type="xs:boolea n"
minOccurs="0">
<xs:annotatio n>
<xs:documentati on>The client specifies whether the request context
will be echoed in the response</xs:documentatio n>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
<xs:complexTy pe name="ResponseC ontext__Type">
<xs:sequence>
<xs:element name="MessageId " type="xs:string ">
<xs:annotatio n>
<xs:documentati on>
<!-- Fidelity generates this ID and returns it in a response. For
asynchronous requests and orders, the client must use this ID to retrieve the
response/order. This ID is a UUID. -->
</xs:documentatio n>
</xs:annotation>
</xs:element>
<xs:element name="Correlati onId" type="xs:string " minOccurs="0">
<xs:annotatio n>
<xs:documentati on>
<!-- Echoes the correlation ID that was provided by the client in
the input message, if any. -->
</xs:documentatio n>
</xs:annotation>
</xs:element>
<xs:element name="SoftwareV ersionNumber" type="xs:string ">
<xs:annotatio n>
<xs:documentati on>This element will be used to tie the software build
version with this version of the schema</xs:documentatio n>
</xs:annotation>
</xs:element>
<xs:element name="RequestCo ntext" type="RequestCo ntext__Type"
minOccurs="0">
<xs:annotatio n>
<xs:documentati on>Echoes the corresponding request context of the
input message, if any, if the input message Echo element specified
CONTEXT.</xs:documentatio n>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
<xs:complexTy pe name="LocaleInf o__Type">
<xs:sequence>
<xs:element name="ISOCountr yCode" minOccurs="0">
<xs:simpleTyp e>
<xs:restricti on base="xs:string ">
<xs:enumerati on value="US"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="ISOLangua geCode" minOccurs="0">
<xs:simpleTyp e>
<xs:restricti on base="xs:string ">
<xs:enumerati on value="en"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="localeVar iant" type="xs:string " minOccurs="0"/>
</xs:sequence>
</xs:complexType>
<xs:simpleTyp e name="Channel__ Enum">
<xs:restricti on base="xs:string ">
<xs:enumerati on value="Web"/>
<xs:enumerati on value="CSR"/>
<xs:enumerati on value="VRU"/>
</xs:restriction>
</xs:simpleType>
<xs:complexTy pe name="Channel__ Type">
<xs:simpleConte nt>
<xs:extension base="Channel__ Enum"/>
</xs:simpleConten t>
</xs:complexType>
<xs:simpleTyp e name="Event__En um">
<xs:restricti on base="xs:string ">
<xs:enumerati on value="Validate Order"/>
<xs:enumerati on value="PlaceOrd er"/>
<xs:enumerati on value="AcceptOr der"/>
<xs:enumerati on value="Conditio nallyAcceptOrde r"/>
<xs:enumerati on value="RejectOr der"/>
<xs:enumerati on value="CancelOr der"/>
<xs:enumerati on value="AcceptCa ncelRequest"/>
<xs:enumerati on value="DenyCanc elRequest"/>
<xs:enumerati on value="HoldOrde r"/>
<xs:enumerati on value="Provider HoldOrder"/>
<xs:enumerati on value="ResumeOr der"/>
<xs:enumerati on value="Complete Order"/>
<xs:enumerati on value="Comment"/>
<xs:enumerati on value="OrderDel ayed"/>
<xs:enumerati on value="ManualRe search"/>
<xs:enumerati on value="Unavaila bleData"/>
<xs:enumerati on value="Resubmit Order"/>
<xs:enumerati on value="Provider CancelOrder"/>
<xs:enumerati on value="UpgradeO rder"/>
<xs:enumerati on value="AcceptUp gradeRequest"/>
<xs:enumerati on value="DenyUpgr adeRequest"/>
<xs:enumerati on value="AddDataA ttachment"/>
<xs:enumerati on value="AddDocum entAttachment"/>
</xs:restriction>
</xs:simpleType>
<xs:complexTy pe name="Event__Ty pe">
<xs:simpleConte nt>
<xs:extension base="Event__En um"/>
</xs:simpleConten t>
</xs:complexType>
<xs:complexTy pe name="MSPSystem Credential__Typ e">
<xs:sequence>
<xs:element name="ClientId" type="xs:string ">
<xs:annotatio n>
<xs:documentati on>For MSP data, indicates the owner of the data to
which the credentials apply </xs:documentatio n>
</xs:annotation>
</xs:element>
<xs:element name="MSPId" type="xs:string " minOccurs="0">
<xs:annotatio n>
<xs:documentati on>For user level RACF IDs , the MSP Id can be
inferred based on the naming convention, but for system level RACF IDs, the
MSP ID can be explicitly specified</xs:documentatio n>
</xs:annotation>
</xs:element>
<xs:element name="RACFId" type="xs:string ">
<xs:annotatio n>
<xs:documentati on>used for Mainframe authentication</xs:documentatio n>
</xs:annotation>
</xs:element>
<xs:element name="RACFPassw ord" type="xs:string ">
<xs:annotatio n>
<xs:documentati on>used for Mainframe authentication</xs:documentatio n>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
<xs:simpleTyp e name="TaskID__T ype">
<xs:annotatio n>
<xs:documentati on> Identifies a type of task ( not necessarily a unique
task) for a loan</xs:documentatio n>
</xs:annotation>
<xs:restricti on base="xs:string ">
<xs:length value="6"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleTyp e name="ClientId_ _Type">
<xs:restricti on base="xs:string ">
<xs:length value="3"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleTyp e name="CurrencyC ode__Type">
<xs:restricti on base="xs:string ">
<xs:length value="3"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleTyp e name="LoanNumbe r__Type">
<xs:restricti on base="xs:string ">
<xs:maxLength value="13"/>
<xs:minLength value="6"/>
</xs:restriction>
</xs:simpleType>
<xs:complexTy pe name="ResponseS tatus__Type">
<xs:annotatio n>
<xs:documentati on>indicates whether the request was
successful</xs:documentatio n>
</xs:annotation>
<xs:sequence>
<xs:element name="StatusCod e">
<xs:annotatio n>
<xs:documentati on>The element will categorise the result codes into
predefined enumeration categories</xs:documentatio n>
</xs:annotation>
<xs:simpleTyp e>
<xs:restricti on base="xs:string ">
<xs:enumerati on value="Success"/>
<xs:enumerati on value="SystemEr ror"/>
<xs:enumerati on value="Communic ationError"/>
<xs:enumerati on value="RequestE rror"/>
<xs:enumerati on value="Authoriz ationError"/>
<xs:enumerati on value="Authenti cationError"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="ResultCod e" type="ResultCod e__Type">
<xs:annotatio n>
<xs:documentati on>The error code will indicate the 3 char error
category, 4 char system component that caused the error and 4 char error
number separated by hyphens</xs:documentatio n>
</xs:annotation>
</xs:element>
<xs:element name="ErrorMess age" type="xs:string " minOccurs="0"
maxOccurs="unbo unded">
<xs:annotatio n>
<xs:documentati on>one or more error messages related to a single
exception.</xs:documentatio n>
</xs:annotation>
</xs:element>
<xs:element name="Informati onalMessage" type="xs:string " minOccurs="0"
maxOccurs="unbo unded">
<xs:annotatio n>
<xs:documentati on>This element will indicate if there the RPC call
generated warnings or other informational messages. e.g. "This loan is not
available for foreclosure". This element may appear even when the status code
is 0(successs).</xs:documentatio n>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
<xs:complexTy pe name="ResponseH eader__Type">
<xs:sequence>
<xs:element name="Status" type="ResponseS tatus__Type"/>
</xs:sequence>
</xs:complexType>
<xs:simpleTyp e name="ResultCod e__Type">
<xs:restricti on base="xs:string "/>
</xs:simpleType>

"Gaurav Vaish (www.EduJini.IN )" wrote:
I have run into a problem generating the class file via the WSDL utility.
I
have a WSDL file that was generated by XMLSpy and is able to be read by
the
Java code utility, but I get the following error from the WSDL utility.

Error: Unable to import binding 'REMSOAPHttpsBi nding' from namespace


Can you post the complete WSDL?
Seems like some wsdl-soap-bindings missing.

--
Happy Hacking,
Gaurav Vaish
http://www.mastergaurav.org
http://webservices.edujini.in
-------------------

Jun 1 '06 #3
Part 2 of the WSDL file

<xs:element name="PlaceBPOO rderREMResponse ">
<xs:complexType >
<xs:sequence>
<xs:element name="ResponseC ontext" type="ResponseC ontext__Type"/>
<xs:element name="REMCorpor ationBPORs">
<xs:complexType >
<xs:sequence>
<xs:element name="ResponseH eader" type="ResponseH eader__Type"/>
<xs:element name="ResponseB ody" minOccurs="0">
<xs:complexType >
<xs:sequence>
<xs:element name="OrderId" type="xs:unsign edInt"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="PlaceBPOO rderREMMSPMARKU pdate"
type="PlaceBPOO rderREMMSPUpdat e__Type"/>
<xs:element name="PlaceBPOO rderREMMSPAPR1U pdate"
type="PlaceBPOO rderREMMSPUpdat e__Type"/>
<xs:element name="PlaceBPOO rderREM">
<xs:complexType >
<xs:sequence>
<xs:element name="RequestCo ntext" type="RequestCo ntext__Type"/>
<xs:element name="REMCorpor ationBPORq">
<xs:complexType >
<xs:sequence>
<xs:element name="RequestBo dy">
<xs:complexType >
<xs:sequence>
<xs:element name="REMBPOReq uest" type="REMBPOReq uest__Type"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexTy pe name="PlaceBPOO rderREMMSPUpdat e__Type">
<xs:sequence>
<xs:element name="RequestCo ntext" type="RequestCo ntext__Type"/>
<xs:element name="REMCorpor ationBPORqMSPUp date">
<xs:complexType >
<xs:sequence>
<xs:element name="RequestBo dy">
<xs:complexType >
<xs:sequence>
<xs:element name="REMBPOReq uestMSPUpdate"
type="REMBPOReq uestMSPUpdate__ Type"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
<xs:complexTy pe name="REMBPOReq uest__Type">
<xs:sequence>
<xs:element name="Borrower" >
<xs:complexType >
<xs:sequence>
<xs:element name="Name" type="Name__Typ e"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="Loan">
<xs:complexType >
<xs:sequence>
<xs:element name="Reference Number">
<xs:simpleTyp e>
<xs:restricti on base="xs:string ">
<xs:maxLength value="30"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="Property" >
<xs:complexType >
<xs:sequence>
<xs:element name="Address" type="Address__ Type"/>
<xs:element name="PropertyT ypeIndicator">
<xs:simpleTyp e>
<xs:restricti on base="xs:string ">
<xs:enumerati on value="1">
<xs:annotatio n>
<xs:documentati on>Single Family</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
<xs:enumerati on value="2">
<xs:annotatio n>
<xs:documentati on>Condo</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
<xs:enumerati on value="3">
<xs:annotatio n>
<xs:documentati on>2-4 Unit Residential</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="RoomsNumb er" type="xs:unsign edInt" minOccurs="0"/>
<xs:element name="BedroomsN umber" type="xs:unsign edInt"
minOccurs="0"/>
<xs:element name="Bathrooms Number" minOccurs="0">
<xs:simpleTyp e>
<xs:restricti on base="xs:string ">
<xs:pattern value="^\d*\.{0 ,1}\d$"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="Occupancy Indicator">
<xs:simpleTyp e>
<xs:restricti on base="xs:string ">
<xs:enumerati on value="1">
<xs:annotatio n>
<xs:documentati on>Owner</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
<xs:enumerati on value="2">
<xs:annotatio n>
<xs:documentati on>Tenant</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
<xs:enumerati on value="3">
<xs:annotatio n>
<xs:documentati on>Vacant</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="LivingAre aNumber" type="xs:unsign edInt"
minOccurs="0">
<xs:annotatio n>
<xs:documentati on>Square footage of the living
area.</xs:documentatio n>
</xs:annotation>
</xs:element>
<xs:element name="Contact">
<xs:complexType >
<xs:complexCont ent>
<xs:extension base="LiteConta ct__Type">
<xs:sequence>
<xs:element name="HomeNumbe r" type="Telephone Number__Type"
minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexConte nt>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="Product">
<xs:complexType >
<xs:sequence>
<xs:element name="Comment" minOccurs="0">
<xs:simpleTyp e>
<xs:restricti on base="xs:string ">
<xs:maxLength value="255"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="RushIndic ator" type="xs:boolea n"/>
<xs:element name="Type">
<xs:simpleTyp e>
<xs:restricti on base="xs:string ">
<xs:enumerati on value="11">
<xs:annotatio n>
<xs:documentati on>Exterior Market Valuation</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
<xs:enumerati on value="12">
<xs:annotatio n>
<xs:documentati on>Exterior Market Valuation with
Photos</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
<xs:enumerati on value="15">
<xs:annotatio n>
<xs:documentati on>Interior Market Valuation without
Photos</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
<xs:enumerati on value="16">
<xs:annotatio n>
<xs:documentati on>Interior Market Valuation with
Photos</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="Submittin gParty">
<xs:complexType >
<xs:sequence>
<xs:element name="Departmen t">
<xs:simpleTyp e>
<xs:restricti on base="xs:string ">
<xs:enumerati on value="99">
<xs:annotatio n>
<xs:documentati on>None</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
<xs:enumerati on value="10">
<xs:annotatio n>
<xs:documentati on>Bankruptcy</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
<xs:enumerati on value="20">
<xs:annotatio n>
<xs:documentati on>Foreclosure</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
<xs:enumerati on value="30">
<xs:annotatio n>
<xs:documentati on>Collections</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
<xs:enumerati on value="40">
<xs:annotatio n>
<xs:documentati on>Default Reporting</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
<xs:enumerati on value="50">
<xs:annotatio n>
<xs:documentati on>Loss Mitigation</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
<xs:enumerati on value="60">
<xs:annotatio n>
<xs:documentati on>FHA Per-Sale</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
<xs:enumerati on value="70">
<xs:annotatio n>
<xs:documentati on>REO</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
<xs:complexTy pe name="REMBPOReq uestMSPUpdate__ Type">
<xs:sequence>
<xs:element name="Borrower" >
<xs:complexType >
<xs:sequence>
<xs:element name="Name" type="Name__Typ e"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="Loan">
<xs:complexType >
<xs:sequence>
<xs:element name="Reference Number">
<xs:simpleTyp e>
<xs:restricti on base="xs:string ">
<xs:maxLength value="30"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="Property" >
<xs:complexType >
<xs:sequence>
<xs:element name="Address" type="Address__ Type"/>
<xs:element name="PropertyT ypeIndicator">
<xs:simpleTyp e>
<xs:restricti on base="xs:string ">
<xs:enumerati on value="1">
<xs:annotatio n>
<xs:documentati on>Single Family</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
<xs:enumerati on value="2">
<xs:annotatio n>
<xs:documentati on>Condo</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
<xs:enumerati on value="3">
<xs:annotatio n>
<xs:documentati on>2-4 Unit Residential</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="RoomsNumb er" type="xs:unsign edInt" minOccurs="0"/>
<xs:element name="BedroomsN umber" type="xs:unsign edInt"
minOccurs="0"/>
<xs:element name="Bathrooms Number" minOccurs="0">
<xs:simpleTyp e>
<xs:restricti on base="xs:string ">
<xs:pattern value="^\d*\.{0 ,1}\d$"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="Occupancy Indicator">
<xs:simpleTyp e>
<xs:restricti on base="xs:string ">
<xs:enumerati on value="1">
<xs:annotatio n>
<xs:documentati on>Owner</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
<xs:enumerati on value="2">
<xs:annotatio n>
<xs:documentati on>Tenant</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
<xs:enumerati on value="3">
<xs:annotatio n>
<xs:documentati on>Vacant</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="LivingAre aNumber" type="xs:unsign edInt"
minOccurs="0">
<xs:annotatio n>
<xs:documentati on>Square footage of the living
area.</xs:documentatio n>
</xs:annotation>
</xs:element>
<xs:element name="Contact">
<xs:complexType >
<xs:complexCont ent>
<xs:extension base="LiteConta ct__Type">
<xs:sequence>
<xs:element name="HomeNumbe r" type="Telephone Number__Type"
minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexConte nt>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="Product" type="REMMSPUpd ateProduct__Typ e"/>
</xs:sequence>
</xs:complexType>
<xs:complexTy pe name="REMMSPUpd ateProduct__Typ e">
<xs:sequence>
<xs:element name="Comment" minOccurs="0">
<xs:simpleTyp e>
<xs:restricti on base="xs:string ">
<xs:maxLength value="255"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="RushIndic ator" type="xs:boolea n"/>
<xs:element name="Type">
<xs:simpleTyp e>
<xs:restricti on base="xs:string ">
<xs:enumerati on value="11">
<xs:annotatio n>
<xs:documentati on>Exterior Market Valuation</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
<xs:enumerati on value="12">
<xs:annotatio n>
<xs:documentati on>Exterior Market Valuation with
Photos</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
<xs:enumerati on value="15">
<xs:annotatio n>
<xs:documentati on>Interior Market Valuation without
Photos</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
<xs:enumerati on value="16">
<xs:annotatio n>
<xs:documentati on>Interior Market Valuation with
Photos</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="Submittin gParty">
<xs:complexType >
<xs:sequence>
<xs:element name="Departmen t">
<xs:simpleTyp e>
<xs:restricti on base="xs:string ">
<xs:enumerati on value="99">
<xs:annotatio n>
<xs:documentati on>None</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
<xs:enumerati on value="10">
<xs:annotatio n>
<xs:documentati on>Bankruptcy</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
<xs:enumerati on value="20">
<xs:annotatio n>
<xs:documentati on>Foreclosure</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
<xs:enumerati on value="30">
<xs:annotatio n>
<xs:documentati on>Collections</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
<xs:enumerati on value="40">
<xs:annotatio n>
<xs:documentati on>Default Reporting</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
<xs:enumerati on value="50">
<xs:annotatio n>
<xs:documentati on>Loss Mitigation</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
<xs:enumerati on value="60">
<xs:annotatio n>
<xs:documentati on>FHA Per-Sale</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
<xs:enumerati on value="70">
<xs:annotatio n>
<xs:documentati on>REO</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="NDSRegist eredCredential" type="xs:string ">
<xs:annotatio n>
<xs:documentati on>preconfigure d MSP Credentials for MSP
Updates</xs:documentatio n>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:schema>
</types>
<message name="REMReques tSOAPIn">
<part name="REMReques tPart" element="ns:Pla ceBPOOrderREM"/>
</message>
<message name="REMReques tSOAPInMSPMARKU pdate">
<part name="REMReques tPart" element="ns:Pla ceBPOOrderREMMS PMARKUpdate"/>
</message>
<message name="REMReques tSOAPInMSPAPR1U pdate">
<part name="REMReques tPart" element="ns:Pla ceBPOOrderREMMS PAPR1Update"/>
</message>
<message name="REMRespon seSOAPOut">
<part name="REMRespon sePart" element="ns:Pla ceBPOOrderREMRe sponse"/>
</message>
<portType name="REMInterf ace">
<operation name="REMCorpor ationBPOOrder">
<input name="REMReques tIn" message="tns:RE MRequestSOAPIn"/>
<output name="REMRespon seOut" message="tns:RE MResponseSOAPOu t"/>
</operation>
<operation name="REMCorpor ationBPOOrderWi thMSPMarkUpdate ">
<input name="REMReques tIn" message="tns:RE MRequestSOAPInM SPMARKUpdate"/>
<output name="REMRespon seOut" message="tns:RE MResponseSOAPOu t"/>
</operation>
<operation name="REMCorpor ationBPOOrderWi thMSPAPR1Update ">
<input name="REMReques tIn" message="tns:RE MRequestSOAPInM SPAPR1Update"/>
<output name="REMRespon seOut" message="tns:RE MResponseSOAPOu t"/>
</operation>
</portType>
<binding name="REMSOAPHt tpsBinding" type="tns:REMIn terface">
<soap:binding style="document "
transport="http ://schemas.xmlsoap .org/soap/http"/>
<operation name="REMCorpor ationBPOOrder">
<soap:operati on soapAction="REM CorporationBPO/1.0/REMCorporationB POOrder"/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
<operation name="REMCorpor ationBPOOrderWi thMSPMarkUpdate ">
<soap:operati on
soapAction="REM CorporationBPO/1.0/REMCorporationB POOrderWithMSPM arkUpdate"/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
<operation name="REMCorpor ationBPOOrderWi thMSPAPR1Update ">
<soap:operati on
soapAction="REM CorporationBPO/1.0/REMCorporationB POOrderWithMSPA PR1Update"/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
</binding>
<service name="REMCorpor ationBPO">
<port name="iLabREMSO APPort" binding="tns:RE MSOAPHttpsBindi ng">
<soap:address location="http://test3.mortgagep hd.net/services"/>
</port>
<port name="BasicAuth REMSOAPPort" binding="tns:RE MSOAPHttpsBindi ng">
<soap:address location="http://test3.mortgagep hd.net:20443/services"/>
</port>
<port name="REMSOAPPo rt" binding="tns:RE MSOAPHttpsBindi ng">
<soap:address location="https ://www.mortgagephd .net/services"/>
</port>
</service>
</definitions>
"Gaurav Vaish (www.EduJini.IN )" wrote:
I have run into a problem generating the class file via the WSDL utility.
I
have a WSDL file that was generated by XMLSpy and is able to be read by
the
Java code utility, but I get the following error from the WSDL utility.

Error: Unable to import binding 'REMSOAPHttpsBi nding' from namespace


Can you post the complete WSDL?
Seems like some wsdl-soap-bindings missing.

--
Happy Hacking,
Gaurav Vaish
http://www.mastergaurav.org
http://webservices.edujini.in
-------------------

Jun 1 '06 #4
Hi Scott,

Can you host it on a website... may be geocities or elsewhere.

Basically, I would like to look thru the "tree structure" and see if
something's missing out...

--
Happy Hacking,
Gaurav Vaish
http://www.mastergaurav.org
http://www.edujini.in
http://webservices.edujini.in
-------------------
"ScottM" <Sc****@discuss ions.microsoft. com> wrote in message
news:5E******** *************** ***********@mic rosoft.com...
The site indicates that the post is to large and they have a limit of
30000
characters. The WSDL file is about 40K in size.

I will be posting the WSDL file is two parts.

Jun 1 '06 #5
I posted both parts into the two reply messages if you can cut and paste them
together.
I would have to create a website to share the file out. Please let me know
if you can cut and paste the two sections together.

Thanks
Scott

"Gaurav Vaish (www.EduJini.IN )" wrote:
Hi Scott,

Can you host it on a website... may be geocities or elsewhere.

Basically, I would like to look thru the "tree structure" and see if
something's missing out...

--
Happy Hacking,
Gaurav Vaish
http://www.mastergaurav.org
http://www.edujini.in
http://webservices.edujini.in
-------------------
"ScottM" <Sc****@discuss ions.microsoft. com> wrote in message
news:5E******** *************** ***********@mic rosoft.com...
The site indicates that the post is to large and they have a limit of
30000
characters. The WSDL file is about 40K in size.

I will be posting the WSDL file is two parts.


Jun 1 '06 #6
> I would have to create a website to share the file out. Please let me
know
if you can cut and paste the two sections together.


Facing some problems... somewhere it says the element is not closed. :(
--
Happy Hacking,
Gaurav Vaish | http://www.mastergaurav.org
http://www.edujini.in | http://webservices.edujini.in
-------------------

Jun 2 '06 #7
I was able to find a website that I could post the WSDL file to

The address is http://www.webprogrammers.com/remorig.wsdl

Thank you for your help!!
Scott

"Gaurav Vaish (www.EduJini.IN )" wrote:
I would have to create a website to share the file out. Please let me
know
if you can cut and paste the two sections together.


Facing some problems... somewhere it says the element is not closed. :(
--
Happy Hacking,
Gaurav Vaish | http://www.mastergaurav.org
http://www.edujini.in | http://webservices.edujini.in
-------------------

Jun 2 '06 #8
Hi Scott,
Error: Unable to import binding 'REMSOAPHttpsBi nding' from namespace
'http://www.fnfis.com/services/Services-Common/REM/20040109/v1.0'. - The


Won't say that have been able to track down the problem.

But one issue is that an operation - 'REMCorporation BPOOrder' has been
defined in portType section. There is also an entry corresponding to the
binding. However, the two have not been correlated in the service section.

Try adding similar lines in the 'service' section:

<port name='REMCorpor ationBPOOrder' binding='tns:RE MSOAPHttpsBindi ng'>
<soap:address location="http://whatever.is.the .location" />
</port>

Similarly, you will need to add entries for all the entries that have
not been given a binding. Besides the ports 'iLab..' etc mentioned are not
defined in the WSDL.

Rest looks ok... if error still persists, will need to dig deep if there
are any 'silly' mistakes...
--
Happy Hacking,
Gaurav Vaish | http://www.mastergaurav.org
http://www.edujini.in | http://webservices.edujini.in
-------------------
Jun 2 '06 #9
Thank you. So the error is in the WSDL file itself and not a bug in the WSDL
utility? The reason that I ask is the group that generated the WSDL file
indicates that it is OK in Java and XMLSpy indicates that it is a good WSDL
file, but I believe that these two utilities are simply ignoring the errors
in the WSDL file and the Microsoft's WSDL utility exposes the errors in the
WSDL file.

Let me know what you think about this debate.
"Gaurav Vaish (www.EduJini.IN )" wrote:
Hi Scott,
Error: Unable to import binding 'REMSOAPHttpsBi nding' from namespace
'http://www.fnfis.com/services/Services-Common/REM/20040109/v1.0'. - The


Won't say that have been able to track down the problem.

But one issue is that an operation - 'REMCorporation BPOOrder' has been
defined in portType section. There is also an entry corresponding to the
binding. However, the two have not been correlated in the service section.

Try adding similar lines in the 'service' section:

<port name='REMCorpor ationBPOOrder' binding='tns:RE MSOAPHttpsBindi ng'>
<soap:address location="http://whatever.is.the .location" />
</port>

Similarly, you will need to add entries for all the entries that have
not been given a binding. Besides the ports 'iLab..' etc mentioned are not
defined in the WSDL.

Rest looks ok... if error still persists, will need to dig deep if there
are any 'silly' mistakes...
--
Happy Hacking,
Gaurav Vaish | http://www.mastergaurav.org
http://www.edujini.in | http://webservices.edujini.in
-------------------

Jun 2 '06 #10

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

1
1257
by: holder25 | last post by:
Folks, I am trying to run the wsdl.exe tool to generate a server stub for the UDDI wsdl spec file at : http://www.oasis-open.org/committees/uddi-spec/doc/tcspecs.htm#uddiv2 When I run it I get the following error: C:\Program Files\Microsoft Platform SDK\Samples\UDDI\wsdldiscovery\xx>wsdl /serv er inquire_v2.wsdl Microsoft (R) Web...
5
7078
by: Wayne | last post by:
I have a way for doing plugin's in my gui app. These plugins have to talk to a webservice to do database calls. I've done the DB access as a web service so it can be shared with the rest of the company, if not for the want of reuse the gui app would have just simply accessed the DB Directly and each plugin in would have been fully self...
1
7551
by: Stefan Lischke | last post by:
hi there, I have a lot of problems generating code for the new "WS-Eventing" Specification http://schemas.xmlsoap.org/ws/2004/08/eventing/ Is it possible, that after IBM joined this spec. the code can only be generated by the WSDL toolkit from IBM?????
2
22484
by: Carmit | last post by:
Hi, I'm trying to build a proxy for this webservice: http://webservices.sabre.com/wsdl/sabreXML1.0.00/tpf/EndTransactionLLSRQ.wsdl I'm getting the following error: Error: Unable to import binding 'EndTransactionSoapBinding' from namespace 'http s://webservices.sabre.com/websvc'.
0
2031
by: Stefan Lischke | last post by:
Hi, I'm really desperate using code generation(wsdl.exe) from wsdl files for latest WS-Eventing(including WS-Addressing) Specs. I'm writing my diploma about "publish subscribe systems based on Web Services" I took the WS-Eventing WSDL file and added <binding>'s and <service>'s... Then i took the apache axis wsdl2java tool and i got nice
5
5062
by: Kevin Burton | last post by:
I am running wsdl.exe to try and generate some classes and I am getting: wsdl ppc.wsdl Microsoft (R) Web Services Description Language Utility Copyright (C) Microsoft Corporation 1998-2002. All rights reserved. Schema validation warning: Invalid 'name' attribute value: The ' ' character, hexadecimal value 0x20, cannot be included in a...
3
32113
by: John K | last post by:
I am trying to eliminate the capability of displaying the details of a web service by disabling WSDL generation in the web.config file. I have made the following changes to the web.config: <webServices> <wsdlHelpGenerator href="helpPage.aspx"/> <protocols> <remove name="Documentation" /> </protocols> </webServices>
1
3717
by: ahsan19 | last post by:
Our company is doing a project for the City of Chicago and we are trying to communicate with their servers using web services. Their environment is java based but we are using .NET on our end. The problem we are currently facing right now is that we are not able to generate a proxy class using the wsdl they have provided us. This is the WSDL...
3
2973
by: Thomas Guettler | last post by:
Hi, I looked for a solution to talk to a web service which offers its signature with a wsdl file. I googled for 'wsdl python' and found ZSI. This project uses code generation. That's something I don't like.
0
7507
marktang
by: marktang | last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However, people are often confused as to whether an ONU can Work As a Router. In this blog post, well explore What is ONU, What Is Router, ONU & Routers main...
0
7435
by: Hystou | last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can effortlessly switch the default language on Windows 10 without reinstalling. I'll walk you through it. First, let's disable language...
0
7698
Oralloy
by: Oralloy | last post by:
Hello folks, I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>". The problem is that using the GNU compilers, it seems that the internal comparison operator "<=>" tries to promote arguments from unsigned to signed. This is as boiled down as I can make it. ...
0
7947
jinu1996
by: jinu1996 | last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven tapestry of website design and digital marketing. It's not merely about having a website; it's about crafting an immersive digital experience that...
0
7794
tracyyun
by: tracyyun | last post by:
Dear forum friends, With the development of smart home technology, a variety of wireless communication protocols have appeared on the market, such as Zigbee, Z-Wave, Wi-Fi, Bluetooth, etc. Each protocol has its own unique characteristics and advantages, but as a user who is planning to build a smart home system, I am a bit confused by the...
1
5361
isladogs
by: isladogs | last post by:
The next Access Europe User Group meeting will be on Wednesday 1 May 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM). In this session, we are pleased to welcome a new presenter, Adolph Dupr who will be discussing some powerful techniques for using class modules. He will explain when you may want to use classes...
0
3492
by: TSSRALBI | last post by:
Hello I'm a network technician in training and I need your help. I am currently learning how to create and manage the different types of VPNs and I have a question about LAN-to-LAN VPNs. The last exercise I practiced was to create a LAN-to-LAN VPN between two Pfsense firewalls, by using IPSEC protocols. I succeeded, with both firewalls in...
0
3472
by: adsilva | last post by:
A Windows Forms form does not have the event Unload, like VB6. What one acts like?
1
1046
muto222
by: muto222 | last post by:
How can i add a mobile payment intergratation into php mysql website.

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.