For your channel definition instead of using a relative URL for an
endpoint...
<endpoint
uri="http://{server.name}:{server.port}/{context.root}/blazeds/amf";
class="flex.messaging.endpoints.AMFEndpoint"
/>
use a specific one...
<endpoint
uri="http://someother
server.com:8080/otherapp/blazeds/amf"
class="flex.messaging.endpoints.AMFEndpoint"
/>
At least this is what I do with Granite DS which I assume should work
the same.
- Todd
--- In [email protected], Mark Lapasa <[EMAIL PROTECTED]> wrote:
>
> Suppose the blaze server does have a crossdomain.xml.
>
> How can I point remote object to hit the blaze server at all? From
what I've read so far, the .swf is usually hosted on the same server
as the remoting server.
>
> -mL
>
>
> On Thursday 27 Mar 2008, Mark Lapasa wrote:
>
> > > The reason for this arrangement is that the place where the .swf is
> > > hosted not available to install BlazeDS.
> > > Haven't been able to find out in the documentation how to
redirect the
> > > remote object to a different URL.
> >
>
> I think you'll just need a suitable crossdomain.xml on the blaze server.
>
> -- Tom Chiverton Helping to confidentially transform dot-com features
> on: http://thefalken.livejournal.com
> > On one domain, the .swf is hosted On another domain, resides Blaze DS
> > server. User accesses the .swf from the first one so it can take
> > advantage of remoting on the other. The reason for this
arrangement is
> > that the place where the .swf is hosted not available to install
> > BlazeDS. Haven't been able to find out in the documentation how to
> > redirect the remote object to a different URL. Help anyone? Thx, -mL
>
>
>
> Notice of confidentiality:
> The information contained in this e-mail is intended only for the
use of the individual or entity named above and may be confidential.
Should the reader of this message not be the intended recipient, you
are hereby notified that any unauthorized dissemination, distribution
or reproduction of this message is strictly prohibited. If you have
received this message in error, please advise the sender immediately
and destroy the e-mail.
>
