Steve, If you don't try it, 1.2 final will have the same bug and you will be stuck for many more months. It's your call, we're just asking feedback on whether the bug exists in latest code.
-- dims On Thu, 3 Jun 2004 17:09:26 +0200, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > I cannot try the nightly build as the company policy for upgrading product > versions are pretty strict. > > Regards > > Steve > > > Quoting Davanum Srinivas <[EMAIL PROTECTED]>: > > > can you please try the nightly build? if it still fails, please open a > > bug report with sample code to recreate the problem. > > > > thanks, > > dims > > > > On Thu, 3 Jun 2004 10:48:55 +0200, [EMAIL PROTECTED] > > <[EMAIL PROTECTED]> wrote: > > > > > > Hi Jeff and anybody else out there whom may be able to help..... > > > > > > The SOAP request is stored as text in a file. Originally is was saved in > > UTF-8 > > > format and the German character � showed up in TCPMON as the two characters > > ö > > > which is how it is displayed in ISO-8859-1. > > > > > > I opend the file in ISO-8859-1 using JEdit, changed the offending > > characters > > > back to thier German format from the 2 character format displayed and > > resaved > > > the file. > > > > > > Now in TCPMON the request looks correct and the back end can understand > > the > > > content. However, TCPMON shows the responce to have the same encoding > > problem. > > > It shows the German UTF-8 characters as htier ISO-8859-1 equivalent. > > > > > > I also have a <wsdlFile> element in my server-config.wsdd so that axis > > shows my > > > wsdl file instead of its generated wsdl (needed because axis cocks up the > > > namespace for <fault> elements and fails to deserialise all but the first > > from > > > its hash map). I opend this also in JEdit ISO8859-1 encoding and changed > > the 2 > > > character representations to the German characters and resaved this. Axis > > does > > > not show the wsdl at all after this. > > > > > > I know its an encoding issue but I am stuck as to weather its AXIS, Tomcat > > or > > > the JVM that is causing my encoding headaches. > > > > > > I am using Axis 1.1, Tomcat 4.1.27 and JVM 1.4.2_02 > > > > > > Any help in pointing me in the right direction would be great. I have > > attached > > > my wsdl to this mail (in UTF-8 character encoding) in the hope that it > > could > > > help. I have also attached the SOAP message (in ISO-8859-1 characted > > encoding). > > > > > > Best regards > > > > > > Steve > > > > > > Quoting Jeff Loomis <[EMAIL PROTECTED]>: > > > > > > > > If I access the wsdl file using > > > > > http://<host>:<port>/<context>/services/<web_service>?wsdl > > > > > usinf the same version of Internet explorer I get the > > > > > following error at the first special German characted encountered > > > > > > > > In your original example your file contains: > > > > > > > > > xsi:type='xsd:string'>Zubeh�r</category>> > > > > > > > > Which showed up like this: > > > > > > > > > xsi:type='xsd:string'>Zubehör</category> > > > > > > > > on the server when using TCPMonitor. > > > > > > > > You did not state how the request XML was generated or how you copied it > > for > > > > use in your message. It may be that the message was valid UTF-8 and was > > > > translated for you when you pasted it into your email program. If you > > look > > > > at the request with a hex editor, the � should appear as C3 B6. This is > > the > > > > UTF-8 encoding of that character, and it will show up as ö if you view > > the > > > > file with an editor that thinks it is looking at iso8859-1. > > > > > > > > Since TCPMonitor is showing two characters, it implies that something on > > your > > > > client is converting your message to UTF-8 twice. > > > > > > > > -Jeff > > > > > > > > > > > > > > > > > > > > >
