No, we're not at crossed purposes at all - that's really useful thanks! Do I still need to worry about the services-config.xml and remote-config.xml files? If not, how do the destinations and their properties (i.e. the source property that specifies which Java service gets called) get set up?
Cheers, Lawrie --- In [email protected], "Stephen Allison" <[EMAIL PROTECTED]> wrote: > > > Thanks for your help - Apologies if I'm being a bit thick , but I'm a > > not quite sure what you mean when you say that you "set the endpoint > > property of the RemoteObject to point at whatever AMF endpoint url you > > want". Could you clarify this a bit, please? > > Hi, > RemoteObject defines an endpoint property which allows you to > programatically set the AMF endpoint used by that instance. So: > > var ro:RemoteObject = new RemoteObject(...); > ro.endpoint = Application.application.parameters["gatewayUrl"] > > and you're ready to go, the RemoteObject will use either a secure AMF > channel or a regular AMF channel depending on whether or not the url you > provide it is https or not. > > You can probably (and I've not checked) set it in mxml using data binding: > <mx:RemoteObject ... > endpoint={Application.application.parameters['gatewayUrl']} ...> > > or somesuch. We set gatewayUrl from FlashVars in the containing ASP page, > so the server decides which endpoint a given application talks to. > > Apologies if we're at crossed purposes here! > > Stephen >
