Thanks Bob... that's a very helpful tag that I didn't know about. 

The trace shows I'm getting as far as "encoding soap request body" 
before the error crops up - seems to suggest something wrong with my 
input args?? 

--- In [email protected], "bobignacio" <[EMAIL PROTECTED]> 
wrote:
>
> Set the following on the line right after the "<mx:Application" tag
> near the top:
> 
>  <mx:TraceTarget />
> 
> Run your application in debug mode. This will allow you to see all 
the
> network traffic going across the wire. See if you actually get a
> response from the NDFD web service.
> 
> Hope this helps,
> 
> Bob I.
> 
> 
> --- In [email protected], "jaywood58" <jaywood@> wrote:
> >
> > 
> > I am having a problem getting data from the National Weather 
Service's
> > "National Digital Forecast Database"  XML Web Service...
> > http://www.weather.gov/xml/ <http://www.weather.gov/xml/> .  I',m 
using
> > Flex Builder 2.0.1.
> > 
> > The service provides 9 functions for accessing the NWS' vast 
database of
> > weather forecasts and statistics. I am able to use the simplest 
one,
> > "latLonByZipCode" with no trouble... I pass it a valid US 
zipcode, it
> > returns a string containing the corresponding latitude and 
longitude.  I
> > pass it a bad zipcode, it returns a nice, informative error 
message.
> > 
> > When I try one of the other functions (NDFDgenByDay), I keep 
getting the
> > following: "TypeError: Error #1009: Cannot access a property or 
method
> > of a null object reference", triggered by the webservice call.  
The
> > errorID i s 0, the fault code is "Encoding Error", and the 
message is
> > null.
> > 
> > The only difference I can see between these 2 function calls is 
the list
> > of input parameters -- latLonByZipCode (the one that's working) 
takes a
> > single string argument;  NDFDgenByDay takes a mix of decimal, 
date,
> > integer, and string arguments.  Could an ill-formed argument list 
cause
> > this error? (and if so, what do I need to do to fix it). Any help 
would
> > be greatly appreciated!
> >
>


Reply via email to