Hello guys,
I have read ur email from last month and figured that u r dealing with some
invalid xml characters and Gary said he changed some setting on weblogic.
Could anyone tell me exactly what was changed on weblogic side.
Thanks
Praveen
- Original Message -
From: <[EMAIL PROTEC
rsity
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 15, 2004 11:58 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: RE: Invalid XML Character Unicode
Hello Sandeep,
Yes looks like it. so we changed some parameter on the web logic and it
started wo
To: [EMAIL PROTECTED]
|
| cc:
|
| Subject: RE: Invalid XML Characte
-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, June 14, 2004 6:07 PM
To: [EMAIL PROTECTED]
Subject: Invalid XML Character Unicode
Hello ,
First Time I got the following
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString
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:
What is the best way to "fix" bad xml being returned from a service?
I can't actually fix the service (it is an MS product) but the xml it
returns isn't valid xml in some spots and I need to be able to parse it.
When Axis tries to parse it, it blows up becuase one of the tags is in the
wrong namep
:
--
Caught SOAPException (SOAP-ENV:Client): Parsing error, response was:
An invalid XML character (Unicode: 0x1) was found in the element content of
the
document.
--
The service have several methods, logon
