Re: RemoteObject and SimpleRemoteObject not working with WebORB for .NET

Hi Joe, thanks for locate the problem. I think this would be hard for use without having experience/access to a WebOrb and touch here and there trying. I just tried to remove the charset as you suggested and tried with the example and all works ok, so I removed it. Here's the commit: https://git

Re: RemoteObject and SimpleRemoteObject not working with WebORB for .NET

Hello Carlos and Alex. It seems WebORB doesn't like the Content-Type being set as "application/x-amf; charset=UTF-8". It matches up the content-type with internal parsers depending on how you are using it so it's expecting Content-Type "application/x-amf". In the AMFNetConnection.as file xhr.s

Re: RemoteObject and SimpleRemoteObject not working with WebORB for .NET

Hi Joe, I'll leaving for a trip tomorrow and will come in a few days, and as much I'm trying to finish a new jewel component before leaving (If I solve my current problems in time! :)). Please try this weekend to call a simple method sending a String and receiving a server string and report what y

Re: RemoteObject and SimpleRemoteObject not working with WebORB for .NET

ct: Re: RemoteObject and SimpleRemoteObject not working with WebORB for .NET Hi Radu, Althoght we don't have 0.9.3 released you can use nightly build [1]. Probably later you will need MXRoyale branch to go with Emulation path.[2] Alex, Is it even possible sync that branch

Re: RemoteObject and SimpleRemoteObject not working with WebORB for .NET

Hello Carlos. The destinations for WebORB are defined in a different config file. I'll upload that file for you too see. I use the GenericDestination because its a wild card and doesn't require me to specify any namespaces. remoting-config.xml

Re: RemoteObject and SimpleRemoteObject not working with WebORB for .NET

Hi I forgot to mention one more thing about passing a List. In BlazeDS and ColdFusion (for what I know from other users), a server side Collection is passed like an externalized object reference. We solved this for BlazeDS and Coldfusion. I think that should work the same for WebOrb, but since may

Re: RemoteObject and SimpleRemoteObject not working with WebORB for .NET

Jose, based in your info I could make a working example to try. I think code is missing, but I can explain what I see so you can see if you need to fix things in your code or is only information that is missing in your email. Looking to the info you give: 1) The RO configuration is: source = "R

Re: RemoteObject and SimpleRemoteObject not working with WebORB for .NET

Hi Radu, Althoght we don't have 0.9.3 released you can use nightly build [1]. Probably later you will need MXRoyale branch to go with Emulation path.[2] Alex, Is it even possible sync that branch with develop? [1] http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/lastSucces

Re: RemoteObject and SimpleRemoteObject not working with WebORB for .NET

, -Alex From: radu birsan Reply-To: "users@royale.apache.org" Date: Thursday, August 9, 2018 at 10:33 PM To: "users@royale.apache.org" Subject: Re: RemoteObject and SimpleRemoteObject not working with WebORB for .NET Where can we make a donation to help release the official

Re: RemoteObject and SimpleRemoteObject not working with WebORB for .NET

Hi Joe, - correlationId is received from server (talking about BlazeDS always, since don't know about WebOrb), and is a String if small messages are off and a ByteArray if on. - operation is send from client and is 5 (client pong operation) in a normal RO operation (not SimpleRO) to establish conn

Re: RemoteObject and SimpleRemoteObject not working with WebORB for .NET

Where can we make a donation to help release the official Apache 9.3 with AMF support?

Re: RemoteObject and SimpleRemoteObject not working with WebORB for .NET

Hello Carlos and Alex. After digging a bit further i noticed that WebORB is expecting 2 additional properties in the remoting request than what AbstractMessage.as is sending. AbstractMessage.as sends: body clientId destination headers messageId timestamp timeToLive WebORB is expecting... body

Re: RemoteObject and SimpleRemoteObject not working with WebORB for .NET

Hi Carlos. Thank you for the suggestions. I've tried to get this remoting working with all builds available 0.9.2, 0.9.3 and the nightly build at http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/lastSuccessfulBuild/artifact/out/ I tried the MXRoyale branch build bas

Re: RemoteObject and SimpleRemoteObject not working with WebORB for .NET

Hi Alex, ok I'll try it and report my findings. Just one thing from Joe's email: It seems you are trying to use MXRoyale branch? I think that could be a problem. I'm not familiar with that branch but I think is not already synced with develop, so if what I think is real, RO will not work, since no

Re: RemoteObject and SimpleRemoteObject not working with WebORB for .NET

Carlos, Since you've debugged this stuff more recently than me, I will let you debug this too unless you are too busy. Let me know, -Alex On 8/9/18, 11:31 AM, "JoeBoxer" wrote: Hello Alex and Carlos. Thank you for responding to this issue. I tried the nightly build of t

Re: RemoteObject and SimpleRemoteObject not working with WebORB for .NET

Hello Alex and Carlos. Thank you for responding to this issue. I tried the nightly build of the feature/MXRoyale branch and noticed that SimpleRemoteObject wasn't in that build so i used RemoteObject. Unfortunately i had the same problem. I put together a test environment with WebORB at this en

Re: RemoteObject and SimpleRemoteObject not working with WebORB for .NET

Hi, I don't have experience in WebOrb and I suppose Alex is in the same track like me, but we want RO and AMF working for all platforms, so first I want to ask you if you check this: https://github.com/apache/royale-asjs/wiki/Apache-Royale-communication-with-AMF-and-RemoteObject (I suppose you d

Re: RemoteObject and SimpleRemoteObject not working with WebORB for .NET

Are you using the latest nightly build of the feature/MXRoyale branch? If not, get it from http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/Royale-asjs_MXRoyale/lastSuccessfulBuild/artifact/out/ If it still isn't working, can you create a small test case we can debug using that same s