You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by ga...@jpmorgan.com on 2004/06/15 00:07:21 UTC

Invalid XML Character Unicode


Hello ,

First Time I got the following

faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
 faultSubcode:
 faultString: org.xml.sax.SAXParseException: An invalid XML character
(Unicode: 0x0) was found in the value of attribute "href".
 faultActor:
 faultNode:
 faultDetail:

Second time the exception looked like ::-

 faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
 faultSubcode:
 faultString: org.xml.sax.SAXParseException: Element type
"ns101:MarketClie" must be followed by either attribute
specifications, ">" or "/>".
 faultActor:
 faultNode:
 faultDetail:
      {http://xml.apache.org/axis/}stackTrace:
org.xml.sax.SAXParseException: Element type "ns101:MarketClie"
must be followed by either attribute specifications, ">" or
"/>".
      at
org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:1213)
      at
org.apache.xerces.framework.XMLDocumentScanner.reportFatalXMLError(XMLDocumentScanner.java:579)
      at
org.apache.xerces.framework.XMLDocumentScanner.abortMarkup(XMLDocumentScanner.java:628)
      at
org.apache.xerces.framework.XMLDocumentScanner.scanElement(XMLDocumentScanner.java:1800)
      at
org.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispatch(XMLDocumentScanner.java:1182)


Any ideas on this.

Thanks and Regards,

===
Gary Grewal





This communication is for informational purposes only.  It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data 
and other information are not warranted as to completeness or accuracy and 
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan Chase & Co., its
subsidiaries and affiliates.

RE: Invalid XML Character Unicode

Posted by Sandeep <sa...@binghamton.edu>.
Gary,

I had the same exception. Looks to me that the data producing this exception
is binary and probably needs Base64 encoding. I tried sending byte codes
wrapped in a String object and landed in the same pool. 

Sandeep Advani
Grid Research Lab, Binghamton University
-----Original Message-----
From: gary.si.grewal@jpmorgan.com [mailto:gary.si.grewal@jpmorgan.com] 
Sent: Monday, June 14, 2004 6:07 PM
To: axis-user@ws.apache.org
Subject: Invalid XML Character Unicode



Hello ,

First Time I got the following

faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
 faultSubcode:
 faultString: org.xml.sax.SAXParseException: An invalid XML character
(Unicode: 0x0) was found in the value of attribute &quot;href&quot;.
 faultActor:
 faultNode:
 faultDetail:

Second time the exception looked like ::-

 faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
 faultSubcode:
 faultString: org.xml.sax.SAXParseException: Element type
&quot;ns101:MarketClie&quot; must be followed by either attribute
specifications, &quot;&gt;&quot; or &quot;/&gt;&quot;.
 faultActor:
 faultNode:
 faultDetail:
      {http://xml.apache.org/axis/}stackTrace:
org.xml.sax.SAXParseException: Element type &quot;ns101:MarketClie&quot;
must be followed by either attribute specifications, &quot;&gt;&quot; or
&quot;/&gt;&quot;.
      at
org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:1213)
      at
org.apache.xerces.framework.XMLDocumentScanner.reportFatalXMLError(XMLDocume
ntScanner.java:579)
      at
org.apache.xerces.framework.XMLDocumentScanner.abortMarkup(XMLDocumentScanne
r.java:628)
      at
org.apache.xerces.framework.XMLDocumentScanner.scanElement(XMLDocumentScanne
r.java:1800)
      at
org.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispatch(XM
LDocumentScanner.java:1182)


Any ideas on this.

Thanks and Regards,

===
Gary Grewal





This communication is for informational purposes only.  It is not intended
as
an offer or solicitation for the purchase or sale of any financial
instrument
or as an official confirmation of any transaction. All market prices, data 
and other information are not warranted as to completeness or accuracy and 
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan Chase & Co., its
subsidiaries and affiliates.