I know the title looks scary however it wont be as scary once I explain the situation and the fact that message would not be really untyped :) So lets say that you are dealing with an intricate and a huge schema and you also expose the orchestration as a web service. Now assuming that you used the BizTalk Web Service Publishing wizard, it will do all the plumbing for you to set up the web service, create ports and hook up logical ports to the physical web service ports. So far so good, however now...

Recently I encountered a rather fresh error while publishing an orchestration as a web service. 'The datatype '' is missing' was the gist of the complaint during the publishing process (This error could be different in different situations but mostly it should complain about some sort of datatype). Looking behind the scenes, my best guess was that serialization had to be the culprit directly or indirectly since thats the only non-trivial subprocess taking place during the whole publishing process...

There could be times when you want to enter an orchestration through both a file drop as well as a web service call. The first obstacle you could encounter is that you can only have a single receive shape with 'Activate=True' and since we are not talking about convoys, multiple receive shapes in a sequence is certianly now the way to go. Thank you Heavens that MS provided the 'Listen' shape which allows you many activate-able receive locations. My wonderament start after the Listen shape where I...