| Author |
Message
|
| ghoshly |
 Posted: Thu Mar 14, 2013 5:55 am Post subject: WSDL error |
 |
|
Partisan
Joined: 10 Jan 2008
Posts: 333
|
Hi ,
I am facing a error while building a wsdl file from xsds which we need to expose as a web service.
Error below.
| Code: |
| WSDL: A SOAP address cannot be specified here as the ESB_Invoice_SOAP12Binding binding that the ESB_InvoiceSOAP12Port port refers to does not have a SOAP binding element defined. There must be a SOAP binding element defined in order to specify a SOAP address for a binding. ESB_Invoice.wsdl MFP_ESB_POC line 73 WSDL Problem |
However I can see the binding definition present just above.
| Code: |
<wsdl:binding name="ESB_Invoice_SOAP12Binding" type="tns:ESB_Invoice_PortType">
<soap12:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
<wsdl:operation name="PostInvoice">
<soap12:operation soapAction="http://www.sodexo.com/ESB/Invoice/PostInvoice" />
<wsdl:input>
<soap12:body use="literal" />
</wsdl:input>
<wsdl:output>
<soap12:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="ESB_Invoice_Interface">
<wsdl:port binding="tns:ESB_Invoice_SOAP11Binding" name="ESB_Invoice_SOAP11Port">
<soap:address location="http://10.195.17.134:9080/esb/services/PostInvoiceInterface" />
</wsdl:port>
<wsdl:port binding="tns:ESB_Invoice_SOAP12Binding" name="ESB_InvoiceSOAP12Port">
<soap12:address location="http://10.195.17.134:9080/esb/services/PostInvoiceInterface"/>
</wsdl:port>
</wsdl:service>
|
It would have been helpful if I could update those files.
Thanks in advance for help |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Thu Mar 14, 2013 6:03 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| ghoshly |
| Posted: Thu Mar 14, 2013 6:14 am Post subject: SOAP 1.1 or SOAP 1.2 |
|
|
Partisan
Joined: 10 Jan 2008
Posts: 333
|
Actually these services are consumed by multiple reciepient / consumers and diff application uses different.
I accept, I do not have much knowledge on the differences between these two versions.
I'll try first removing SOAP 1.2 binding completely |
|
| Back to top |
|
|
| ghoshly |
| Posted: Thu Mar 14, 2013 6:59 am Post subject: Refreshing error? |
|
|
Partisan
Joined: 10 Jan 2008
Posts: 333
|
I have just recreated the wsdl with both the binding and this time, I am not seeing the error in wsdl file.
May be because of refreshing issue?
Though I had performed Cleann as well as Close / Open project.
After I have created mxsd from the wsdl definition using both the versions, I see the error below.
| Code: |
Description Resource Path Location Type
Recursive element definition 'Subcode' is not permitted in TDS physical format 'Text1' and this element is used by the message(s): 'Envelope, Fault'. Remove the recursion, or the layer. soapenv12.mxsd MSP_TMC_ESB_Invoice_IN/TMC_ESB_Invoice_IN/org/w3/www/_2003/_05/soapenvelope line 128 Message Set Problem
|
Should we use either SOAP 1.1 or SOAP1.2 in a message set?
Is there any advantage / disadvantage between SOAP versions? |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Thu Mar 14, 2013 7:53 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
If you are sure that the XSD/WSDL is a good one, you could try deleting the old message set and creating a new one. What WMB version are you on? If you are on V8, you probably should not use message set at all.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| ghoshly |
| Posted: Fri Mar 15, 2013 12:03 am Post subject: I understand |
|
|
Partisan
Joined: 10 Jan 2008
Posts: 333
|
I understand, in MB 8 we should use DFDL, but I am in MB 7.
I am creating mxsd from wsdl and it is validating without any error. I could see in a different message set that both SOAP 1.1 and SOAP1.2 envelope co-exist.
I'll try to recreate the mxsds or debug this one.
Thanks for responding... |
|
| Back to top |
|
|
|
|
