| Author | 
		  Message
		 | 
		
		  | Frik | 
		  
		    
			  
				 Posted: Mon Aug 12, 2013 6:15 am    Post subject: Bip 0116E - can't create message set from WSDL | 
				     | 
			   
			 
		   | 
		
		
		   Acolyte
 
 Joined: 25 Nov 2009 Posts: 69
  
  | 
		  
		    
			  
				Hello people, 
 
I have a problem improting wsdl to message set, Can't find out what the problem is...
 
 
I'm getting Bip0116E - Error Creating Message Definition File for this wsdl:
 
   
	| Quote: | 
   
  
	
 
<wsdl:definitions targetNamespace="http://tempuri.org/">
 
  <wsdl:types>
 
    <s:schema elementFormDefault="qualified" targetNamespace="http://tempuri.org/">
 
      <s:import schemaLocation="OpenAccount.xsd"/>
 
      <s:element name="get_openAccountLead">
 
        <s:complexType>
 
          <s:sequence>
 
            <s:element minOccurs="0" maxOccurs="1" name="requestID" type="s:string"/>
 
          </s:sequence>
 
        </s:complexType>
 
      </s:element>
 
      <s:element name="get_openAccountLeadResponse">
 
        <s:complexType>
 
          <s:sequence>
 
            <s:element minOccurs="0" maxOccurs="1" name="get_openAccountLeadResult">
 
              <s:complexType>
 
                <s:sequence>
 
                  <s:element ref="AccountForSingle"/>
 
                </s:sequence>
 
              </s:complexType>
 
            </s:element>
 
          </s:sequence>
 
        </s:complexType>
 
      </s:element>
 
    </s:schema>
 
  </wsdl:types>
 
  <wsdl:message name="get_openAccountLeadSoapIn">
 
    <wsdl:part name="parameters" element="tns:get_openAccountLead"/>
 
  </wsdl:message>
 
  <wsdl:message name="get_openAccountLeadSoapOut">
 
    <wsdl:part name="parameters" element="tns:get_openAccountLeadResponse"/>
 
  </wsdl:message>
 
  <wsdl:portType name="ServiceSoap">
 
    <wsdl:operation name="get_openAccountLead">
 
      <wsdl:input message="tns:get_openAccountLeadSoapIn"/>
 
      <wsdl:output message="tns:get_openAccountLeadSoapOut"/>
 
    </wsdl:operation>
 
  </wsdl:portType>
 
  <wsdl:binding name="ServiceSoap" type="tns:ServiceSoap">
 
    <soap:binding transport="http://schemas.xmlsoap.org/soap/http"/>
 
    <wsdl:operation name="get_openAccountLead">
 
      <soap:operation soapAction="http://tempuri.org/get_openAccountLead" 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="ServiceSoap12" type="tns:ServiceSoap">
 
    <soap12:binding transport="http://schemas.xmlsoap.org/soap/http"/>
 
    <wsdl:operation name="get_openAccountLead">
 
      <soap12:operation soapAction="http://tempuri.org/get_openAccountLead" 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="Service">
 
    <wsdl:port name="ServiceSoap" binding="tns:ServiceSoap">
 
      <soap:address location="http://127.0.0.1/dev/Service.asmx"/>
 
    </wsdl:port>
 
    <wsdl:port name="ServiceSoap12" binding="tns:ServiceSoap12">
 
      <soap12:address location="http://127.0.0.1/dev/Service.asmx"/>
 
    </wsdl:port>
 
  </wsdl:service>
 
</wsdl:definitions> | 
   
 
 
 
Does anone can see a problem here?
 
It's really weird... | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | dogorsy | 
		  
		    
			  
				 Posted: Mon Aug 12, 2013 6:23 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Knight
 
 Joined: 13 Mar 2013 Posts: 553 Location: Home Office 
  | 
		  
		    
			  
				
   
	| Code: | 
   
  
	| <s:import schemaLocation="OpenAccount.xsd"/>  | 
   
 
 
 
do you have the XSD in the directory ? | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | lancelotlinc | 
		  
		    
			  
				 Posted: Mon Aug 12, 2013 6:25 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Jedi Knight
 
 Joined: 22 Mar 2010 Posts: 4941 Location: Bloomington, IL USA 
  | 
		  
		    
			  
				Quote the full error. What toolkit version are you on? There are significant APARs related to importing WSDLs into the toolkit. You need to be on 8.0.0.2 iFix 001. _________________ http://leanpub.com/IIB_Tips_and_Tricks
 
Save $20: Coupon Code: MQSERIES_READER | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | stevarg | 
		  
		    
			  
				 Posted: Mon Aug 12, 2013 6:57 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Novice
 
 Joined: 20 Nov 2012 Posts: 24
  
  | 
		  
		    
			  
				Is this a valid wsdl that you are using... 
 
the wsdl has a lot of namespace declarations missing.... | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | Frik | 
		  
		    
			  
				 Posted: Mon Aug 12, 2013 10:14 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Acolyte
 
 Joined: 25 Nov 2009 Posts: 69
  
  | 
		  
		    
			  
				Hey, Thanks.
 
 
   
	| dogorsy wrote: | 
   
  
	
   
	| Code: | 
   
  
	| <s:import schemaLocation="OpenAccount.xsd"/>  | 
   
 
 
 
