| Author |
Message
|
| smdavies99 |
 Posted: Mon Nov 09, 2015 3:10 am Post subject: |
 |
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| mpong wrote: |
This is a migration from biztalk to IIB, biztalk is currently sending output file in xmlns doming and it is working fine with all declaration and DTD. In IIB i have changed it to XMLNSC but I am facing issue on DTD.
Now I changed back to XMLSC everything works fine except encoding on declaration as I am not able to write it. Any suggestion how to put it. |
don't you mean XMLNS.
Have you tried the XML.{declaration_thingy} style of notation for setting the decparation as has been suggested?
If you have what was the result?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
 |
| maurito |
| Posted: Mon Nov 09, 2015 3:11 am Post subject: |
|
|
Partisan
Joined: 17 Apr 2014
Posts: 358
|
| mpong wrote: |
This is a migration from biztalk to IIB, biztalk is currently sending output file in xmlns doming and it is working fine with all declaration and DTD. In IIB i have changed it to XMLNSC but I am facing issue on DTD.
Now I changed back to XMLSC everything works fine except encoding on declaration as I am not able to write it. Any suggestion how to put it. |
what do you mean by XMLSC ?... either XMLNS or XMLNSC.
I also asked what have you tried to output the encoding ?.. I mean, what ESQL sentence ?
Failing everything else, you could also look at the example in the knowledge centre ?... or would that be cheating ?... search for outputroot.xmlns. and look at "Constructing an XML message tree" |
|
| Back to top |
|
|
| mpong |
| Posted: Mon Nov 09, 2015 3:20 am Post subject: |
|
|
Disciple
Joined: 22 Jan 2010
Posts: 164
|
Hi Maurito/smdavies99/timber,
I mean I tried the below and it worked fine in XMLNS domain and I am able to open the output xml file in IE.
But when I change UTF-8 to UTF-16, it is again blank in IE.
SET OutputRoot.XMLNS.(XML.XmlDecl).(XML."Encoding")='UTF-8';
SET OutputRoot.XMLNS.(XML.DocTypeDecl)ledesxml = '';
SET OutputRoot.XMLNS.(XML.DocTypeDecl).(XML.SystemId) = 'http://www.ledes.org/ledes2000.dtd'; |
|
| Back to top |
|
|
| maurito |
| Posted: Mon Nov 09, 2015 3:22 am Post subject: |
|
|
Partisan
Joined: 17 Apr 2014
Posts: 358
|
| mpong wrote: |
Hi Maurito/smdavies99/timber,
I mean I tried the below and it worked fine in XMLNS domain and I am able to open the output xml file in IE.
But when I change UTF-8 to UTF-16, it is again blank in IE.
SET OutputRoot.XMLNS.(XML.XmlDecl).(XML."Encoding")='UTF-8';
SET OutputRoot.XMLNS.(XML.DocTypeDecl)ledesxml = '';
SET OutputRoot.XMLNS.(XML.DocTypeDecl).(XML.SystemId) = 'http://www.ledes.org/ledes2000.dtd'; |
and what do you get with the above code ?
| Code: |
<?xml version="1.0" encoding="UTF-8"?> |
something like the line above ?? |
|
| Back to top |
|
|
| mpong |
| Posted: Mon Nov 09, 2015 3:28 am Post subject: |
|
|
Disciple
Joined: 22 Jan 2010
Posts: 164
|
I got the below when using UTF-8
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ledesxml SYSTEM "http://www.ledes.org/ledes2000.dtd">
When I change to UTF-16 then the output is as below
<?xml version="1.0" encoding="UTF-16"?>
<!DOCTYPE ledesxml SYSTEM "http://www.ledes.org/ledes2000.dtd">
My worry is I am able to open UTF-8 file in IE where as UTF-16 is failed to open and UTF-16 is needed in application.  |
|
| Back to top |
|
|
| maurito |
| Posted: Mon Nov 09, 2015 3:35 am Post subject: |
|
|
Partisan
Joined: 17 Apr 2014
Posts: 358
|
| mpong wrote: |
I got the below when using UTF-8
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ledesxml SYSTEM "http://www.ledes.org/ledes2000.dtd">
When I change to UTF-16 then the output is as below
<?xml version="1.0" encoding="UTF-16"?>
<!DOCTYPE ledesxml SYSTEM "http://www.ledes.org/ledes2000.dtd">
My worry is I am able to open UTF-8 file in IE where as UTF-16 is failed to open and UTF-16 is needed in application. |
Try a different browser, for example, google chrome. |
|
| Back to top |
|
|
| mpong |
| Posted: Mon Nov 09, 2015 3:43 am Post subject: |
|
|
Disciple
Joined: 22 Jan 2010
Posts: 164
|
| Other browsers does not show up XML declaration part. |
|
| Back to top |
|
|
| maurito |
| Posted: Mon Nov 09, 2015 3:47 am Post subject: |
|
|
Partisan
Joined: 17 Apr 2014
Posts: 358
|
| mpong wrote: |
| Other browsers does not show up XML declaration part. |
you were complaining about opening the file and not about showing the declaration part. Can you open the file with other browsers ? |
|
| Back to top |
|
|
| mpong |
| Posted: Mon Nov 09, 2015 3:53 am Post subject: |
|
|
Disciple
Joined: 22 Jan 2010
Posts: 164
|
| Yes, I am able to open the file in other browsers. |
|
| Back to top |
|
|
| maurito |
| Posted: Mon Nov 09, 2015 3:55 am Post subject: |
|
|
Partisan
Joined: 17 Apr 2014
Posts: 358
|
| mpong wrote: |
| Yes, I am able to open the file in other browsers. |
In that case you have the following options:
- use a different browser.
- contact Microsoft and ask them why IE cannot open the file.
- use UTF-8 instead of UTF-16 |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Nov 09, 2015 3:55 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20767
Location: LI,NY
|
Changing the declaration part to UTF-16 does not change the content.
You also need to change the CCSID from 1208 to 1200, 1201 or 1202 (with bom indicator)...
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| timber |
| Posted: Mon Nov 09, 2015 4:01 am Post subject: |
|
|
Grand Master
Joined: 25 Aug 2015
Posts: 1292
|
Please think carefully before answering this question...
Your message flow is *claiming* that the document is UTF-16 ( that's what the 'Encoding'' attribute is saying ). But what is the *actual* CCSID of the output XML?
Is it possible that IE is trying to interpret the document as UTF-16 and it is failling because it is actually UTF-8? ( I think fjb_saper had the same thought as me ). |
|
| Back to top |
|
|
| maurito |
| Posted: Mon Nov 09, 2015 4:03 am Post subject: |
|
|
Partisan
Joined: 17 Apr 2014
Posts: 358
|
| timber wrote: |
Please think carefully before answering this question...
Your message flow is *claiming* that the document is UTF-16 ( that's what the 'Encoding'' attribute is saying ). But what is the *actual* CCSID of the output XML?
Is it possible that IE is trying to interpret the document as UTF-16 and it is failling because it is actually UTF-8? ( I think fjb_saper had the same thought as me ). |
correct, and it was one of the first things I asked, which the OP never answered.
| Quote: |
are you sure you want utf-16 and not UTF-8 ?
|
|
|
| Back to top |
|
|
| mpong |
| Posted: Mon Nov 09, 2015 4:05 am Post subject: |
|
|
Disciple
Joined: 22 Jan 2010
Posts: 164
|
Hi Maurito, The same file which is generated out from BizTalk having UTF-16 is opening in IE  which is also XMLNS domain. |
|
| Back to top |
|
|
| maurito |
| Posted: Mon Nov 09, 2015 4:08 am Post subject: |
|
|
Partisan
Joined: 17 Apr 2014
Posts: 358
|
| mpong wrote: |
| Hi Maurito, The same file which is generated out from BizTalk having UTF-16 is opening in IE which is also XMLNS domain. |
look at the posts by fjb_saper and kimber. just for info
| Code: |
ccsid 1208 = UTF-8
1200 = UTF-16 BE
1201 = UTF-16 BE
1202 = UTF-16 LE
|
|
|
| Back to top |
|
|
|
|
