Posted: Tue Jan 13, 2009 1:32 am Post subject: Can we have two operations in a WSDL as two message flows?
Centurion
Joined: 14 Feb 2008 Posts: 100
Hi,
I wanted to know that can we have two operations described uder one WSDL as two separate message flows with the same URLSelector in same execution group?
I made two flows by exposing two operations from a single WSDL separetly.I intentionally kept the URLSelector for both same as descibed in WSDL. Then I tried to invoke flow having Operation A exposed using a third flow. But SOAP Request was always going to the flow with Operation B.
Does SOAP Input node does not differentiate based on the operation?
It seems that no one is getting the point from the text I had wriiten earlier.
I have two Questions
1. Will the SOAP Input node not allow the message for a operation which is present in the WSDL used by it but not exposed?
2. Can I use two message flows for exposing the two operations of a single WSDL separetly with the same URL Selector in the same execution group?
While I tried to do so the Broker got confused and was invoking the flows randomly without making any differentiation for the Operation.
You can easily create your own flow that does this routing for you. But you should consider what the definition of a "service" is, and whether you really need to handle different operations on the same service by different code, or whether you really need different services.
But my flow is slightly on the heavier side. So I wanted to separate the operations so that load on the flow is less.Also I have to maintain sequencing for that particular operation so I can not deploy multiple instances of the same flow.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum