Maybe it’s some odd timing problem?  Any profiler settings from Flex 1.5 turned on?  Have you looked to see if you have a flashlog.txt file that has any info in it?  Running in the debugger (even with no breakpoints) would also let you see the output and if there’s anything there.  You’ve built clean I assume.  Delete everything in the bin folder anyway (with FB closed) and see if that changes anything?

 

Sounds strange,

 

Matt

 


From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of ben.clinkinbeard
Sent: Tuesday, August 15, 2006 11:54 AM
To: [email protected]
Subject: [flexcoders] Re: Operation.arguments is populated but nulls are sent

 

OK, the issue seems to be isolated to my machine. The error began
happening again, so I sent a coworker the link to the file on my
machine. He can run the app successfully with no issues whatsoever,
while I still cannot. I have tried clearing my cache, closing Flex
Builder and restarting my machine but nothing seems to help. It seems
like this has to be related to something getting screwed up on my
machine because it also usually goes away by the time I come in the
next day.

Is there anything else I can try clearing or resetting? This has to be
'a bug', no?

Thanks,
Ben

--- In [EMAIL PROTECTED]ups.com, "Matt Chotin" <[EMAIL PROTECTED]> wrote:
>
> You should be calling op.send(), if you call GetDataByGrouping() you're
> ignoring the arguments.
>
>
>
> Matt
>
>
>
> ________________________________
>
> From: [EMAIL PROTECTED]ups.com [mailto:[EMAIL PROTECTED]ups.com] On
> Behalf Of ben.clinkinbeard
> Sent: Monday, August 14, 2006 2:14 PM
> To: [EMAIL PROTECTED]ups.com
> Subject: [flexcoders] Operation.arguments is populated but nulls are
> sent
>
>
>
> I am having a very odd error, and it only happens sometimes. I am
> creating an object structure and then assigning that to the arguments
> property of my mx.rpc.soap.Operation object like this:
>
> op.arguments = args;
>
> I then call the SOAP method like this:
>
> var call:AsyncToken = service.GetDataByGrouping();
> call.addResponder(responder);
>
> Sometimes (I've not figured out a pattern), Flex somehow loses all of
> the contents of the arguments property and sends nulls. It is sending
> the same number of nulls as there were properties though, so I am
> super confused. The Operation.arguments object is still populated with
> the correct data, but none of it gets sent. Does anyone have any idea
> what is going on here? I am pasting the entire method from my delegate
> below.
>
> // in the delegate constructor
> service = ServiceLocator.getInstance().getService("cmws") as WebService;
>
> // in the method called by my command class
> var op:Operation = service.getOperation("GetDataByGrouping") as
> Operation;
> op.resultFormat = "e4x";
> // temp object to store arguments
> var args:Object = new Object();
> args.groupingRequests = new Object();
> args.groupingRequests.GroupName = "RPRTool";
> args.groupingRequests.Parameters = new Array();
> ... populate Parameters array ...
> op.arguments = args;
> var call:AsyncToken = service.GetDataByGrouping();
> call.addResponder(responder);
>
> // results in sendign an object like this
> <ns1:groupingRequests
> xmlns:ns1="http://fmr.com/BackOffice/ClientMeasures
> <http://fmr.com/BackOffice/ClientMeasures> ">
> <ns1:DataGroupingRequest/>
> <ns1:DataGroupingRequest/>
> <ns1:DataGroupingRequest/>
>
> Ben
>

__._,_.___

--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com





YAHOO! GROUPS LINKS




__,_._,___

Reply via email to