Charles Young

  Home  |   Contact  |   Syndication    |   Login
  104 Posts | 41 Stories | 312 Comments | 406 Trackbacks

News

MVP - Microsoft Most Valuable Professional

Article Categories

Archives

Post Categories

Image Galleries

Alternative Feeds

BizTalk Bloggers

BizTalk Sites

CMS Bloggers

Fun

Other Bloggers

SharePoint Bloggers

Utilities

WF Bloggers

BizTalk Server 2004/2006







Don't get me wrong. I think the world of BizTalk as a product. But, like any complex piece of software, there are one or two things that annoy me. An orchestration issue which caused me some suffering a few days ago is the auto-construction of orchestration variables.


I spent a couple of hours today looking at the problem we encountered yesterday with the xpath() function in BizTalk. We were attempting to use an XPath to extract the value of a nested element and assign it to a string variable. The nested element () was in the global (anonymous) namespace, but was a child of an element in a named namespace. The code failed on XmlSerializer de-serialisation with an error saying " not expected".



I was recently asked if I would provide some insight into solving the following problem. In the given scenario, data stored in flat files in being delivered to the BizTalk message box via a pass-through pipeline. An orchestration subscribes to these messages and creates XML output. Each time a file is processed, the developer wants to 'dump' the contents of the flat file into an element in the output. Other information, including the file name, is also included in the XML.


Full BizTalk Server 2004/2006 Archive