in reply to SOAP and .NET
The .NET web-service should be publishing a WSDL description of what the service expects. Clients of the service need merely translate the WSDL into "proxy" methods of the service.
Even though my script runs with apparently no errors, the other end is saying nothing is coming through.How exactly is the "other end" saying this? That you're script runs with "no errors" is probably meaningless, as you'd need to explicitly handle any SOAP fault objects that are sent back to the client.
In the worst case, you can turn on debugging in SOAP::Lite to see what is being sent to and received from the .NET service.
On the perl client side, I absolutely recommend SOAP::WSDL as it does almost all of the hard work for you; you'll get much more meaningful errors before you see the few exceptions to this.
SOAP::WSDL is a sub-class of SOAP::Lite, the module used by the vast majority of perl SOAP clients/services.
-David
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: SOAP and .NET
by Trudge (Acolyte) on Sep 20, 2007 at 13:36 UTC | |
by Trudge (Acolyte) on Sep 20, 2007 at 15:33 UTC | |
by erroneousBollock (Curate) on Sep 20, 2007 at 15:42 UTC | |
by Trudge (Acolyte) on Sep 20, 2007 at 17:17 UTC |