Re: BizTalk 2002 - XML Declaration - Unicode
From: Michael (Michael_at_xyzzy.com)
Date: 07/08/04
- Next message: Matt Milner: "Re: Deploy business rules without using the RE deployment wizard"
- Previous message: Matt Milner: "Re: Dynamic Transform"
- In reply to: larry franks: "RE: BizTalk 2002 - XML Declaration - Unicode"
- Next in thread: larry franks: "Re: BizTalk 2002 - XML Declaration - Unicode"
- Reply: larry franks: "Re: BizTalk 2002 - XML Declaration - Unicode"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 07 Jul 2004 23:01:09 -0400
Larry,
Yes, we are using HTTP - but ours was coming out UTF-16. We captured
the raw data from an ASP page.
The only way we have been able to get this to work is to use a
pipeline with the charset to ASCII and disabling the XML declaration
as you have done.
The only thing we tried on the ASP side was to properly detect the
content type and use an ADO Stream object to convert the data from
binary to the appropriate text type. We then submit it to MSMQ.
In my mind the big deal here is that you have to know to create a
pipeline and make these changes just to get BizTalk 2004 to talk to
BizTalk 2002 out of the box. It seems it is not very backward
compatible.
Michael
On Wed, 07 Jul 2004 17:11:04 GMT, larryfr@online.microsoft.com ("larry
franks") wrote:
>Followup posting.
>
>>From my testing, if I save to file from BizTalk 2004 and then use a file
>receive function to read in this data this appears to work fine. However
>if I try to submit this data as a string it fails.
>I'm assuming that you are sending over HTTP? On my machine the data is
>sent in UTF-8 encoding with byte order mark and the XML declaration set to
>UTF-8. I was able to get BizTalk 2004 to send the data as ASCII by
>creating a pipeline and setting the target charset to ASCII. This appears
>to be received fine on the BizTalk 2002 side. I also disabled XML
>declaration generation in the XML assembler component in my pipeline.
>
>On the BizTalk 2002 side you could possibly resolve this by receiving the
>data in an .asp page and modifying the data format before submitting to
>BizTalk 2002.
>
>I'm still investigating this as it is often desirable to send the document
>in UTF-8 since this allows encoding of non-english character sets.
>Larry Franks
>
>This posting is provided "AS IS" with no warranties,and confers no rights.
>Subscribe at
>http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
>&SD=msdn
>--------------------
>| X-Tomcat-ID: 620745903
>| References: <euj3e0d9m6nm9cle2jgn49n2ahjelp5n0t@4ax.com>
>| MIME-Version: 1.0
>| Content-Type: text/plain
>| Content-Transfer-Encoding: 7bit
>| From: larryfr@online.microsoft.com ("larry franks")
>| Organization: Microsoft
>| Date: Thu, 01 Jul 2004 21:16:55 GMT
>| Subject: RE: BizTalk 2002 - XML Declaration - Unicode
>| X-Tomcat-NG: microsoft.public.biztalk.general
>| Message-ID: <7p28SJ7XEHA.3316@cpmsftngxa06.phx.gbl>
>| Newsgroups: microsoft.public.biztalk.general
>| Lines: 54
>| Path: cpmsftngxa06.phx.gbl
>| Xref: cpmsftngxa06.phx.gbl microsoft.public.biztalk.general:16718
>| NNTP-Posting-Host: TOMCATIMPORT1 10.201.218.122
>|
>| Ok, I've reproduced this. I'll look into it and see what I can find.
>|
>| Larry Franks
>|
>| This posting is provided "AS IS" with no warranties,and confers no
>rights.
>| Subscribe at
>|
>http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
>| &SD=msdn
>| --------------------
>| | From: Michael <Michael@xyzzy.com>
>| | Subject: BizTalk 2002 - XML Declaration - Unicode
>| | Date: Tue, 29 Jun 2004 16:32:02 -0400
>| | Reply-To: Michael@xyzzy.com
>| | Message-ID: <euj3e0d9m6nm9cle2jgn49n2ahjelp5n0t@4ax.com>
>| | X-Newsreader: Forte Agent 1.93/32.576 English (American)
>| | MIME-Version: 1.0
>| | Content-Type: text/plain; charset=us-ascii
>| | Content-Transfer-Encoding: 7bit
>| | Newsgroups: microsoft.public.biztalk.general
>| | NNTP-Posting-Host: pow229159.columbus.rr.com 204.210.229.159
>| | Lines: 1
>| | Path:
>|
>cpmsftngxa06.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFTNGP0
>| 8.phx.gbl!TK2MSFTNGP09.phx.gbl
>| | Xref: cpmsftngxa06.phx.gbl microsoft.public.biztalk.general:16593
>| | X-Tomcat-NG: microsoft.public.biztalk.general
>| |
>| | What is the definitive situation with BizTalk 2002 and different
>| | document encodings?
>| |
>| | We are starting to use BizTalk 2004 and our first outbound document to
>| | a BizTalk 2002 partner failed with:
>| |
>| | [0x1439] No parser component recognizes the data. This might be caused
>| | by an interchange specification that is missing or not valid, or it
>| | might be caused by data that is not valid. Verify that both the
>| | interchange specification (if one is specified) and the data match.
>| |
>| | The outbound document uses the default XML pipeline and appears to be
>| | UTF-16 with a byte order mark.
>| |
>| | I tried configuring a custom pipeline with ASCII as the target charset
>| | but that didn't work. After removing the XML declaration BizTalk 2002
>| | can read the document.
>| |
>| | Is there a way to configure BizTalk 2002 so that it can receive a
>| | document from BizTalk 2004 without writing a pipeline? Does BizTalk
>| | 2002 read the XML declaration header and / or the byte order mark to
>| | determine the document encoding?
>| |
>| | Thanks for an enlightenment.
>| |
>| | Michael
>| |
>|
>|
- Next message: Matt Milner: "Re: Deploy business rules without using the RE deployment wizard"
- Previous message: Matt Milner: "Re: Dynamic Transform"
- In reply to: larry franks: "RE: BizTalk 2002 - XML Declaration - Unicode"
- Next in thread: larry franks: "Re: BizTalk 2002 - XML Declaration - Unicode"
- Reply: larry franks: "Re: BizTalk 2002 - XML Declaration - Unicode"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
