Browse by Tags

One of the interesting challenges I’ve faced in the last year was creating a flat file schema for a well established custom flat file format that was in use at one of my clients. What made this flat file format different from most that I had dealt with in the past was that this flat […] Blog...

Last week I ran into a really interesting issue. When I was running Visual Studio unit tests to validate instances of XML formatted EDIFact messages (see my previous blog post on BizTalk testing for more details on schema testing) I found that my tests just seemed to take forever and timed out with no...

A colleague of mine was implementing a system which required a generic XML on ramp that accepted messages from a variety of trading partners. He quickly encountered the age-old problem of not so sophisticated trading partners sending XML documents which contained no namespaces. This can quickly become...

The out of the box unit test framework for BizTalk maps leaves a lot to be desired. Effectively a Visual Studio map unit test is the equivalent of choosing to validate your map, which involves running an instance of an input message through your map and validating the output of the map against it’s...

I’ve been working on a BizTalk solution which includes a scenario in which I am receiving envelope messages that are to be debatched in a receive pipeline using an XML Disassembler pipeline component, correlating the debatched messages which will be of different message types to relevant orchestrations...

When creating schemas I typically follow the rule that each xsd file contains one root node only. However when dealing with schemas that have been generated from metadata it is quite common for schemas to be generated with multipe root nodes. In the case of web services all the request and response schema...