do you have the XSD in the directory ? | 
   
 
 
yes, of course.
 
 
about the namespaces - for some reason, the wsdl definitions part was cutted,
 
 
This is the full wsdl:
 
   
	| Quote: | 
   
  
	<?xml version="1.0" encoding="utf-16"?>
 
<wsdl:definitions targetNamespace="http://tempuri.org/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://tempuri.org/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
 
    <wsdl:types>
 
        <s:schema elementFormDefault="qualified" targetNamespace="http://tempuri.org/">
 
            </s:import schemaLocation="OpenAccount.xsd">
 
            <s:element name="get_openAccountLead">
 
                <s:complexType>
 
                    <s:sequence>
 
                        <s:element minOccurs="0" maxOccurs="1" name="requestID" type="s:string" />
 
                    </s:sequence>
 
                </s:complexType>
 
            </s:element>
 
            <s:element name="get_openAccountLeadResponse">
 
                <s:complexType>
 
                    <s:sequence>
 
                        <s:element minOccurs="0" maxOccurs="1" name="get_openAccountLeadResult">
 
                            <s:complexType>
 
                                <s:sequence>
 
                                    </s:element ref="AccountForSingle">
 
                                </s:sequence>
 
                            </s:complexType>
 
                        </s:element>
 
                    </s:sequence>
 
                </s:complexType>
 
            </s:element>
 
        </s:schema>
 
    </wsdl:types>
 
    <wsdl:message name="get_openAccountLeadSoapIn">
 
        <wsdl:part name="parameters" element="tns:get_openAccountLead" />
 
    </wsdl:message>
 
    <wsdl:message name="get_openAccountLeadSoapOut">
 
        <wsdl:part name="parameters" element="tns:get_openAccountLeadResponse" />
 
    </wsdl:message>
 
    <wsdl:portType name="ServiceSoap">
 
        <wsdl:operation name="get_openAccountLead">
 
            <wsdl:input message="tns:get_openAccountLeadSoapIn" />
 
            <wsdl:output message="tns:get_openAccountLeadSoapOut" />
 
        </wsdl:operation>
 
    </wsdl:portType>
 
    <wsdl:binding name="ServiceSoap" type="tns:ServiceSoap">
 
        <soap:binding transport="http://schemas.xmlsoap.org/soap/http" />
 
        <wsdl:operation name="get_openAccountLead">
 
            <soap:operation soapAction="http://tempuri.org/get_openAccountLead" 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="ServiceSoap12" type="tns:ServiceSoap">
 
        <soap12:binding transport="http://schemas.xmlsoap.org/soap/http" />
 
        <wsdl:operation name="get_openAccountLead">
 
            <soap12:operation soapAction="http://tempuri.org/get_openAccountLead" 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="Service">
 
        <wsdl:port name="ServiceSoap" binding="tns:ServiceSoap">
 
            <soap:address location="http://127.0.0.1/dev/Service.asmx" />
 
        </wsdl:port>
 
        <wsdl:port name="ServiceSoap12" binding="tns:ServiceSoap12">
 
            <soap12:address location="http://127.0.0.1/dev/Service.asmx" />
 
        </wsdl:port>
 
    </wsdl:service>
 
</wsdl:definitions> 
 
 | 
   
 
 
 
I'm working on toolkit version 7.0.0.3
 
 
The full error is:
 
 
"BIP0116E Error Creating Message Definition File
 
"An error occured while writing creating:
 
\aMset\AMset\tempuri\openaccount.mxsd.
 
unable to write to the local file system:
 
\aMset\AMset\tempuri\openaccount.mxsd
 
 
Refresh the workspace" | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | dogorsy | 
		  
		    
			  
				 Posted: Mon Aug 12, 2013 10:19 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Knight
 
 Joined: 13 Mar 2013 Posts: 553 Location: Home Office 
  | 
		  
		    
			  
				Do you have write privileges to the directory shown in the message ?
 
what does the message suggest ?
   
	| Code: | 
   
  
	unable to write to the local file system: 
 
 \aMset\AMset\tempuri\openaccount.mxsd 
 
 | 
   
 
 
 
It does not say anything about the wsdl | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | Frik | 
		  
		    
			  
				 Posted: Mon Aug 12, 2013 10:41 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Acolyte
 
 Joined: 25 Nov 2009 Posts: 69
  
  | 
		  
		    
			  
				
   
	| dogorsy wrote: | 
   
  
	Do you have write privileges to the directory shown in the message ?
 
what does the message suggest ?
   
	| Code: | 
   
  
	unable to write to the local file system: 
 
 \aMset\AMset\tempuri\openaccount.mxsd 
 
 | 
   
 
 
 
