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 Index » WebSphere Message Broker (ACE) Support » An invalid XML character (Unicode: 0x0) was found

Post new topic  Reply to topic
 An invalid XML character (Unicode: 0x0) was found « View previous topic :: View next topic » 
Author Message
madi
PostPosted: Thu Mar 15, 2007 8:37 am    Post subject: An invalid XML character (Unicode: 0x0) was found Reply with quote

Chevalier

Joined: 17 Jan 2006
Posts: 475

I am getting this exception when i try to do a xsl transforamtion



Quote:
'Transformation failure when processing Stylesheet /usr1/ibus/files/sfidf/schema/xsl/reditCardApplicationForDec
isionRsp_XMLToRes_V01.00.xsl
ERROR: 'An invalid XML character (Unicode: 0x0) was found in the element content of the document.'
ERROR: 'org.apache.xml.utils.WrappedRuntimeException: An invalid XML character (Unicode: 0x0) was found in the element content of the document.'

javax.xml.transform.TransformerException: javax.xml.transform.TransformerException: org.apache.xml.utils.WrappedRuntimeException: An invalid XML character (Unicode: 0x0) was f
ound in the element content of the document.
at org.apache.xalan.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:612)
at org.apache.xalan.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:282)
at com.ibm.xsl.exmlt.ParseFacilitator.parseXmlStylesheet(ParseFacilitator.java:676)
at com.ibm.xsl.exmlt.ParseFacilitator.parse(ParseFacilitator.java:253)
at com.ibm.xsl.exmlt.EnhancedXMLTransform.transformWithStylesheet(EnhancedXMLTransform.java:773)
at com.ibm.xsl.exmlt.EnhancedXMLTransform.transformDocument(EnhancedXMLTransform.java:706)
at com.ibm.xsl.mqsi.XMLTransformData.transformData(XMLTransformData.java:838)
at com.ibm.xsl.mqsi.XMLTransformNode.evaluate(XMLTransformNode.java:942)
at com.ibm.broker.plugin.MbNode.evaluate(MbNode.java:1298)
at com.ibm.broker.plugin.MbOutputTerminal._propagate(Native Method)
at com.ibm.broker.plugin.MbOutputTerminal.propagate(MbOutputTerminal.java:140)
at com.ibm.xsl.mqsi.XMLTransformNode.evaluate(XMLTransformNode.java:1021)
at com.ibm.broker.plugin.MbNode.evaluate(MbNode.java:1298)
Caused by: javax.xml.transform.TransformerException: org.apache.xml.utils.WrappedRuntimeException: An invalid XML character (Unicode: 0x0) was found in the element content of
the document.
at org.apache.xalan.xsltc.trax.TransformerImpl.getDOM(TransformerImpl.java:464)
at org.apache.xalan.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:602)
... 12 more
Caused by: org.apache.xml.utils.WrappedRuntimeException: An invalid XML character (Unicode: 0x0) was found in the element content of the document.
at org.apache.xalan.xsltc.dom.XSLTCDTMManager.getDTM(XSLTCDTMManager.java:393)
at org.apache.xalan.xsltc.dom.XSLTCDTMManager.getDTM(XSLTCDTMManager.java:228)
at org.apache.xalan.xsltc.trax.TransformerImpl.getDOM(TransformerImpl.java:442)
... 13 more
'
)
)
)


now the input is being created by broker in the XMLNSC parser

i cannot understand why broker would create a unicode character in xml

do you guys have any idea why this might happen??

thanks
madi
Back to top
View user's profile Send private message
kimbert
PostPosted: Thu Mar 15, 2007 12:15 pm    Post subject: Reply with quote

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton

Quote:
i cannot understand why broker would create a unicode character in xml
I presume you meant to say 'an invalid unicode character'.
WMB does not check for illegal XML characters when serializing a message tree. That statement is true for all XML processing domains ( XML, XMLNS, XMLNSC, MRM ). So if you put an illegal character into the name or the value of an element, it can result in an illegal XML document being output. You just have to be careful - after all, there are plenty of legal XML characters to choose from
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » An invalid XML character (Unicode: 0x0) was found
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.