ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum IndexWebSphere Message Broker SupportWhat's wrong with this XML Data

Post new topicReply to topic
What's wrong with this XML Data View previous topic :: View next topic
Author Message
Hartmut Grell
PostPosted: Tue Oct 09, 2001 8:22 am Post subject: Reply with quote

Newbie

Joined: 11 Jul 2001
Posts: 4

after parsing the following XML data:

-

This is an epic audit log 0 used for test




I get the following in the debug trace:
2001-10-09 14:24:31.031999 485 ParserException BIP5004E: An error has been reported by the BIPXML4C component: code '65606'; public id ''; line number '1'; column number '429'; current element 'EPICBODY'; error text 'Reference to external declaration in standalone document. Entity=lt'.
The above error was reported by the XML parser.
Check that the XML message is well-formed and that it adheres to the XML specification.

I don't know why but the XML data is only being displayed when in "edit" mode

[ This Message was edited by: Hartmut Grell on 2001-10-09 09:31 ]
Back to top
View user's profile Send private message
gowdy
PostPosted: Tue Oct 09, 2001 9:46 am Post subject: Reply with quote

Apprentice

Joined: 17 Jul 2001
Posts: 29
Location: Bournemouth, UK

Hi

You need to ensure that you check the box 'Disable HTML on this Post'

Your message reads:

*********************************************
after parsing the following XML data:
<?xml version="1.0" standalone="yes" ?>
- <EPICHEADER>
<HEADER AckRequested="0" DestinationLogicalID="ePICLogServer" GroupStatus="NOT-IN-GROUP" MessageType="ePICAuditLog" RespondToLogicalID="TEST1" Revision="001" SourceLogicalID="TEST1" TimeStampCreated="1002616651218" TimeStampExpired="-1" TransactionID="1002616651218" UniqueID="1002616651218" />
<EPICBODY BodyCategory="ePICMessage" BodyType="ePICAuditLog" Size="667"><?xml version="1.0" standalone="yes" ?><EPICHEADER><HEADER AckRequested="0" CorrelationID="correlation" DestinationLogicalID="ePICLogServer" EncryptionStatus="encriptionID" ExternalID="externalID" GroupStatus="NOT-IN-GROUP" InternalID="InternalID" MessageType="ePICAuditLog" ProcessingCategory="processingCat" RespondToLogicalID="respondID" Revision="001" SessionID="sessioID" SourceLogicalID="TEST1" TimeStampCreated="1002616650515" TimeStampExpired="-1" TransactionID="transaction" UniqueID="1002616650515"></HEADER><EPICBODY BodyCategory="BodyCat" BodyType="BodyType" Size="41">This is an epic audit log 0 used for test</EPICBODY><USERAREA></USERAREA></EPICHEADER></EPICBODY>
<USERAREA />
</EPICHEADER>

I get the following in the debug trace:
2001-10-09 14:24:31.031999 485 ParserException BIP5004E: An error has been reported by the BIPXML4C component: code '65606'; public id ''; line number '1'; column number '429'; current element 'EPICBODY'; error text 'Reference to external declaration in standalone document. Entity=lt'.
The above error was reported by the XML parser.
Check that the XML message is well-formed and that it adheres to the XML specification.

I don't know why but the XML data is only being displayed when in "edit" mode

[ This Message was edited by: Hartmut Grell on 2001-10-09 09:31 ]

*********************************************

Rgds

Mark

[ This Message was edited by: gowdy on 2001-10-09 10:47 ]
Back to top
View user's profile Send private message Send e-mail
Outdesign
PostPosted: Wed Oct 10, 2001 4:57 am Post subject: Reply with quote

Apprentice

Joined: 16 Sep 2001
Posts: 38
Location: Hampshire, UK

The error message is ...
Check that the XML message is well-formed and that it adheres to the XML specification

1. Your message is invalid XML as you have two XML declarations in your message
2. The second XML declaration is contained within the message, within element EPICBODY
3. If you took your XML message and saved it as test.xml and tried to open it with IE5 you would get the same error message.
Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:
Post new topicReply to topic Page 1 of 1

MQSeries.net Forum IndexWebSphere Message Broker SupportWhat's wrong with this XML Data
Jump to:



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP


Theme by Dustin Baccetti
Powered by phpBB 2001, 2002 phpBB Group

Copyright MQSeries.net. All rights reserved.