Forum Discussion

smehaffieUMB's avatar
smehaffieUMB
Occasional Contributor
13 years ago

Invalid charater entity reference: � - Help Needed

I am getting the following error on a response I am getting back from web service. The field the &#x0 is in is a null field in the database. I get a parsing error accessing the web service in Firefox because of the same characters being in the filed, but do not get the parse error when I use IE. So is there anyway I can SoapUI to treat this the same way as IE does and not get the "&#x0" characters in the empty fields? I checked the web services and I am not returning those charcters in the XML so those have to be being added by the browse/SoapUI (rendering engine). If I put a space in the database the error also goes away, but that is unacceptable. I shoudl be able to return a null field back in the XML and have the tag just be empty.

Any help will be appreciatd.

3 Replies

  • nmrao's avatar
    nmrao
    Community Hero
    13 years ago
    Is the response validated against schema? i.e., if the field can't be empty or so in its type definition of xml schema/wsdl?
  • smehaffieUMB's avatar
    smehaffieUMB
    Occasional Contributor
    13 years ago
    No it is not validatinb against a scheme. But the bigger question is why are these characters being shown in the return message in SoapUI and Firefox, but not IE. I have checked the code and the fields are null in the database and I am not sending these characters back in those fields either. So I am not sure where they are being added.

    Is there a way to make SoapUI make the call usign the IE renderign enging instead of what it uses by default? If so, how do I do this?
  • nmrao's avatar
    nmrao
    Community Hero
    13 years ago
    What tool is being used to create the respones? are you setting any encoding while sending the response?