| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Problem while generating message definition from WSDL |
« View previous topic :: View next topic » |
| Author |
Message
|
| mqwbi |
 Posted: Wed Apr 14, 2010 9:38 am Post subject: Problem while generating message definition from WSDL |
 |
|
Novice
Joined: 15 Dec 2008
Posts: 24
|
Hi
I have got a WSDL from a project colleague which was generated in Websphere Integration Developer 6.1.2 . I am trying to generate a message definition (for a message set) using the WSDL. But the wizard is not progressing complianing that
| Quote: |
Error loading WSDL file. Check the wsdl for Validity
|
I try to explicitly validate the WSDL but it complains saying
| Quote: |
WS-I: A problem occured while running the WS-I WSDL conformance check: org.eclipse.wst.wsi.internal.analyzer.WSIAnalyzerException: The WS-I Test Assertion Document (TAD)document was either not found or could not be processed.The WSDLAnalyzer was unable to validate the given WSDL File. MSP_Request_Response ARBIRAccountServices.wsdl
|
Request you to give me some pointers if u can please. Pasting the text of the WSDL file below
Thank You
mqwbi
===================WSDL File Contents===============
| Quote: |
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:tns="http://api.interfaces.sessions.ar.amdocs" xmlns:xsd="http://www.w3.org/2001/XMLSchema" name="ARBIRAccountServices_2" targetNamespace="http://api.interfaces.sessions.ar.amdocs">
<wsdl:types>
<xsd:schema xmlns:bons0="http://com/ibm/vel/eai/disha/ar/custom" xmlns:bons1="http://com/ibm/vel/eai/disha/bo/custom" targetNamespace="http://api.interfaces.sessions.ar.amdocs">
<xsd:import namespace="http://com/ibm/vel/eai/disha/bo/custom"/>
<xsd:import namespace="http://com/ibm/vel/eai/disha/ar/custom"/>
<xsd:element name="getAccountBalance">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="getAccountBalanceReq" nillable="true" type="bons0:GetAccountBalanceRequest"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="getAccountBalanceResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="getAccountBalanceRes" nillable="true" type="bons0:GetAccountBalanceResponse"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="EAIFault_element" nillable="true" type="bons1:EAIFault"/>
</xsd:schema>
<schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:tns2="http://datatypes.datalayer.ar.amdocs" attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://datatypes.datalayer.ar.amdocs" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<element name="AccountBalanceDt" nillable="true" type="tns2:AccountBalanceDt"/>
<complexType name="AccountBalanceDt">
<complexContent>
<extension base="tns2:Datatype">
<sequence>
<element name="arBalance" type="xsd:double"/>
<element name="unappliedAmount" type="xsd:double"/>
</sequence>
</extension>
</complexContent>
</complexType>
<complexType abstract="true" name="Datatype">
<sequence/>
</complexType>
<element name="AccountIdInfoDt" nillable="true" type="tns2:AccountIdInfoDt"/>
<complexType name="AccountIdInfoDt">
<complexContent>
<extension base="tns2:Datatype">
<sequence>
<element name="accountId" type="xsd:long"/>
<element name="cmAccountNumber" nillable="true" type="xsd:string"/>
</sequence>
</extension>
</complexContent>
</complexType>
</schema>
<xsd:schema xmlns:bons0="http://datatypes.datalayer.ar.amdocs" xmlns:bons1="http://datatypes.datalayer.ar.amdocs" xmlns:bons2="http://com/ibm/vel/eai/disha/bo/custom" attributeFormDefault="unqualified" elementFormDefault="unqualified" targetNamespace="http://com/ibm/vel/eai/disha/ar/custom" xmlns="" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:import namespace="http://datatypes.datalayer.ar.amdocs"/>
<xsd:import namespace="http://com/ibm/vel/eai/disha/bo/custom"/>
<xsd:complexType name="GetAccountBalanceRequest">
<xsd:sequence>
<xsd:element minOccurs="0" name="metaData" type="bons2:MetaData">
</xsd:element>
<xsd:element minOccurs="0" name="accountIdInfoDt" type="bons0:AccountIdInfoDt">
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="GetAccountBalanceResponse">
<xsd:sequence>
<xsd:element minOccurs="0" name="metaData" type="bons2:MetaData">
</xsd:element>
<xsd:element minOccurs="0" ref="bons1:AccountBalanceDt"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
<xsd:schema xmlns:bons1="http://com/ibm/vel/eai/disha/bo/custom" attributeFormDefault="unqualified" elementFormDefault="unqualified" targetNamespace="http://com/ibm/vel/eai/disha/bo/custom" xmlns="" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:complexType name="EAIFault">
<xsd:sequence>
<xsd:element minOccurs="0" name="metaData" type="bons1:MetaData">
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="MetaData">
<xsd:sequence>
<xsd:element minOccurs="0" name="field1" type="xsd:string">
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
</wsdl:types>
<wsdl:message name="getAccountBalanceRequestMsg">
<wsdl:part element="tns:getAccountBalance" name="getAccountBalanceParameters"/>
</wsdl:message>
<wsdl:message name="getAccountBalanceResponseMsg">
<wsdl:part element="tns:getAccountBalanceResponse" name="getAccountBalanceResult"/>
</wsdl:message>
<wsdl:message name="getAccountBalance_fault1Msg">
<wsdl:part element="tns:EAIFault_element" name="fault1"/>
</wsdl:message>
<wsdl:portType name="ARBIRAccountServices">
<wsdl:operation name="getAccountBalance">
<wsdl:input message="tns:getAccountBalanceRequestMsg" name="getAccountBalanceRequest"/>
<wsdl:output message="tns:getAccountBalanceResponseMsg" name="getAccountBalanceResponse"/>
<wsdl:fault message="tns:getAccountBalance_fault1Msg" name="fault1"/>
</wsdl:operation>
</wsdl:portType>
</wsdl:definitions>
|
[/quote] |
|
| Back to top |
|
 |
| mgk |
| Posted: Wed Apr 14, 2010 10:03 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
Hi, this is not a complete WSDL, as it does not have a bindings or a service section, you need to add them in as WMB requires complete WSDL files...
Kind Regards,
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
| skidewd |
| Posted: Thu Apr 15, 2010 7:44 pm Post subject: |
|
|
Novice
Joined: 20 Mar 2010
Posts: 12
|
If your project colleague has exports/imports defined in their WebSphere Integration Developer Module (these sometimes also called bindings), then they must have version of WSDL that has binding definitions. You may want to find out what type of binding they use to invoke Module that is defined in WID.
By the way, if you are trying to integrate WMB with WPS/WESB - WID is typically used to develop services that run under one of those server environments - you may want to look at SCA nodes. They are available since WMB 7.0 and provide really simple integration between WMB and WPS/WESB.
Hope this helps. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
