As suggested, I removed the endpoint property from my mx:RemoteObject
tag, removed the services property from my mxmlc Ant task and did a
clean, build, deploy.
<mx:RemoteObject
id="mService"
destination="MyService"
showBusyCursor="true"
result="event.token.resultHandler( event )"
fault="event.token.faultHandler( event )"
requestTimeout="30" />
Now when I run the app I get a "Destination 'MyService' has no
channels defined and the application does not define any default
channels."
Any thoughts?
Cheers,
Lawrie
--- In [email protected], "Peter Farland" <[EMAIL PROTECTED]> wrote:
>
> For the MXML RemoteObject API, it's true there is an endpoint property
> and what steve writes about it automatically selecting the right channel
> based on HTTP(S) URLs is correct, but it is not marked bindable and I've
> not seen it used with MXML binding statements. So, I am suggesting that
> while you're trying to get this to work - just use the programmatic
> approach you're using with ChannelSet exclusively for now.
>
> Pete
>
> -----Original Message-----
> From: [email protected] [mailto:[EMAIL PROTECTED] On
> Behalf Of lawriegallardo
> Sent: Monday, November 19, 2007 1:52 PM
> To: [email protected]
> Subject: [flexcoders] Re: Confused by context.root, services-config.xml
> and remoting-config.xml...
>
> 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"
> <steve.allison@> 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
> >
>
>
>
>
> --
> 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
>
