Re: Two questions - BOM in UTF-8, and manually cleaning XML

[Axel Bock]

Hi,

hm. then ... maybe you could write an axis handler which actually modifies the response buffer before xerces kicks in. I don't know how to do that, though, so you'd have to refer to some other guys who know better :-) .

and, ah, it's AXEL ;-)


Greetings,
Axel.

On 7/5/06, Matthew Brown <[EMAIL PROTECTED] > wrote:

Alex,

 

The problem I am having is with the SOAP response from the web service; so I'm not really sure how we'd be saving that to a file... this isn't a static piece of text.

-----Original Message-----
From: Axel Bock [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 05, 2006 10:17 AM
To: axis-user@ws.apache.org

Subject: Re: Two questions - BOM in UTF-8, and manually cleaning XML

Yes, there is a work-around. It works if you encode the file with UTF-8 (for example), and do not include the BOM at the beginning. I use notepad++ for that task, where you can save in "UTF-8 without BOM".

The process for that is easy:
1. open the file in notepad++
2. mark everything via CTRL-A
3. cut (not copy!)
4. in the format menu, choose "ANSI" formatting and select "UTF without BOM" at the bottom
5. paste
6. save.

that is a crap workaround, but works for me. for automatically generated files ..... I dunno :-)


Greetings,
Axel.

On 7/5/06, Matthew Brown <[EMAIL PROTECTED]> wrote:

Hi all,

 

I hate to do this, but can anyone please help me with either of these issues? I've tried to upgrade Xerces to 2.8.0 but to no avail.

 

Is there anything else I could be doing?

 

What about the possibility of programmatically editing/cleaning the response XML before it is given to the parser?

 

Thanks

Matt

-----Original Message-----
From: Matthew Brown [mailto:[EMAIL PROTECTED]]
Sent: Saturday, July 01, 2006 12:41 PM
To: axis-user@ws.apache.org
Subject: Two questions - BOM in UTF-8, and manually cleaning XML

1. From searching the mailing list archives, I see several references to people having problems with Byte Order Mark characters appearing before the prolog in their UTF-8 messages. However I can't seem to find much of a known resolution to these issues. Is there a standard/common workaround for these BOM and UTF-8 issues?

 

2. If there is no answer to my #1, is there anyway that Axis will allow me to pragmatically edit the response XML before it is passed to the parser and de-serialized? I've tried adding Handlers, but I'm assuming that the Handler comes into the picture after the message is parsed, because my Handler is only ever seeing the request message, and not the response.

 

Thanks

Matt Brown