RE: Problem with Custom Send Pipeline Component
- From: ruslany@xxxxxxxxxxxxxxxxxxxx (Ruslan Yakushev [MSFT])
- Date: Sat, 02 Apr 2005 01:39:41 GMT
Those characters at the beginning is the UTF-8 byte order mark. This is the
default encoding used withing the server. What you can do is to add logic
in the FixMsg component to check for those 3 bytes at the beginning and
remove them.
Simpler, but not universal way to get rid of those characters is to place
your component after the XML assembler and set XML assembler property
"Targer charset" to "ASCII" or any other non unicode charset. This way the
input stream for FixMsg component will not have byte order mark but of
course you will be limited to ASCII encoding only.
--------------------
>
>Hi,
>
>We are using the FixMsg component to prepend a String to an XML message
>before it is sent out of BizTalk to Siebel.
>
>We have noticed some unknown characters passing after the define String
and
>in between the xml message.
>
>Has anybody come across with similar issues? If yes, what is the
correction
>required.
>
>Thanks
>Venkat
>
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
.
- Prev by Date: Re: How to consume a webservice which returns a dataset
- Next by Date: BRE and Forward Chaining
- Previous by thread: Re: What's the simplest way to implement this?
- Next by thread: BRE and Forward Chaining
- Index(es):
Relevant Pages
|
Loading
