Frankly, using the ServiceLocator in the first place is far from a
best practice. In the past, I've done this to initialize my remote
objects:
var ro:RemoteObject =
RemoteObject(ServiceLocator.getInstance().getRemoteObject("ro"));
ro.endpoint = myEndpoint;
ro.source = mySource;
You can do something similar for your HTTPServices when you know what
properties you want to set on them.
--- In [email protected], "adamratcliffe2002" <a...@...> wrote:
>
> I have an AIR application which uses the Merapi bridge to
communicate with a local Java
> application. My service class wraps the bridge and I would like to
initialize this service
> alongside the HTTPService I have defined in the ServiceLocator mxml.
>
> Should I extend the Cairngorm ServiceLocator to support my own
service interface as an
> additional type or is there some better way of doing this?
>
> Cheers
> Adam
>
