No, my server and ui code are together as a single war file, running from my local on tomcat server.
Alina, Royale example (SampleAmfWebApp) is a spring boot application and ui is using websocket-amf channel. Whereas my use case is traditional web application with ui and server bundled together as single war file and I am using amf channel. Have you used amf channel in your application? Thanks, Sudhakar. -----Original Message----- From: Hugo Ferreira [mailto:[email protected]] Sent: Tuesday, October 06, 2020 4:23 AM To: Apache Royale Development <[email protected]> Subject: Re: RemoteObject error - Invalid Response type Are you running your Royale App from your development environment and your server-side from your production server? If you, you can use a plugin for that. I use this one: Cross Domain - CORS. I tested several and this one works very well. Alina Kazi <[email protected]> escreveu no dia terça, 6/10/2020 à(s) 07:23: > Sudhakar, > > We have used remote object extensively in our application. > > Declaration > <mx:RemoteObject id="roComp" > > endpoint="{parentMxmlDocument.parentMxmlDocument.parentMxmlDocument.Se > rverURL} > destination="dbzCompanySetupBO" /> > > Call > var responderComp1:Responder; > var tokenComp1:AsyncToken; > responderComp1 = new Responder(fn_roCompListRH,fn_HandleFault); > tokenComp1 = roCompList.fn_GetCompListDP(); > tokenComp1.addResponder(responderComp1); > trace(tokenComp1); > I am sending you this with the reference of title of this thread,this > might Help you. All other configuration files are same as they were in Flex. > > Alina Kazi > > On Tue, 6 Oct 2020, 8:11 am Sudhakar Kakaraparthi, < > [email protected]> wrote: > > > Thanks for your inputs, > > > > I still getting same error. Please advise. > > > > Thanks, > > Sudhakar. > > > > -----Original Message----- > > From: Hugo Ferreira [mailto:[email protected]] > > Sent: Monday, October 05, 2020 9:56 PM > > To: Apache Royale Development <[email protected]> > > Subject: Re: RemoteObject error - Invalid Response type > > > > I have cross domain and it's working. > > One main endpoint that tells the client where should look at ! > > So the second endpoint would fail with the typical CORS error. > > > > One this case you need to configure your server side. > > On my case it's a ASP.NET and the only option that worked was to > > configure web.config.\ So theorical this also should work for other > > web server backend as PHP, etc ... > > > > Another important thing with the configuration is that you can > > configure all the possibilities cross domains that you need, > > avoinding this anoying errors but keeping the seurity (the best all worlds). > > If a third party creates a new clone client, will not work in > > production and gets this CORS error. > > > > > > > > Greg Dove <[email protected]> escreveu no dia terça, 6/10/2020 > > à(s) > > 02:34: > > > > > Yes, http and https endpoints should work. > > > > > > I have not tried these with any cross-domain scenario in the past, > > > so there may need to be CORS configuration for javascript (which > > > is different to flash crossdomain.xml permissions model) in that case. > > > > > > > > > > > > On Tue, Oct 6, 2020 at 2:29 PM Sudhakar Kakaraparthi < > > > [email protected]> wrote: > > > > > > > Thanks for the response Greg, > > > > > > > > These configurations are from previous my flex application, let > > > > me try "messagebroker/amf". So amf and secure-amf channels > > > > should be supported > > > by > > > > Royale remote object, correct ? > > > > > > > > Thanks, > > > > Sudhakar. > > > > > > > > -----Original Message----- > > > > From: Greg Dove [mailto:[email protected]] > > > > Sent: Monday, October 05, 2020 9:18 PM > > > > To: Apache Royale Development <[email protected]> > > > > Subject: Re: RemoteObject error - Invalid Response type > > > > > > > > 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. > > > > > > > > > > > > > > > > > --- > > > > 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. > > > --- 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.
