Posted: Mon Jan 25, 2010 7:44 pm Post subject: Exposing msgflow as webservice
Acolyte
Joined: 10 Mar 2009 Posts: 57
Hi,
I am generating awsdl from the message set. My doubt is whether to use SOAPInput node or HttpInput node. What differece does it make?
Which has the better performance.
After the SAOP/HttpInput node am using Extract node to extract the body and then HttpReply node is used to send the reply.
So which combination of nodes would be better in such situation?
You CAN NOT use an HTTPReply with a SOAPInput. You *must* use a SOAPReply.
Likewise you CAN NOT use a SOAPReply with an HTTPInput, you *MUST* use an HTTPReply.
Performance is entirely dependant on too many other things for the choice of node to impact it, until you've done all of the necessary testing you need to do to show that you need to adjust performance by changing the node you use.
Use the SOAP nodes. They're easier. You'll get more done quicker.
Posted: Wed Jan 27, 2010 2:26 am Post subject: Exposing msgflow as webservice
Acolyte
Joined: 10 Mar 2009 Posts: 57
Ya I am using the HttpInputnode in combination with the HttpReply node itself.. My client doesn need any security feature n all..So I don need any new feature of the SOAP nodes, so is it better to use HTTP nodes?
In properties of HttpInput node there is a property called input message parsing, where in we are able to set the message domain where as in SOAPInput node it is not possible to change the property and it is always fixed to SOAP domain which I don want. Then it wont be useful using SOAP nodes right?
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