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 did it) and let us know if weborb has some configuration for serialization and small messages like in BlazeDS. If so, you need to turn off small messages since we don't have support yet for that, but is not critical and is just a server optimization over normal AMF. Small Messages in BlazeDS makes heaving use of IExternalizable to reduce size of messages, but turning off fall back to a normal AMF communication. In the other hand RO is aware of clientId while SimpleRO is not. I suppose you'll need RO to let WebOrb knows which client is sending the request and maintain communication. Another thing you could do is send your test code so we can take a look, and in your side use some tool like Charles (https://www.charlesproxy.com) to see what you'r sending and what you're receiving. And compare with your Flex App to see differences. 2018-08-09 2:34 GMT+02:00 Alex Harui <[email protected]>: > 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 server? > > Thanks, > -Alex > > On 8/8/18, 4:50 PM, "JoeBoxer" <[email protected]> wrote: > > Hello. > > We are in the process of migrating to Royale and our current Flex/Flash > application relies heavily on WebORB for remoting. Unfortunately, we > are > having issues getting the Royale amf/remoting to work. Performing a > simple > amf request using RemoteObject or SimpleRemoteObject results in: > > Chrome console output: > > destination fault handler > {code: -1005, message: "Invalid response.", detail: "", data: null} > > AND > > The server-side WebORB log shows: > > [Thread-24] WEBORB INFO:8/8/2018 1:33:27 PM:Received request for > http://[weborb service]/remoting.aspx from [myIP] > [Thread-24] WEBORB INFO:8/8/2018 1:33:27 PM:Request is in session > vtvglifchdfomrb2ym5xtr55 > [Thread-24] WEBORB EXCEPTION:8/8/2018 1:33:27 PM:cannot parse request. > possible reasons: malformed request or protocol formatter is not > registered > : at Weborb.Protocols.ProtocolRegistry.BuildMessage(String > contentType, > Stream requestStream, NameValueCollection headers) > at Weborb.ORBHttpHandler.a(HttpContext A_0, HttpRequest A_1, > HttpResponse > A_2) > > If anyone has any ideas or suggestions on how to trouble-shoot this it > would > be greatly appreciated. > In addition if further information is needed please don't hesitate to > comment and I'll do my best to track it down. > > Thanx in advance. > Regards, > Joe > > > > -- > Sent from: https://na01.safelinks.protection.outlook.com/?url= > http%3A%2F%2Fapache-royale-users.20374.n8.nabble.com%2F& > amp;data=02%7C01%7Caharui%40adobe.com%7C5ad5877e0a804bf9518208d5fd89b848% > 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636693690326905523& > sdata=%2BGe4Jf9Ua05%2Bt2hq7A%2Bn6925eOsXXZDUaAgc40tzpy4%3D&reserved=0 > > > -- Carlos Rovira http://about.me/carlosrovira