It does not say anything about the wsdl | 
   
 
 
 
Yes, id fo have write privileges. Checked it several times.
 
 
The mxsd it failed to create is generated from the wsdl above. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | dogorsy | 
		  
		    
			  
				 Posted: Mon Aug 12, 2013 11:33 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Knight
 
 Joined: 13 Mar 2013 Posts: 553 Location: Home Office 
  | 
		  
		    
			  
				
   
	| Frik wrote: | 
   
  
	
   
	| dogorsy wrote: | 
   
  
	Do you have write privileges to the directory shown in the message ?
 
what does the message suggest ?
   
	| Code: | 
   
  
	unable to write to the local file system: 
 
 \aMset\AMset\tempuri\openaccount.mxsd 
 
 | 
   
 
 
 
It does not say anything about the wsdl | 
   
 
 
 
Yes, id fo have write privileges. Checked it several times.
 
 
The mxsd it failed to create is generated from the wsdl above. | 
   
 
 
 
Try a completely different wsdl. Preferably one that you know can be generated. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | Frik | 
		  
		    
			  
				 Posted: Mon Aug 12, 2013 11:55 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Acolyte
 
 Joined: 25 Nov 2009 Posts: 69
  
  | 
		  
		    
			  
				
   
	| dogorsy wrote: | 
   
  
	
   
	| Frik wrote: | 
   
  
	
   
	| dogorsy wrote: | 
   
  
	Do you have write privileges to the directory shown in the message ?
 
what does the message suggest ?
   
	| Code: | 
   
  
	unable to write to the local file system: 
 
 \aMset\AMset\tempuri\openaccount.mxsd 
 
 | 
   
 
 
 
It does not say anything about the wsdl | 
   
 
 
 
Yes, id fo have write privileges. Checked it several times.
 
 
The mxsd it failed to create is generated from the wsdl above. | 
   
 
 
 
Try a completely different wsdl. Preferably one that you know can be generated. | 
   
 
 
 
another wsdls are generated successfully. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | Simbu | 
		  
		    
			  
				 Posted: Tue Aug 13, 2013 12:10 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Master
 
 Joined: 17 Jun 2011 Posts: 289 Location: Tamil Nadu, India 
  | 
		  
		    
			  
				
   
	| Frik wrote: | 
   
  
	
   
	| dogorsy wrote: | 
   
  
	
   
	| Frik wrote: | 
   
  
	
   
	| dogorsy wrote: | 
   
  
	Do you have write privileges to the directory shown in the message ?
 
what does the message suggest ?
   
	| Code: | 
   
  
	unable to write to the local file system: 
 
 \aMset\AMset\tempuri\openaccount.mxsd 
 
 | 
   
 
 
 
It does not say anything about the wsdl | 
   
 
 
 
Yes, id fo have write privileges. Checked it several times.
 
 
The mxsd it failed to create is generated from the wsdl above. | 
   
 
 
 
Try a completely different wsdl. Preferably one that you know can be generated. | 
   
 
 
 
 
another wsdls are generated successfully. | 
   
 
 
 
Please clean and build the worksapce and try. if still the problem persist then try to create new worksapce, copy the wsdl/xsd and try. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | Frik | 
		  
		    
			  
				 Posted: Tue Aug 13, 2013 12:20 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Acolyte
 
 Joined: 25 Nov 2009 Posts: 69
  
  | 
		  
		    
			  
				
   
	| Simbu wrote: | 
   
  
	
 
Please clean and build the worksapce and try. if still the problem persist then try to create new worksapce, copy the wsdl/xsd and try. | 
   
 
 
Already done.
 
failed in each. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | stevarg | 
		  
		    
			  
				 Posted: Tue Aug 13, 2013 1:25 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Novice
 
 Joined: 20 Nov 2012 Posts: 24
  
  | 
		  
		    
			  
				| Have you tried validating the wsdl in the broker toolkit... ??? | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | Frik | 
		  
		    
			  
				 Posted: Tue Aug 13, 2013 1:33 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Acolyte
 
 Joined: 25 Nov 2009 Posts: 69
  
  | 
		  
		    
			  
				
   
	| stevarg wrote: | 
   
  
	| Have you tried validating the wsdl in the broker toolkit... ??? | 
   
 
 
Of course, it's valid. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | stevarg | 
		  
		    
			  
				 Posted: Tue Aug 13, 2013 1:39 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Novice
 
 Joined: 20 Nov 2012 Posts: 24
  
  | 
		  
		    
			  
				well this statement in ur wsdl doesnt seem to be valid 
 
</s:import schemaLocation="OpenAccount.xsd"> | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | Frik | 
		  
		    
			  
				 Posted: Tue Aug 13, 2013 1:45 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Acolyte
 
 Joined: 25 Nov 2009 Posts: 69
  
  | 
		  
		    
			  
				
   
	| stevarg wrote: | 
   
  
	well this statement in ur wsdl doesnt seem to be valid 
 
</s:import schemaLocation="OpenAccount.xsd"> | 
   
 
 
 
Well, the broker assured that this wsdl is valid.Actually, this specific line somehow was reserved in the way to the forum, but in the broker it's :
 
   
	| Quote: | 
   
  
	| <s:import schemaLocation="OpenAccount.xsd"/> | 
   
 
 | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | 
		    
		   |