February 04, 2009 6:33 PM
> To: flexcoders@yahoogroups.com
> Subject: [flexcoders] Re: Passing values using mx:WebService
>
>
>
> FYI ws call
>
> private function button_click():void {
> var wsOperation:Operation = ws.Assess;
> wsOperation.resultFormat = "e4x"
Flex development bandwidth available
From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On
Behalf Of m_ollman
Sent: Wednesday, February 04, 2009 6:33 PM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Re: Passing values using mx:WebService
FYI ws call
private function button_click():void {
var wsOperation:Operation = ws.Assess;
wsOperation.resultFormat = "e4x";
var atCall:AsyncToken;
var sQ2:String = Q2.selectedItem.data;
Great advice and thanks for your comments valdhor & tracey.
I have re-coded the ws call in AS - and am running into the "Error
parsing request: Unexpected end element assess-request"
(code @ EOM)
I figure that means that this call has the Unexpected end element in it:
var oRequest:Object = {Q2
Great advice and thanks for your comments valdhor & tracey.
I have re-coded the ws call in AS - and am running into the "Error
parsing request: Unexpected end element assess-request"
I figure that means that this is braking it:
var oRequest:Object = {Q2: sQ2, Q5: sQ5};
values are tracing ok
I have to agree with Tracy - data service calls can be very tricky
with mxml; I'd rather use AS.
This thread may give you some pointers:
http://tech.groups.yahoo.com/group/flexcoders/message/134966
--- In flexcoders@yahoogroups.com, "Tracy Spratt" wrote:
>
> I like mxml for a lot of things, bu
6 matches
Mail list logo
