- This topic has 1 reply, 1 voice, and was last updated 9 years, 2 months ago by
.
-
Posts
-
-
1. ) I have an Orchestration (reporting ) published as a webservice . The schema is say http://myreporting and root node in Data
2.) Now I have another Orchestration(consumer ) which consumes this reporting webservice . So I add the schema from the other webservice, this creates the reference.xsd and I build and deploy the schema in the same machine.
Now when the consumer orchestration tries to send a message to webservice , We get this SOAP exception
The \”SOAP\” adapter is suspending an outbound message going to destination URL:\”http://localhost/myreportingapp.asmx\”. Details:\”Unable to load type
I tried putting a custom recieve pipeline to do a forceful promotion . that did not help either. Apparently I can see that now there are two schemas with same namespace and root node , One from the original solution and other from the reference.xsd whihc is causing this inability to identify the schema .
Any idea how to overcome this problem other than deploying both apps in different machines ?
-
Catch-22
You can’t publish the web service without a schema and when you reference the web service a copy of the schema is created.
One thing you might like to try is not adding the web reference to your consumer application. But add a reference to the reporting assembly. And use the original schema to create the orchestration message and a SOAP send port to send it.
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.