We have created two orchestrations. Orchestration-1 sends an xml mail
message via MSMQT to Orchestration-2. The message received is different from
the one sent out. Extra "\r\n " strings are added at the begin and end of
each tag names.

Any ideas? Thank you in advance.

Johnny

[ Post a follow-up to this message ]

that may not make a difference when using XML, does it matter in your case?
however you may need to specify some configuration on the pipeline you are
using

Regards,
Christof

"Johnny W" <tcwangs@msn.com> wrote in message
news:Of3dcfXHEHA.2300@tk2msftngp13.phx.gbl...
> We have created two orchestrations. Orchestration-1 sends an xml mail
> message via MSMQT to Orchestration-2. The message received is different
from
> the one sent out. Extra "\r\n " strings are added at the begin and end of
> each tag names.
>
> Any ideas? Thank you in advance.
>
> Johnny
>
>

[ Post a follow-up to this message ]

The transport type of this message is MSMQT. The send pipeline is:
"Microsoft.BizTalk.DefaultPipelines.XMLTransmit", and the receive pipeline
is "Microsoft.BizTalk.DefaultPipelines.XMLReceive". The xml message was
normal before it was sent out. I have no problem to parse the receive
message to remove the extra "\r\n  " strings, but there must be a better way
to do it.

-Jonny

"Christof" <bts2004communityfeedback (at) hotmail (dot) com> wrote in
message news:OYmMiDlHEHA.4092@TK2MSFTNGP11.phx.gbl...
> that may not make a difference when using XML, does it matter in your
case?
> however you may need to specify some configuration on the pipeline you are
> using
>
> Regards,
> Christof
>
> "Johnny W" <tcwangs@msn.com> wrote in message
> news:Of3dcfXHEHA.2300@tk2msftngp13.phx.gbl... 
> from 
of 
>
>

[ Post a follow-up to this message ]

I think you misunderstood me:
- you can create a custom pipeline and configure the contained components
yourself.
- normally, the "\r\n" should NOT change the semantics of your message in
any way.  It's just whitespace and ignored by any XML compliant parser.

Was wondering why the "\r\n" is bothering you so hard :-) ?
Kind regards,

Christof


"tcw" <tcwangs@msn.com> wrote in message
news:OPn%23PwzHEHA.348@tk2msftngp13.phx.gbl...
> The transport type of this message is MSMQT. The send pipeline is:
> "Microsoft.BizTalk.DefaultPipelines.XMLTransmit", and the receive pipeline
> is "Microsoft.BizTalk.DefaultPipelines.XMLReceive". The xml message was
> normal before it was sent out. I have no problem to parse the receive
> message to remove the extra "\r\n  " strings, but there must be a better
way
> to do it.
>
> -Jonny
>
> "Christof" <bts2004communityfeedback (at) hotmail (dot) com> wrote in
> message news:OYmMiDlHEHA.4092@TK2MSFTNGP11.phx.gbl... 
> case? 
are 
different 
> of 
>
>

[ Post a follow-up to this message ]

It actually drives me nuts. I don't understand where these extra chars come
from. Why didn't I see this when I ran BizTalk 2004 beta? This part of code
has never been changed since beta.

-Johnny

"Christof" <bts2004communityfeedback (at) hotmail (dot) com> wrote in
message news:uTy$vD4HEHA.3376@TK2MSFTNGP09.phx.gbl...
> I think you misunderstood me:
> - you can create a custom pipeline and configure the contained components
> yourself.
> - normally, the "\r\n" should NOT change the semantics of your message in
> any way.  It's just whitespace and ignored by any XML compliant parser.
>
> Was wondering why the "\r\n" is bothering you so hard :-) ?
> Kind regards,
>
> Christof
>
>
> "tcw" <tcwangs@msn.com> wrote in message
> news:OPn%23PwzHEHA.348@tk2msftngp13.phx.gbl... 
pipeline 
> way 
> are 
mail 
> different 
end 
>
>

[ Post a follow-up to this message ]

The XML pipeline can do whatever it wants as long as the output XML is
semantically the same as the input. Your components/applications shoudn't
rely on the presence or absence of whitespaces.

[ Post a follow-up to this message ]