Hmm.... is there any useful information being sent into the demoFailure callback? I think its supposed to get an errror as a parameter. Something like: function demoFailure(error) { alert('error ' + error); }
Barring that, I would check two things: 1) check the server logs (if you have access) for any faults or other stack traces. 2) use wireshark or other TCP trace utility to see the raw transfers to see if the returning soap message looks correct. Dan On Tuesday 22 April 2008, Tim Perrett wrote: > Ok, just realized that its all mapped back onto the SoapType object > through prototype classes. > > x = new > webservices_daelab_net_temperature_TemperatureConversionsSoapType(); > x.FahrenheitToCelcius(demoSucsess, demoFailure, 45); > > It appears that the failure callback is being invoked - any ideas how > I can see what is going on and causing that error? > > Cheers > > Tim > > On 22 Apr 2008, at 09:49, Tim Perrett wrote: > > Otherwise, the output form wsdl2js, uses CxfApacheOrgClient > > prototype, which I found in $CXF_HOME/etc/cxf-utils.js - however, so > > now I get the error: > > > > utils has no properties > > CxfApacheOrgClient(undefined)file:localhost/Us... (line 513) > > webservices_daelab_net_temperature_CelciusToFahrenheit_op > > (demoSucsess(), demoFailure(), 36)file:localhost/Us... (line 981) > > [Break on this error] utils.trace("Client constructor"); > > > > Any ideas how to get around this? -- J. Daniel Kulp Principal Engineer, IONA [EMAIL PROTECTED] http://www.dankulp.com/blog