smashbts.blogspot.com
BizTalk Fringe: Overriding BizTalk Dehydration mechanism
http://smashbts.blogspot.com/2011/01/overriding-biztalk-dehydration.html
Tales from the Integration frontier:. How come when nobody knows and it doesn't make sense, they come to us? Giovedì, gennaio 13, 2011. Overriding BizTalk Dehydration mechanism. On of the most annoying thing I find in orchestration design is the amount of planning one have to put in. What to do if we already contacted five external system when the sixth system rejected the data? Of our actions put us in need to redo only part of our actions:. Activation (original message) should contain an. EAI Patterns ...
smashbts.blogspot.com
BizTalk Fringe: settembre 2010
http://smashbts.blogspot.com/2010_09_01_archive.html
Tales from the Integration frontier:. How come when nobody knows and it doesn't make sense, they come to us? Domenica, settembre 26, 2010. Testing in a BizTalk project is always a tricky task principally due to the. And term overlapping which IMHO accompany it . This confusion can be traced back. To three main reasons:. The most famous testing framework for BizTalk Server has been erroneously. Of biztalk is to. Keeping, as more as possible, these two levels decoupled, simplify testing management. For mes...
smashbts.blogspot.com
BizTalk Fringe: gennaio 2011
http://smashbts.blogspot.com/2011_01_01_archive.html
Tales from the Integration frontier:. How come when nobody knows and it doesn't make sense, they come to us? Giovedì, gennaio 13, 2011. Overriding BizTalk Dehydration mechanism. On of the most annoying thing I find in orchestration design is the amount of planning one have to put in. What to do if we already contacted five external system when the sixth system rejected the data? Of our actions put us in need to redo only part of our actions:. Activation (original message) should contain an. EAI Patterns ...
smashbts.blogspot.com
BizTalk Fringe: febbraio 2011
http://smashbts.blogspot.com/2011_02_01_archive.html
Tales from the Integration frontier:. How come when nobody knows and it doesn't make sense, they come to us? Martedì, febbraio 01, 2011. BizTalk Pipeline Template (Visual Studio 2005). During years of BizTalk development, I’ve finalized a set of standard pipeline components I use on every pipeline of mine. What these pipeline components do is not important here (one is the BAM Pipeline Component depicted here. What we need, in Visual Studio terminology, is an Item Template. This is not unexpected: when V...
smashbts.blogspot.com
BizTalk Fringe: luglio 2010
http://smashbts.blogspot.com/2010_07_01_archive.html
Tales from the Integration frontier:. How come when nobody knows and it doesn't make sense, they come to us? Sabato, luglio 17, 2010. According to Wikipedia mock objects. Simulated objects that mimic the behavior of real objects in controlled ways. The behavior of complex, real (non-mock) objects and are therefore useful when a real object is impractical or impossible to incorporate into a unit test. From the BizTalk environment point of view the concept of unit testing is a bit tricky, as BizUnit. Hones...
smashbts.blogspot.com
BizTalk Fringe: Using Unity in BizTalk Solutions
http://smashbts.blogspot.com/2011/01/using-unity-in-biztalk-solutions.html
Tales from the Integration frontier:. How come when nobody knows and it doesn't make sense, they come to us? Giovedì, gennaio 06, 2011. Using Unity in BizTalk Solutions. Is the pattern and practice solution for realizing Dependency Injection and Inversion Of Control. Is the simplest way to. So, as every good OO developers, you’ll start in developing an Interface declaring the method you’ll use to retrieve configuration data such as the following:. But there’s a catch:. IConfigurationStore Config = new.
smashbts.blogspot.com
BizTalk Fringe: BizTalk Versioning Strategy (4/4)
http://smashbts.blogspot.com/2011/01/biztalk-versioning-strategy-44.html
Tales from the Integration frontier:. How come when nobody knows and it doesn't make sense, they come to us? Giovedì, gennaio 13, 2011. BizTalk Versioning Strategy (4/4). Previous part available here. Really speaking, versioning problem is not the same for each biztalk artifacts:. Orchestrations, for example, are not referenced by any other artifacts and therefore, can be updated with the Modify procedure descripted in the previous part without any risk replacing the old orchestration with the new one.
smashbts.blogspot.com
BizTalk Fringe: BizTalk Versioning Strategy (3/4)
http://smashbts.blogspot.com/2011/01/biztalk-versioning-strategy-34.html
Tales from the Integration frontier:. How come when nobody knows and it doesn't make sense, they come to us? Lunedì, gennaio 10, 2011. BizTalk Versioning Strategy (3/4). Continued from part 2. So every problem seems due to the fact that orchestration are tightly coupled with .NET types representing message schemas and therefore they’ll fail to execute if fed with wrong .NET Type. In fact we’ve reduced BizTalk Versioning strategy problem to a normal .NET Versioning one:. The NET answer is “. So there̵...
smashbts.blogspot.com
BizTalk Fringe: BizTalk Pipeline Template (Visual Studio 2005)
http://smashbts.blogspot.com/2011/02/biztalk-pipeline-template-visual-studio.html
Tales from the Integration frontier:. How come when nobody knows and it doesn't make sense, they come to us? Martedì, febbraio 01, 2011. BizTalk Pipeline Template (Visual Studio 2005). During years of BizTalk development, I’ve finalized a set of standard pipeline components I use on every pipeline of mine. What these pipeline components do is not important here (one is the BAM Pipeline Component depicted here. What we need, in Visual Studio terminology, is an Item Template. This is not unexpected: when V...