http://www.richardhallgren.com/bam-ate-my-xml-declaration/ .NET, BizTalk and integration focused scribbles Tue, 01 Jun 2010 22:09:55 -0500 http://wordpress.org/?v=2.9.2 hourly 1 http://www.richardhallgren.com/bam-ate-my-xml-declaration/comment-page-1/#comment-374 Richard Thu, 04 Jun 2009 14:49:40 +0000 http://www.richardhallgren.com/bam-ate-my-xml-declaration/#comment-374 @Mikael Håkansson: No, right now I only know it's a problem in R2. I haven't had a chance to test in 2009 yet. Let me know if you do. @Mikael Håkansson: No, right now I only know it’s a problem in R2. I haven’t had a chance to test in 2009 yet. Let me know if you do.

]]> http://www.richardhallgren.com/bam-ate-my-xml-declaration/comment-page-1/#comment-373 Mikael Håkansson Thu, 04 Jun 2009 13:07:50 +0000 http://www.richardhallgren.com/bam-ate-my-xml-declaration/#comment-373 Have you verified if this behaviour exists in 2006, R2 and 2009? Have you verified if this behaviour exists in 2006, R2 and 2009?

]]> http://www.richardhallgren.com/bam-ate-my-xml-declaration/comment-page-1/#comment-370 Thiago Almeida Thu, 28 May 2009 21:08:55 +0000 http://www.richardhallgren.com/bam-ate-my-xml-declaration/#comment-370 Wow, that's pretty annoying indeed. Specially given the fact that you don't even use the message at all in the tracking profile. Thanks for sharing! Wow, that’s pretty annoying indeed. Specially given the fact that you don’t even use the message at all in the tracking profile. Thanks for sharing!

]]> http://www.richardhallgren.com/bam-ate-my-xml-declaration/comment-page-1/#comment-369 Antti Somersalo Thu, 28 May 2009 16:58:15 +0000 http://www.richardhallgren.com/bam-ate-my-xml-declaration/#comment-369 We had a similar problem and opened a case with MS. The problem is that BAM actually probes the message and if it looks like XML, the message will be processed like XML with all the nasty side effects you mentioned. I think it is a bug but very difficult get fixed because it is so deep in BAM implementation. MS proposed that we prefix the file with a space character, so BAM does not recogize it as XML. Obviously you have to strip that character away in the send pipeline. Not something we wanted to do. We had a similar problem and opened a case with MS. The problem is that BAM actually probes the message and if it looks like XML, the message will be processed like XML with all the nasty side effects you mentioned. I think it is a bug but very difficult get fixed because it is so deep in BAM implementation. MS proposed that we prefix the file with a space character, so BAM does not recogize it as XML. Obviously you have to strip that character away in the send pipeline. Not something we wanted to do.

]]>