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

to the parser? Thanks Matt -Original Message-From: Matthew Brown [mailto:[EMAIL PROTECTED]Sent: Saturday, July 01, 2006 12:41 PMTo: axis-user@ws.apache.orgSubject: Two questions - BOM in UTF-8, and manually cleaning XML 1. >From searching the mailing list archives, I

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

orks 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 X

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

. 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] mailto:[EMAIL PROTECTED] wrote: Hi all, I hate to do this, but can anyone please help me with either

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

2006 23:04, Matthew Brown wrote: Manuel, I believe you hit the problem on the head - the response prolog says utf-8 but (according to Etherpeak) the BOM is ff/ef. Coincidentally, by the time the response XML gets logged by axis, these initial characters are logged as ef bf bd ef bf bd. Matt

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

23:12, Matthew Brown wrote: Two bytes per char; Etherpeak is showing the second byte as 00. Seems you are stuck between a rock and a hard place here. The byte stream appears to be correctly utf-16 encoded but the xml prolog says utf-8. Not sure what to recommend. Fix it at the source is obvious

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

example for a servlet filter ;-) Hope this helps, Rodrigo Manuel Mall wrote: On Wednesday 05 July 2006 23:12, Matthew Brown wrote: Two bytes per char; Etherpeak is showing the second byte as 00. Seems you are stuck between a rock and a hard place here. The byte stream appears to be correctly

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

, July 05, 2006 3:41 PM To: axis-user@ws.apache.org Subject: Re: Two questions - BOM in UTF-8, and manually cleaning XML did you see my response on setting the CHARACTER_SET_ENCODING? what is the exact stack trace you get on the client? thanks, dims On 7/5/06, Matthew Brown [EMAIL PROTECTED

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

RE: Content is not allowed in prolog

I happen to be having a similar error, although it isn't an endpoint issue. The response we are getting back from the server looks like this: ?? ? x m l v e r s i o n = " 1 . 0 " e n c o d i n g = " u t f - 8 " ? s o a p : E n v e l o p e x m l n s : s o a p = " h t t p : / / s c h e

RE: Content is not allowed in prolog

to change/configure the parser, or find out if parsing a message such as the one below (with all those extra spaces) is possible? -Original Message-From: Matthew Brown [mailto:[EMAIL PROTECTED]Sent: Friday, June 30, 2006 9:23 AMTo: axis-user@ws.apache.orgSubject: RE: Content

RE: Content is not allowed in prolog

ne. Derek -Original Message-From: Matthew Brown [mailto:[EMAIL PROTECTED] Sent: Friday, June 30, 2006 7:16 AMTo: axis-user@ws.apache.orgSubject: RE: Content is not allowed in prolog Some followup information.. I've tested using .NET and their wsdl

Strange format of SOAP Response causing errors

the client. Should we be setting the character set / encoding expected in the response stream manually somewhere? Thanks Matthew Brown