Search code examples
wcfxsdwsdlbpel

Naming XSDs in wsdl generated by WCF

We are working on a WCF service which is being consumed by BPEL. When BPEL imports the WSDL, it reads the XSDs as below:

_

http://Server_Name/Service1.svc?xsd=xsd0

_http://Server_Name/Service1.svc?xsd=xsd1

_http://Server_Name/Service1.svc?xsd=xsd2

so on and so forth.

This random naming of XSDs is creating a lot of churn, as whenever there is a contract change, BPEL again reloads the entire WSDL and a random number suffix will be added to each XSD. BPEL team will have to then again open each XSD to find out the change.

Is there a way by which WCF can stop generating these random XSDs and give each XSD a proper name?

Solution

  • To overcome this problem, We installed .NET 4.5 to generate single wsdl which properly names the XSDs and has no XSD import statements.