Apologies, I should have said that Royale RemoteObject worked with
ColdFusion in sdk 0.9.0 (not 0.9.3).
I've run out of time right now and won't be back for 2 months, but I'll
get back to you if I can reinstate source locally.
Doug
On 14/06/2022 14:20, Yishay Weiss wrote:
Hi Doug,
I am not familiar with this area of code, but it sounds like you have
an idea for a patch. Can you make this work locally?
*From: *Doug Simmons <mailto:doug777...@gmail.com>
*Sent: *Tuesday, June 14, 2022 4:21 AM
*To: *users@royale.apache.org
*Subject: *Re: RemoteObject cannot work with ColdFusion without source
attribute
Hi Alex,
js:RemoteObject worked flawlessly with ColdFusion in sdk 0.9.3.
I don't know why source was removed before 0.9.9, but surely it's simple
to re-instate it and surround it with
if(destination = 'ColdFusion').
Doug
On 14/06/2022 00:51, Alex Harui wrote:
> Hi Doug,
>
> I might have missed a post, but have you tried Charles or a network
analyzer to compare what Flex sends and receives vs Royale?
> Knowing the difference can help determine next steps.
>
> Thanks,
> -Alex
>
> On 6/13/22, 1:31 AM, "Doug Simmons" <doug777...@gmail.com> wrote:
>
> EXTERNAL: Use caution when clicking on links or opening
attachments.
>
>
> Hi All,
>
> After trying everything I can think of including trying all the
examples
> for js:RemoteObject and mx:RemoteObject, I can only get CF to
respond
> with js:RemoteObject set up normally. Unfortunately it responds -
>
> Exception: flex.messaging.MessageException: Unable to find
source to
> invoke (in the CF log)
>
> If using source is a problem with some messaging services,
can't the
> source be written so that it only has an effect when destination =
> 'ColdFusion'?
>
> Please let me know if source can be returned to the sdk as
otherwise I
> have to give up on Apache Royale,
>
> Thanks,
> Doug
>
