That is interesting. Where did you have the ws component placed originally?

John


-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mike Britton
Sent: Wednesday, May 16, 2007 5:07 PM
To: [email protected]
Subject: Re: [AFFUG Discuss] Strange WebService Behavior

By doing away with the mxml WebService component (doing it in code
instead) and using mx.rpc.soap.mxml.Operation instead of AbstractOperation,
the double-request problem went away.

var ws:WebService = new WebService();
var op:Operation = new Operation();
var args:Object = {
                placeName:request.placeName,
                placeFinderOptions:{
                        dataSource:request.dataSource,
                        filterCountry:request.filterCountry,
                        filterType:request.filterType,
                        resultSetRange:{
                                count:request.count,
                                startIndex:0
                        },
                        searchType:request.searchType
                },
                token:model.sessionModel.token                          
};
ws.wsdl = model.serviceModel.selectedService;
ws.loadWSDL();
ws.useProxy = false;
op = ws['findPlace'];
op.resultFormat = "e4x";
ws.addEventListener("result",onResult);
ws.addEventListener("fault",onFault);
op.arguments = args;
op.send();

Hope this helps someone because it took me nine hours to figure out!


Mike


On 5/16/07, Mike Britton <[EMAIL PROTECTED]> wrote:
> I am -- that's how I know there are two requests going out on the 
> third call.  A stack trace of this error just shows a stream error.
>
> Mike
>
>
> On 5/16/07, John Mason <[EMAIL PROTECTED]> wrote:
> > Trying using Charles or Plastic Sniffer to see the raw webservice
requests.
> >
> > John
> > [EMAIL PROTECTED]
> >
> >
> >
> > -----Original Message-----
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mike 
> > Britton
> > Sent: Wednesday, May 16, 2007 1:41 PM
> > To: [email protected]
> > Subject: [AFFUG Discuss] Strange WebService Behavior
> >
> > All,
> >
> > Has anyone experienced "double request" behavior when calling the 
> > same operation on a WebService component (but with different
parameters)?
> > An app of mine that's using WebService to handle SOAP requests is 
> > exhibiting this behavior and I can't seem to track it down.
> >
> > Thanks in advance if you can help,
> >
> >
> > Mike
> >
> >
> > -------------------------------------------------------------
> > To unsubscribe from this list, simply email the list with 
> > unsubscribe in the subject line
> >
> > For more info, see http://www.affug.com Archive @ 
> > http://www.mail-archive.com/discussion%40affug.com/
> > List hosted by http://www.fusionlink.com
> > -------------------------------------------------------------
> >
> >
> >
> >
> > -------------------------------------------------------------
> > To unsubscribe from this list, simply email the list with 
> > unsubscribe in the subject line
> >
> > For more info, see http://www.affug.com Archive @ 
> > http://www.mail-archive.com/discussion%40affug.com/
> > List hosted by http://www.fusionlink.com
> > -------------------------------------------------------------
> >
> >
> >
>
>
> --
> Mike
> ----------
> http://www.mikebritton.com
> http://www.mikenkim.com
>


--
Mike
----------
http://www.mikebritton.com
http://www.mikenkim.com


-------------------------------------------------------------
To unsubscribe from this list, simply email the list with unsubscribe in the
subject line

For more info, see http://www.affug.com
Archive @ http://www.mail-archive.com/discussion%40affug.com/
List hosted by http://www.fusionlink.com
-------------------------------------------------------------




-------------------------------------------------------------
To unsubscribe from this list, simply email the list with unsubscribe in the 
subject line

For more info, see http://www.affug.com
Archive @ http://www.mail-archive.com/discussion%40affug.com/
List hosted by http://www.fusionlink.com
-------------------------------------------------------------


Reply via email to