SOAP vs SERVICE Palette

The strength of the service palette is its weakness.... It gives protocol independence to implementation... Lets take this scenario, you have a interface which you want to expose using SOAP/HTTP, SOAP/JMS, SOAP/HTTPS... then you can use service palette to implement this scenario... You can reuse the implementation... as ur implementation is independent of Protocol details, which is not possible if you are using SOAP Palette... As Yadhav pointed you have certain drawbacks with service palette... SOAP Reequest Reply is the strength of the soap Palette... Lets take this scenario... you have multiple servers providing a service using same interface definition, then you can construct the URL dynamically if you are using SOAP Request Reply... but the same is not possible with InvokePartner... So it is left with the developer to choose between trade offs... whether to deal with service palette or to use SOAP Palette

Service Palette offers architectural advantage over SOAP Event Source when you want to develop web services. Service Palette offers multiple operations defined at a higer level while the configuration is scattered when you use SOAP event source to implement multiple operations in the service. One of the differences between Service palette and soap event source is is when it comes to sequencing. When you use SOAP Even source you have sequencing key in the Misc tab and this field can contain an XPath expression that specifies which processes should run in order. Process instances with sequencing keys that evaluate to the same value will be executed sequentially in the order the process instance was created. Is there anyway you any way of controlling the execution order of process instances using Service Pallete ? Can anybody share real examples when they've used sequencing? (Regardless of webservices anywhere in BW )