Publishing multiple orhestrations as a single web service
Hi,
I have a project with two orchestratioins one for "geting Inventory data" and another for " getting POS data".
The problem is when I published orchestration as a web service by selecting both Inventory and POS receive posts, the "Inventory orhestration" is working fine when I called from C# console application. But the same is not happening for "POS orchestration".
But when I select only "POS orchestration receive port" as web service, it is working fine from c# console application.
Is there any problem in multiple ports from different orchestrations when publishing as a web service?
Thank in advance.
Bikram
Hi,
You could double-check that you have set the operation names in the port types correctly. That may cause issues when publishing more than one orchestration.
Another thing you could try is publishing schemas as web services. I think that publishing schemas is a lot more "contract first" that publishing orchestrations, and you get much better control over the web service you are creating. It also allows you to work with the messaging engine and expose web services just using pub-sub and routing.
You will find binding the schema published web services to the orchestration is a bit tricky, as you need to ensure the port type has an operation name matching the method name of the web service method (you will see this in the subscriptions that the orchestration generates, shout if you need help here...).
Regards,
Alan
