In a fit of coincidence and serendipity, I had a user report that the input string
XSD::ValueSpaceError: {http://www.w3.org/2001/XMLSchema}string: cannot accept 'è or à'.
but a project called "soapUI" announced a 1.6beta1 release today. I installed it, and it is not only a joy to use, but it handled the unicode input flawlessly. It's a Java app, and considering what an utter chore it is to get Java doing SOAP properly, the 1-click install was fantastic.
I'm not ready to turn in Ruby for my regression tests, but having an excellent Java SOAP client at hand is a great relief as these SOAP functions (and their users) become more sophisticated.
An interesting aspect of the soapUI project is that it seems to do load testing out of the box. I've cobbled together some nice load-profiling scripts in Ruby, but these functions in soapUI definitely bear investigation.
è or àcaused his Perl SOAP client to send crazy stuff to the server. My Ruby client also freaked out on this string, although not as badly:
XSD::ValueSpaceError: {http://www.w3.org/2001/XMLSchema}string: cannot accept 'è or à'.
but a project called "soapUI" announced a 1.6beta1 release today. I installed it, and it is not only a joy to use, but it handled the unicode input flawlessly. It's a Java app, and considering what an utter chore it is to get Java doing SOAP properly, the 1-click install was fantastic.
I'm not ready to turn in Ruby for my regression tests, but having an excellent Java SOAP client at hand is a great relief as these SOAP functions (and their users) become more sophisticated.
An interesting aspect of the soapUI project is that it seems to do load testing out of the box. I've cobbled together some nice load-profiling scripts in Ruby, but these functions in soapUI definitely bear investigation.