None of that matters since you are clearly getting the values into Flex.
If you have the data in one place("...I can use them as
> on everything else (text etc) ..."), then you need to see why you
don't have the data in another. Again, don't use the declaritive code,
use AS instead, so you can examine the contents of the variables.
Tracy
________________________________
From: [email protected] [mailto:[EMAIL PROTECTED] On
Behalf Of sanyobn2
Sent: Thursday, January 18, 2007 10:43 PM
To: [email protected]
Subject: [flexcoders] Re: Probably dead simple but......
HI,
Cant be done easily, the code loads Session details , then saves them
for repeat each repeat visit, these are allocated in a frame on
another server....
Starting to wish i had stuck with coldfusion and flash forms. Back to
the books.....
--- In [email protected] <mailto:flexcoders%40yahoogroups.com>
, "Tracy Spratt" <[EMAIL PROTECTED]> wrote:
>
> Debug this by breaking the issue into parts. Make sure you have the
> values in the component first. There are several ways to do this, try
a
> few.
>
>
>
> One alternative to the declaritive style is to set the request object
> and invoke send() in AS.
>
>
>
> Tracy
>
>
>
> ________________________________
>
> From: [email protected] <mailto:flexcoders%40yahoogroups.com>
[mailto:[email protected] <mailto:flexcoders%40yahoogroups.com>
] On
> Behalf Of sanyobn2
> Sent: Thursday, January 18, 2007 9:01 AM
> To: [email protected] <mailto:flexcoders%40yahoogroups.com>
> Subject: [flexcoders] Probably dead simple but......
>
>
>
> HI,
>
> Been thrashing about all morning with this.
>
> I cant get two variables that I have passed in as 'flashVars' to act
> as <mx:request> options for accessing a web service, I can use them as
> on everything else (text etc) but when i call the webservice nothing
> is passed. Sure it must be easy but cant see the wood from the trees.
>
> Thanks in advance.
>
> example code -
>
> This returns nothing
> --------------------
>
> <mx:operation name="getUserinfo" resultFormat="e4x">
> <mx:request>
>
<SFSESSION_ID>{Application.application.parameters.SESSION_ID.value}</SFS
> ESSION_ID>
>
<SERVER_URL>{Application.application.parameters.SERVER_URL.value}</SERVE
> R_URL>
> </mx:request>
> </mx:operation>
>
> This returns the session_Id correctly
> -------------------------------------
>
> <mx:Text x="23" y="380"
> text="{Application.application.parameters.SESSION_ID}"/>
>
> They are directly under each other....
>
> Help !!
>
