I can't really tell for sure what the problem is, but it does look unusual
to have this in your endpoint:
messagebroker/amf.txt

usually that would be:
messagebroker/amf

I have no idea whether that is the issue or not, it just seems unusual to
me.

On Tue, Oct 6, 2020 at 2:11 PM Sudhakar Kakaraparthi <
[email protected]> wrote:

> Looks like there is an issue images, here are the details
>
>
> Thanks a lot for resolving my previous issue with Crux and mx: components.
>
> Now I am getting following error while replacing Flex remote object with
> Royale. Here is my pseudo code,
>
> Remote object definition
> <mx:RemoteObject id="testService" destination="TestController"
> fault="onFault(event)"
>     endpoint="http://localhost:8082/sample-app/messagebroker/amf";
> requestTimeout="240" />
>
>
> Channel definition
> <channel-definition id="my-amf" class="mx.messaging.channels.AMFChannel">
>             <endpoint url="http://{server.name
> }:{server.port}/{context.root}/messagebroker/amf.txt"
>                 class="flex.messaging.endpoints.AMFEndpoint"/>
>         </channel-definition>
>
> Error message
> rootCause:
>                 code: -1004
>                 data: null
>                 detail: "Invalid XMLHttpRequest response status or type."
>                 message: "Invalid response type."
>
>
> As I see all remote object examples are based on websocket-amf, I am not
> sure if Royale remote object supports amf and secure-amf channels. Please
> advise.
>
>
> Thanks,
> Sudhakar.
>
>
> From: Sudhakar Kakaraparthi [mailto:[email protected]]
> Sent: Monday, October 05, 2020 9:04 PM
> To: [email protected]
> Subject: RemoteObject error - Invalid Response type
>
> Thanks a lot for resolving my previous issue with Crux and mx: components.
>
> Now I am getting following error while replacing Flex remote object with
> Royale. Here is my pseudo code,
>
> Remote object definition
> [cid:[email protected]]
>
> Channel definition
> [cid:[email protected]]
>
> Error message
> [cid:[email protected]]
>
> As I see all remote object examples are based on websocket-amf, I am not
> sure if Royale remote object supports amf and secure-amf channels. Please
> advise.
>
>
> Thanks,
> Sudhakar.
>
>
> ---
> This communication may contain confidential and/or privileged information.
> If you are not the intended recipient (or have received this communication
> in error) please notify the sender immediately and destroy this
> communication. Any unauthorized copying, disclosure or distribution of the
> material in this communication is strictly forbidden.
>
> Please refer to https://db.com/disclosures for additional EU corporate
> and regulatory disclosures.
>
> Deutsche Bank does not render legal or tax advice, and the information
> contained in this communication should not be regarded as such.
>
>
> ---
> This communication may contain confidential and/or privileged information.
> If you are not the intended recipient (or have received this communication
> in error) please notify the sender immediately and destroy this
> communication. Any unauthorized copying, disclosure or distribution of the
> material in this communication is strictly forbidden.
>
> Please refer to https://db.com/disclosures for additional EU corporate
> and regulatory disclosures.
>
> Deutsche Bank does not render legal or tax advice, and the information
> contained in this communication should not be regarded as such.
>

Reply via email to