I'm forgetting the details, but there is a known bug with Visual Studio and this description reminds me of it. If you edit/create an XML file in Visual Studio, it torques up the encoding ... you have to manually change the setting on the file in Visual Studio.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, April 04, 2003 4:36 AM To: [EMAIL PROTECTED] Subject: Re: .NET and AXIS Interop - Please Help!! Parag, You said that you had a problem with an extra character in the SOAP xml from a .NET client. "An invalid XML character (Unicode: 0x0) was found in markup after the end of the element content." I have noticed a similar problem when sample XML messages I use for testing are opened with MS Word. Extra characters are inserted at the begining and end of the file. I am using xerces to parse the XML and I get the same parse exception. My temporary solution was to remove everything outside of the start/end tags. I wonder if this is a feature in all Microsoft products. Is the XML valid if there are extra characters outside of the start/end tags? Matt "Joshi, Parag" <[EMAIL PROTECTED]> on 04/03/2003 09:18:31 PM Please respond to [EMAIL PROTECTED] To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> cc: Subject: .NET and AXIS Interop - Please Help!! Hi, I have written a Java client program using axis 1.0 and the program sends SOAP message to my webservice written in Microsoft .NET environment. The .NET Webservice successfully receives the request and returns a response indicating success. I used XMLSpy to check request and response messages and they seem fine (almost same except request header replaced by response). But, my Java client shows the following exception parsing the SOAP response: SAXParseException: An invalid XML character (Unicode: 0x0) was found in markup after the end of the element content. I did see an extra character (which might be 0x0) at the end of response message coming from .NET. It is the last character in the message. I do not control XML SOAP message generation because it is done by .NET. Is there anyway for me to make the SAX parser ignore that extra character at the end? On another machine with similar setup I get a slightly different exception: faultString: org.xml.sax.SAXParseException: Content is not allowed in trailing section. The exception trace is included below. I will greatly appreciate any help!! Thanks -Parag ----------------------------------------------------- [java] AxisFault [java] faultCode: {http://xml.apache.org/axis/}Server.userException [java] faultString: org.xml.sax.SAXParseException: An invalid XML characte r (Unicode: 0x0) was found in markup after the end of the element content. [java] faultActor: null [java] faultDetail: [java] stackTrace: org.xml.sax.SAXParseException: An invalid XML charac ter (Unicode: 0x0) was found in markup after the end of the element content. [java] at org.apache.xerces.framework.XMLParser.reportError(XMLParser.j ava:1196) [java] at org.apache.xerces.framework.XMLDocumentScanner.reportFatalXML Error(XMLDocumentScanner.java:644) This transmission may contain information that is privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you.
