E2E Forum › Modeling & Development › WSDL generated by Bridge can’t be read from consumer
This topic contains 1 reply, has 2 voices, and was last updated by Marcel R. 4 years, 5 months ago.
We received a mail from a consumer of a WSDL of a Bridge Service, saying that he gets an error:
R2001 A DESCRIPTION MUST only use the WSDL “import” statement to import another WSDL description.
According to him, the Bridge WSDL is not correct because we import XSD Files.
Is there a way to create a WSDL that avoids this import?
Actually, importing a XSD file directly into the WSDL is quite common. They even do this in their standard examples, see section 2.1.2 Authoring Style on http://www.w3.org/TR/wsdl (search for <import namespace=”http://example.com/stockquote/schemas“)
However, the WS-Interoperability (WS-I) Profile recommends not to do this. Don’t know why. The rule R2001 is from the WS-I profile.
Workaround: set wsdlPerService = false
You must be logged in to reply to this topic.