SOAP Proxy - XML content validator Reviews

Like it says, not-ready-for-production. There are multiple problems with SOAPServlet.extractSoapEnvelope. Coding bugs, liberal assumptions, chokes with XML pre-processor directives (which are often in SOAP responses). Much useless I/O and conversion code that duplicates what commons IOUtils does much better (IOUtils is already provided and in classpath, so no good reason not to use it). For example SOAPServlet.readHttpRequestBody is entirely unnecessary. Doesn't work for me with a HTTPS service. I see no support for authentication. But don't know if these features are really missing, are broken, or just not-documented-and-not-apparent, but with no communication whatsoever for this project (no forums, mailing lists, etc.), there's nobody to ask.

Soap-proxy was very helpful for me to validate my web service. Before soap-proxy, I was unable to test quickly my web service with a real web service in my local environment. "Quickly" is the word. And Soap -proxy can help you simulate a "datapower" equipment. Great work ! Thanks caballero :-)