RemoteObject and SimpleRemoteObject not working with WebORB for .NET

classic Classic list List threaded Threaded
19 messages Options
Reply | Threaded
Open this post in threaded view
|

RemoteObject and SimpleRemoteObject not working with WebORB for .NET

JoeBoxer
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: http://apache-royale-users.20374.n8.nabble.com/
Reply | Threaded
Open this post in threaded view
|

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

Alex Harui-2
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" <[hidden email]> 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&amp;sdata=%2BGe4Jf9Ua05%2Bt2hq7A%2Bn6925eOsXXZDUaAgc40tzpy4%3D&amp;reserved=0
   

Reply | Threaded
Open this post in threaded view
|

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

Carlos Rovira-2
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:


(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 <[hidden email]>:
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" <[hidden email]> 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&amp;sdata=%2BGe4Jf9Ua05%2Bt2hq7A%2Bn6925eOsXXZDUaAgc40tzpy4%3D&amp;reserved=0





--
Reply | Threaded
Open this post in threaded view
|

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

JoeBoxer
This post was updated on .
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 endpoint:
http://66.155.36.74/remoting.aspx
I also made an Adobe AIR app with a successful remoting call to a country
list.  I'll paste the AIR code below and attach the air app as well.  I'm
not sure i have control of small messages so ill upload the WebORB config
file that I have the ability to modify on the server.

<?xml version="1.0" encoding="utf-8"?>
<s:WindowedApplication xmlns:fx="http://ns.adobe.com/mxml/2009" 
                                           xmlns:s="library://ns.adobe.com/flex/spark"
                                           xmlns:mx="library://ns.adobe.com/flex/mx"
                                           showStatusBar="false"
                                           title="Remoting Test">
        <fx:Script>
                        import mx.collections.ArrayList;
                        import mx.rpc.events.FaultEvent;
                        import mx.rpc.events.ResultEvent;
                        import mx.rpc.remoting.RemoteObject;
                       
                        [Bindable]
                        private var _remotingList:ArrayList;
               
                        private function testHandler(event:MouseEvent):void
                        {
                                var remoting:RemoteObject;
                                remoting = new RemoteObject("GenericDestination");
                                remoting.endpoint = "http://66.155.36.74/remoting.aspx";
                                remoting.source = "Remoting.Service.Components.RemotingTest";
                                remoting.addEventListener(ResultEvent.RESULT,onResult);
                                remoting.addEventListener(FaultEvent.FAULT,onError);
                               
                                remoting.GetCountryList();
                        }
                       
                        private function onResult(event:ResultEvent):void
                        {
                                if (event.result != null) {
                                        _remotingList = new ArrayList(event.result as Array);
                                }
                        }
                       
                        private function onError(event:FaultEvent):void
                        {
                        }
        </fx:Script>
        <s:VGroup width="100%" height="100%">
                <s:Button id="testRemoting_btn" label="Test Remoting" click="testHandler(event)"/>
                <s:List id="remoting_lst" width="100%" height="100%" dataProvider="{_remotingList}"/>
        </s:VGroup>       
</s:WindowedApplication>

----------- Royale Code ------------

<?xml version="1.0" encoding="utf-8"?>
<js:Application xmlns:fx="http://ns.adobe.com/mxml/2009" 
                            xmlns:js="library://ns.apache.org/royale/express"
                                xmlns:j="library://ns.apache.org/royale/basic">
         <fx:Script>
                        import org.apache.royale.net.events.FaultEvent;
                        import org.apache.royale.net.events.ResultEvent;

                        private function onResult(evt:ResultEvent):void
                        {
                                trace("Result");
                        }

                        private function onFault(evt:FaultEvent):void
                        {
                                trace("Fault = " + evt.message);
                        }

                        protected function initRemoting():void
                        {
                                 remotingService.send("GetCountryList",[]);
                        }
        </fx:Script>

        <js:beads>
                        <j:ClassAliasBead />
                 <j:RemoteObject id="remotingService" result="onResult(event)" fault="onFault(event)"
                             endPoint = "http://66.155.36.74/remoting.aspx"
                             source = "Remoting.Service.Components.RemotingTest"
                             destination = "GenericDestination"/>
        </js:beads> 
        <js:initialView>
                <js:View>
                        <js:TextButton text="Get Data" width="200" height="200" click="initRemoting()"/>
                </js:View>
        </js:initialView>

</js:Application>


Main.air <http://apache-royale-users.20374.n8.nabble.com/file/t53/Main.air
weborb.config <http://apache-royale-users.20374.n8.nabble.com/file/t53/weborb.config


--
Sent from: http://apache-royale-users.20374.n8.nabble.com/
Reply | Threaded
Open this post in threaded view
|

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

Alex Harui-2
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" <[hidden email]> wrote:

    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 endpoint:
    https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2F66.155.36.74%2Fremoting.aspx&amp;data=02%7C01%7Caharui%40adobe.com%7Cef8bc5008aad4708502208d5fe265021%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636694362868057831&amp;sdata=4riHOJeYYttb5opEmDxZi2S40P8cChWLr4OynnKuHBM%3D&amp;reserved=0
    I also made an Adobe AIR app with a successful remoting call to a country
    list.  I'll paste the AIR code below and attach the air app as well.  I'm
    not sure i have control of small messages so ill upload the WebORB config
    file that I have the ability to modify on the server.
   
    <?xml version="1.0" encoding="utf-8"?>
    <s:WindowedApplication xmlns:fx="https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009&amp;data=02%7C01%7Caharui%40adobe.com%7Cef8bc5008aad4708502208d5fe265021%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636694362868057831&amp;sdata=Vldme%2BmQ08UQUlI765L0jJ7GJSrGknp2GFPGHiVd%2BNQ%3D&amp;reserved=0"
      xmlns:s="library://ns.adobe.com/flex/spark"
      xmlns:mx="library://ns.adobe.com/flex/mx"
      showStatusBar="false"
      title="Remoting Test">
    <fx:Script>
   
    </fx:Script>
    <s:VGroup width="100%" height="100%">
    <s:Button id="testRemoting_btn" label="Test Remoting"
    click="testHandler(event)"/>
    <s:List id="remoting_lst" width="100%" height="100%"
    dataProvider="{_remotingList}"/>
    </s:VGroup>
    </s:WindowedApplication>
   
    ----------- Royale Code ------------
   
    <?xml version="1.0" encoding="utf-8"?>
    <js:Application xmlns:fx="https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009&amp;data=02%7C01%7Caharui%40adobe.com%7Cef8bc5008aad4708502208d5fe265021%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636694362868057831&amp;sdata=Vldme%2BmQ08UQUlI765L0jJ7GJSrGknp2GFPGHiVd%2BNQ%3D&amp;reserved=0"
      xmlns:js="library://ns.apache.org/royale/express"
    xmlns:j="library://ns.apache.org/royale/basic">
    <fx:Script>
   
    </fx:Script>
   
    <js:beads>
    <j:ClassAliasBead />
    <j:RemoteObject id="remotingService" result="onResult(event)"
    fault="onFault(event)"
                             endPoint = "https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2F66.155.36.74%2Fremoting.aspx&amp;data=02%7C01%7Caharui%40adobe.com%7Cef8bc5008aad4708502208d5fe265021%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636694362868057831&amp;sdata=4riHOJeYYttb5opEmDxZi2S40P8cChWLr4OynnKuHBM%3D&amp;reserved=0"
    source = "Remoting.Service.Components.RemotingTest"
                             destination = "GenericDestination"/>
        </js:beads>
    Main.air <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-users.20374.n8.nabble.com%2Ffile%2Ft53%2FMain.air&amp;data=02%7C01%7Caharui%40adobe.com%7Cef8bc5008aad4708502208d5fe265021%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636694362868057831&amp;sdata=2doCLN2GBg0tm9sTxSos1qwrV3tEt9W6XU2pxYMKnQI%3D&amp;reserved=0>  
    weborb.config
    <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-users.20374.n8.nabble.com%2Ffile%2Ft53%2Fweborb.config&amp;data=02%7C01%7Caharui%40adobe.com%7Cef8bc5008aad4708502208d5fe265021%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636694362868057831&amp;sdata=yDwquYgko07Hbes%2FukKwY9%2BAN6SQZXJ0yniBCTfjffE%3D&amp;reserved=0>  
    <js:initialView>
    <js:View>
    <js:TextButton text="Get Data" width="200" height="200"
    click="initRemoting()"/>
    </js:View>
    </js:initialView>
   
    </js:Application>
   
   
   
    --
    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%7Cef8bc5008aad4708502208d5fe265021%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636694362868057831&amp;sdata=WxOI6rdtOK96MExgvQZssmH9O4iTglZ4Hm1qG%2F9bckg%3D&amp;reserved=0
   

Reply | Threaded
Open this post in threaded view
|

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

Carlos Rovira-2
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 not all the working code is synced in that branch and for that reason you can't find SimpleRO in that branch. I think Alex did a cheery pic of jus one commit.

So before I do something I want you to test the following:

1.- Check develop branch
2.- build the three repos in the order: compiler, typedefs, asjs. I assume you're building with Maven, since I'm not sure if ANT build can have some issue, since I don't have ANT in my system
3.- taking into account this link [1] and since in step 2 you build projects and examples you can go to the SampleAmfWebApp  Java example folder and inside run "java -jar target/SampleAmfWebApp-0.9.3-SNAPSHOT-exec.war" (you should have Java 8, since other java versions will give you errors)
4.- go to a browsers and try http://localhost:8080 and see if all is working fine (check AMF samples are working for you)

From that "safe" point we go to your project (I Think is better to go from safe points and progress from that):

5.- Use RemoteObjectAMFTest   as a sample project and modify with your test server settings

For example take the 

<js:RemoteObject id="service" result="onResult(event)" fault="onFault(event)"
destination = "exampleService"/>

and change endPoint to http://66.155.36.74/remoting.aspx

and so on...

If you don't get it working I'll need you post here the code you tried and no works and I'll try to get it working.

From that point, since the project is a Jewel Example and for what I understand you want to try MXRoyale, we'll need Alex's help to see what problems could be. I think it could be just a matter of sync MXRoyale with develop and fix possible problems at that time.

Please let me know if that plan is right for you.

Thanks





2018-08-09 20:46 GMT+02:00 Alex Harui <[hidden email]>:
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" <[hidden email]> wrote:

    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 endpoint:
    https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2F66.155.36.74%2Fremoting.aspx&amp;data=02%7C01%7Caharui%40adobe.com%7Cef8bc5008aad4708502208d5fe265021%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636694362868057831&amp;sdata=4riHOJeYYttb5opEmDxZi2S40P8cChWLr4OynnKuHBM%3D&amp;reserved=0
    I also made an Adobe AIR app with a successful remoting call to a country
    list.  I'll paste the AIR code below and attach the air app as well.  I'm
    not sure i have control of small messages so ill upload the WebORB config
    file that I have the ability to modify on the server.

    <?xml version="1.0" encoding="utf-8"?>
    <s:WindowedApplication xmlns:fx="https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009&amp;data=02%7C01%7Caharui%40adobe.com%7Cef8bc5008aad4708502208d5fe265021%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636694362868057831&amp;sdata=Vldme%2BmQ08UQUlI765L0jJ7GJSrGknp2GFPGHiVd%2BNQ%3D&amp;reserved=0"
                                           xmlns:s="library://ns.adobe.com/flex/spark"
                                           xmlns:mx="library://ns.adobe.com/flex/mx"
                                           showStatusBar="false"
                                           title="Remoting Test">
        <fx:Script>

        </fx:Script>
        <s:VGroup width="100%" height="100%">
                <s:Button id="testRemoting_btn" label="Test Remoting"
    click="testHandler(event)"/>
                <s:List id="remoting_lst" width="100%" height="100%"
    dataProvider="{_remotingList}"/>
        </s:VGroup>     
    </s:WindowedApplication>

    ----------- Royale Code ------------

    <?xml version="1.0" encoding="utf-8"?>
    <js:Application xmlns:fx="https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009&amp;data=02%7C01%7Caharui%40adobe.com%7Cef8bc5008aad4708502208d5fe265021%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636694362868057831&amp;sdata=Vldme%2BmQ08UQUlI765L0jJ7GJSrGknp2GFPGHiVd%2BNQ%3D&amp;reserved=0"
                                xmlns:js="library://ns.apache.org/royale/express"
                                xmlns:j="library://ns.apache.org/royale/basic">
         <fx:Script>

        </fx:Script>

        <js:beads>
                <j:ClassAliasBead />
                <j:RemoteObject id="remotingService" result="onResult(event)"
    fault="onFault(event)"
                             endPoint = "https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2F66.155.36.74%2Fremoting.aspx&amp;data=02%7C01%7Caharui%40adobe.com%7Cef8bc5008aad4708502208d5fe265021%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636694362868057831&amp;sdata=4riHOJeYYttb5opEmDxZi2S40P8cChWLr4OynnKuHBM%3D&amp;reserved=0"
                                                 source = "Remoting.Service.Components.RemotingTest"
                             destination = "GenericDestination"/>
        </js:beads>
    Main.air <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-users.20374.n8.nabble.com%2Ffile%2Ft53%2FMain.air&amp;data=02%7C01%7Caharui%40adobe.com%7Cef8bc5008aad4708502208d5fe265021%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636694362868057831&amp;sdata=2doCLN2GBg0tm9sTxSos1qwrV3tEt9W6XU2pxYMKnQI%3D&amp;reserved=0
    weborb.config
    <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-users.20374.n8.nabble.com%2Ffile%2Ft53%2Fweborb.config&amp;data=02%7C01%7Caharui%40adobe.com%7Cef8bc5008aad4708502208d5fe265021%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636694362868057831&amp;sdata=yDwquYgko07Hbes%2FukKwY9%2BAN6SQZXJ0yniBCTfjffE%3D&amp;reserved=0
        <js:initialView>
                <js:View>
                        <js:TextButton text="Get Data" width="200" height="200"
    click="initRemoting()"/>
                </js:View>
        </js:initialView>

    </js:Application>



    --
    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%7Cef8bc5008aad4708502208d5fe265021%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636694362868057831&amp;sdata=WxOI6rdtOK96MExgvQZssmH9O4iTglZ4Hm1qG%2F9bckg%3D&amp;reserved=0





--
Reply | Threaded
Open this post in threaded view
|

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

JoeBoxer
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 based on Alex's suggestions.

I haven't had much luck getting the developer branch built with ant or
maven.  Plus I'm getting pom.xml errors when trying to build
RemoteObjectAMFTest... looks like i need 0.9.3-SNAPSHOT build.

The Royale remoting code i posted above is pretty basic and should result in
WebORB taking the request... based on the logs the exception being thrown
is:

WEBORB EXCEPTION:8/9/2018 5:15:56 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)

Now if i make a request with my remoting AIR app I get a successful request
and this is the result in the logs:

[Thread-20] WEBORB INFO:8/9/2018 5:39:23 PM:Received request for
http://66.155.36.74/remoting.aspx from 67.193.118.172
[Thread-20] WEBORB INFO:8/9/2018 5:39:23 PM:Request is in session
2uzzenac0fgkcr45eyvj30bo
[Thread-20] WEBORB DEBUG:8/9/2018 5:39:23 PM:MessageReader:: parsing stream
[Thread-20] WEBORB DEBUG:8/9/2018 5:39:23 PM:MessageReader:: parsing message
- version: 3 totalHeaders: 0
[Thread-20] WEBORB DEBUG:8/9/2018 5:39:23 PM:MessageReader:: Total body
parts: 1
[Thread-20] WEBORB DEBUG:8/9/2018 5:39:23 PM:MessageReader::readBodyPart:
serviceURI - null responseURI - /1 length: 224
[Thread-20] WEBORB DEBUG:8/9/2018 5:39:23 PM:reading object property
operation
[Thread-20] WEBORB DEBUG:8/9/2018 5:39:23 PM:reading object property
correlationId
[Thread-20] WEBORB DEBUG:8/9/2018 5:39:23 PM:reading object property
destination
[Thread-20] WEBORB DEBUG:8/9/2018 5:39:23 PM:reading object property
timestamp
[Thread-20] WEBORB DEBUG:8/9/2018 5:39:23 PM:reading object property
clientId
[Thread-20] WEBORB DEBUG:8/9/2018 5:39:23 PM:reading object property
timeToLive
[Thread-20] WEBORB DEBUG:8/9/2018 5:39:23 PM:reading object property headers
[Thread-20] WEBORB DEBUG:8/9/2018 5:39:23 PM:reading object property body
[Thread-20] WEBORB DEBUG:8/9/2018 5:39:23 PM:reading object property
messageId
[Thread-20] WEBORB DEBUG:8/9/2018 5:39:23 PM:MessageReader:: returning
AMFMessage

If you need more information... Logs, etc.  please don't hesitate to ask.

Thanx so much again
Regards





--
Sent from: http://apache-royale-users.20374.n8.nabble.com/
Reply | Threaded
Open this post in threaded view
|

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

JoeBoxer
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
clientId
destination
headers
messageId
timestamp
timeToLive

AND

operation
correlationId

This could be why the WebORB parser is throwing an exception.  Your
thoughts?

Regards



--
Sent from: http://apache-royale-users.20374.n8.nabble.com/
Reply | Threaded
Open this post in threaded view
|

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

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

Reply | Threaded
Open this post in threaded view
|

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

Carlos Rovira-2
In reply to this post by JoeBoxer
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 connection with BlazeDS, then "operation" is the name of the method your are asking for.
In SimpleRO instead of 5 is 13 (trigger connect operation) for the first connection.

So my guess is that something is wrong in your code

I'll respond to the other email now



2018-08-10 1:19 GMT+02:00 JoeBoxer <[hidden email]>:
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
clientId
destination
headers
messageId
timestamp
timeToLive

AND

operation
correlationId

This could be why the WebORB parser is throwing an exception.  Your
thoughts?



--
Reply | Threaded
Open this post in threaded view
|

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

Alex Harui-2
In reply to this post by radu

Hi Radu,

 

Thanks for your offer.  I don’t think there is a central place to accept monetary donations for Apache Royale.  Donating to the Apache Software Foundation is always a nice thing to do, but it won’t directly accelerate development.

 

There may be a few committers with spare time who would be encouraged to spend more time on Royale if they could get paid for it.  That’s one way to help.  Another is for you to donate your time instead of money.  Learn how to fix bugs and develop new features in Royale.  We could always use more folks contributing code, tests, doc, etc.

 

Thanks,

-Alex

 

From: radu birsan <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Thursday, August 9, 2018 at 10:33 PM
To: "[hidden email]" <[hidden email]>
Subject: 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? 

Reply | Threaded
Open this post in threaded view
|

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

Piotr Zarzycki
In reply to this post by Carlos Rovira-2
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?


Thanks,
Piotr

On Fri, Aug 10, 2018, 9:15 AM Carlos Rovira <[hidden email]> wrote:
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 connection with BlazeDS, then "operation" is the name of the method your are asking for.
In SimpleRO instead of 5 is 13 (trigger connect operation) for the first connection.

So my guess is that something is wrong in your code

I'll respond to the other email now



2018-08-10 1:19 GMT+02:00 JoeBoxer <[hidden email]>:
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
clientId
destination
headers
messageId
timestamp
timeToLive

AND

operation
correlationId

This could be why the WebORB parser is throwing an exception.  Your
thoughts?



--
Reply | Threaded
Open this post in threaded view
|

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

Carlos Rovira-2
In reply to this post by Carlos Rovira-2
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 = "Remoting.Service.Components.RemotingTest"
 destination = "GenericDestination

source is a deprecated property left in RO for backwards compatibility, since it expose the path to the server object. It's not needed anymore. Again talking about BlazeDS. Only destination should be required along "endPoint". If I search for "GenericDestination" in the config file you posted I don't find it. The same happens for "Remoting.Service.Components.RemotingTest". IMHO the .Net class should be exposed in the weborb config file like this one:

<service>
<name>ExamplesActivationSession</name>
<serviceId>Weborb.Examples.ShoppingCart</serviceId>
</service>

to have something like:

<service>
<name>RemotingTest</name>
<serviceId>Remoting.Service.Components.RemotingTest</serviceId>
</service>


In our example in BlazeDS we don't do this in config file since we have a Spring annotation in code. Example:

@Service("exampleService")
@RemotingDestination
public class ExampleService {

just guessing and trying to match what I know from BlazeDS and what I see in your WebOrb config file

Then remove "source" property from the Royale RO declaration

Now going to the calling code: I don't see nothing of that in your sample code. It seems the button calls "initRemoting" but where's the code?

The code should be something like:

protected function sendName():void
            {
service.send("XXX", []);
            }

Where XXX is the name of the method in the .Net class Remoting.Service.Components.RemotingTest
second param is the array of params to send to that method. I understand in this case we don't send anything

Then managing the result, I don't see again any callback code. But lets imagine s something like this:

private function onResult(evt:ResultEvent):void
            {
                trace("[Client:" + RoyaleClient.getInstance().id + "] Result= " + evt.data);

var arr:ArrayList = new ArrayList(evt.data as Array);
list.dataProvider = arr;
                
            }

If you run in debug mode (js-debug) in your browser (and here is important that you left your browser communication within local and external sources since that security restriction will make this communication not work)
you should see a trace with the "clientId" and the data from server. clientId will then be shared in each transaction with the server

then since we are receiving a list of countries for what I understand, you should get an Array (maybe for the first connection you should start with only a String, instead this structure since is more complex)

For the Array, one important thing is to know if each object in the array are plain Objects or TypedObjects and if the later, you'll need something like the following example in the Class:

[RemoteClass(alias="org.apache.royale.amfsamples.valueobjects.Product")]
    public class Product
    {

Maybe in WebOrb is needed as well some config, on this point.

My suggestion is that instead of try for the first time to exchange a list, you'll try to send a simple string and send back another string from WebOrb method. That will make a safe point from wich you can evolve to something more complicated. Then try a Typed object, and then try a List of typed objects.





2018-08-10 9:15 GMT+02:00 Carlos Rovira <[hidden email]>:
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 connection with BlazeDS, then "operation" is the name of the method your are asking for.
In SimpleRO instead of 5 is 13 (trigger connect operation) for the first connection.

So my guess is that something is wrong in your code

I'll respond to the other email now



2018-08-10 1:19 GMT+02:00 JoeBoxer <[hidden email]>:
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
clientId
destination
headers
messageId
timestamp
timeToLive

AND

operation
correlationId

This could be why the WebORB parser is throwing an exception.  Your
thoughts?



--



--

Carlos Rovira

Director General

M: +34 607 22 60 05

http://www.codeoscopic.com


Conócenos en 1 minuto!


AVISO LEGAL: La información contenida en este correo electrónico, y en su caso en los documentos adjuntos, es información privilegiada para uso exclusivo de la persona y/o personas a las que va dirigido. No está permitido el acceso a este mensaje a cualquier otra persona distinta a los indicados. Si Usted no es uno de los destinatarios, cualquier duplicación, reproducción, distribución, así como cualquier uso de la información contenida en él o cualquiera otra acción u omisión tomada en relación con el mismo, está prohibida y puede ser ilegal. En dicho caso, por favor, notifíquelo al remitente y proceda a la eliminación de este correo electrónico, así como de sus adjuntos si los hubiere. En cumplimiento de la legislación española vigente en materia de protección de datos de carácter personal y del RGPD 679/2016 le informamos que sus datos están siendo objeto de tratamiento por parte de CODEOSCOPIC S.A. con CIFA85677342, con la finalidad del mantenimiento y gestión de relaciones comerciales y administrativas. La base jurídica del tratamiento es el interés legítimo de la empresa. No se prevén cesiones de sus datos, salvo que exista una obligación legal. Para ejercitar sus derechos puede dirigirse a CODEOSCOPIC S.A., domiciliada enPaseo de la Habana, 9-11, 28036 de Madrid (MADRID), o bien por email [hidden email], con el fin de ejercer sus derechos de acceso, rectificación, supresión (derecho al olvido), limitación de tratamiento, portabilidad de los datos, oposición, y a no ser objeto de decisiones automatizadas, indicando como Asunto: “Derechos Ley Protección de Datos”, y adjuntando fotocopia de su DNI. Delegado de protección de [hidden email]


Reply | Threaded
Open this post in threaded view
|

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

Carlos Rovira-2
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 maybe you're the first trying this I don't know for sure at this time. Ad well, in Royale we use ArrayList instead of ArrayCollection like we use to do in Flex. For that reason I encourage you to start with a simple pass of a String and then cover other scenarios progressively.

thanks

Carlos



2018-08-10 9:51 GMT+02:00 Carlos Rovira <[hidden email]>:
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 = "Remoting.Service.Components.RemotingTest"
 destination = "GenericDestination

source is a deprecated property left in RO for backwards compatibility, since it expose the path to the server object. It's not needed anymore. Again talking about BlazeDS. Only destination should be required along "endPoint". If I search for "GenericDestination" in the config file you posted I don't find it. The same happens for "Remoting.Service.Components.RemotingTest". IMHO the .Net class should be exposed in the weborb config file like this one:

<service>
<name>ExamplesActivationSession</name>
<serviceId>Weborb.Examples.ShoppingCart</serviceId>
</service>

to have something like:

<service>
<name>RemotingTest</name>
<serviceId>Remoting.Service.Components.RemotingTest</serviceId>
</service>


In our example in BlazeDS we don't do this in config file since we have a Spring annotation in code. Example:

@Service("exampleService")
@RemotingDestination
public class ExampleService {

just guessing and trying to match what I know from BlazeDS and what I see in your WebOrb config file

Then remove "source" property from the Royale RO declaration

Now going to the calling code: I don't see nothing of that in your sample code. It seems the button calls "initRemoting" but where's the code?

The code should be something like:

protected function sendName():void
            {
service.send("XXX", []);
            }

Where XXX is the name of the method in the .Net class Remoting.Service.Components.RemotingTest
second param is the array of params to send to that method. I understand in this case we don't send anything

Then managing the result, I don't see again any callback code. But lets imagine s something like this:

private function onResult(evt:ResultEvent):void
            {
                trace("[Client:" + RoyaleClient.getInstance().id + "] Result= " + evt.data);

var arr:ArrayList = new ArrayList(evt.data as Array);
list.dataProvider = arr;
                
            }

If you run in debug mode (js-debug) in your browser (and here is important that you left your browser communication within local and external sources since that security restriction will make this communication not work)
you should see a trace with the "clientId" and the data from server. clientId will then be shared in each transaction with the server

then since we are receiving a list of countries for what I understand, you should get an Array (maybe for the first connection you should start with only a String, instead this structure since is more complex)

For the Array, one important thing is to know if each object in the array are plain Objects or TypedObjects and if the later, you'll need something like the following example in the Class:

[RemoteClass(alias="org.apache.royale.amfsamples.valueobjects.Product")]
    public class Product
    {

Maybe in WebOrb is needed as well some config, on this point.

My suggestion is that instead of try for the first time to exchange a list, you'll try to send a simple string and send back another string from WebOrb method. That will make a safe point from wich you can evolve to something more complicated. Then try a Typed object, and then try a List of typed objects.





2018-08-10 9:15 GMT+02:00 Carlos Rovira <[hidden email]>:
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 connection with BlazeDS, then "operation" is the name of the method your are asking for.
In SimpleRO instead of 5 is 13 (trigger connect operation) for the first connection.

So my guess is that something is wrong in your code

I'll respond to the other email now



2018-08-10 1:19 GMT+02:00 JoeBoxer <[hidden email]>:
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
clientId
destination
headers
messageId
timestamp
timeToLive

AND

operation
correlationId

This could be why the WebORB parser is throwing an exception.  Your
thoughts?



--



--

Carlos Rovira

Director General

M: +34 607 22 60 05

http://www.codeoscopic.com


Conócenos en 1 minuto!


AVISO LEGAL: La información contenida en este correo electrónico, y en su caso en los documentos adjuntos, es información privilegiada para uso exclusivo de la persona y/o personas a las que va dirigido. No está permitido el acceso a este mensaje a cualquier otra persona distinta a los indicados. Si Usted no es uno de los destinatarios, cualquier duplicación, reproducción, distribución, así como cualquier uso de la información contenida en él o cualquiera otra acción u omisión tomada en relación con el mismo, está prohibida y puede ser ilegal. En dicho caso, por favor, notifíquelo al remitente y proceda a la eliminación de este correo electrónico, así como de sus adjuntos si los hubiere. En cumplimiento de la legislación española vigente en materia de protección de datos de carácter personal y del RGPD 679/2016 le informamos que sus datos están siendo objeto de tratamiento por parte de CODEOSCOPIC S.A. con CIFA85677342, con la finalidad del mantenimiento y gestión de relaciones comerciales y administrativas. La base jurídica del tratamiento es el interés legítimo de la empresa. No se prevén cesiones de sus datos, salvo que exista una obligación legal. Para ejercitar sus derechos puede dirigirse a CODEOSCOPIC S.A., domiciliada enPaseo de la Habana, 9-11, 28036 de Madrid (MADRID), o bien por email [hidden email], con el fin de ejercer sus derechos de acceso, rectificación, supresión (derecho al olvido), limitación de tratamiento, portabilidad de los datos, oposición, y a no ser objeto de decisiones automatizadas, indicando como Asunto: “Derechos Ley Protección de Datos”, y adjuntando fotocopia de su DNI. Delegado de protección de [hidden email]





--
Reply | Threaded
Open this post in threaded view
|

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

JoeBoxer
In reply to this post by Carlos Rovira-2
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
<http://apache-royale-users.20374.n8.nabble.com/file/t53/remoting-config.xml>  

   <destination id="GenericDestination">
        <properties>
            <source>*</source>
        </properties>
    </destination>

I'll take some time to test various settings in the remoting-config file and
see if i get a different response.

The initRemoting click event does call the following code
                        protected function initRemoting():void
                        {
                                 remotingService.send("GetCountryList",[]);
                        }

Its a simple request that returns an array.  From what i can tell in the
WebORB logs is that the request coming in from RemoteObject or
SimpleRemoteObject is not being parsed correctly.  It doesn't matter what i
put in for the source, destination properties it still results in...

PM:cannot parse request. possible reasons: malformed request or protocol
formatter is not registered

Thank you for your continued attention with this issue.

Regards



--
Sent from: http://apache-royale-users.20374.n8.nabble.com/
Reply | Threaded
Open this post in threaded view
|

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

Alex Harui-2
In reply to this post by Piotr Zarzycki

I don’t know how difficult it will be to sync up.  I don’t want to stop to try right now.  Volunteers are welcome to try.

 

Thanks,

-Alex

 

From: Piotr Zarzycki <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Friday, August 10, 2018 at 12:37 AM
To: "[hidden email]" <[hidden email]>
Subject: 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?

 

 

Thanks,

Piotr

 

On Fri, Aug 10, 2018, 9:15 AM Carlos Rovira <[hidden email]> wrote:

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 connection with BlazeDS, then "operation" is the name of the method your are asking for.

In SimpleRO instead of 5 is 13 (trigger connect operation) for the first connection.

 

So my guess is that something is wrong in your code

 

I'll respond to the other email now

 

 

 

2018-08-10 1:19 GMT+02:00 JoeBoxer <[hidden email]>:

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
clientId
destination
headers
messageId
timestamp
timeToLive

AND

operation
correlationId

This could be why the WebORB parser is throwing an exception.  Your
thoughts?



 

--

Carlos Rovira

 

Reply | Threaded
Open this post in threaded view
|

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

Carlos Rovira-2
In reply to this post by JoeBoxer
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 you get. I'll help you next week as I return and can invest time in it. In the meanwhile, hope you could continue investigating what can be the issue, so we can isolate the possible causes.

thanks!

Carlos



2018-08-10 17:07 GMT+02:00 JoeBoxer <[hidden email]>:
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
<http://apache-royale-users.20374.n8.nabble.com/file/t53/remoting-config.xml

   <destination id="GenericDestination">
        <properties>
            <source>*</source>
        </properties>
    </destination>

I'll take some time to test various settings in the remoting-config file and
see if i get a different response.

The initRemoting click event does call the following code
                        protected function initRemoting():void
                        {
                                 remotingService.send("GetCountryList",[]);
                        }

Its a simple request that returns an array.  From what i can tell in the
WebORB logs is that the request coming in from RemoteObject or
SimpleRemoteObject is not being parsed correctly.  It doesn't matter what i
put in for the source, destination properties it still results in...

PM:cannot parse request. possible reasons: malformed request or protocol
formatter is not registered

Thank you for your continued attention with this issue.



--
Reply | Threaded
Open this post in threaded view
|

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

JoeBoxer
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.setRequestHeader("Content-Type", "application/x-amf; charset=UTF-8");

would need to be

xhr.setRequestHeader("Content-Type", "application/x-amf");

Thanks again for taking the time to look into this.  Not sure how to address
this unless I compile my own version everytime.  Any suggestions?

Regards



--
Sent from: http://apache-royale-users.20374.n8.nabble.com/
Reply | Threaded
Open this post in threaded view
|

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

Carlos Rovira-2
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:


I understand that you're now working fine with RO in WebORB. Let us know if you find some other issue.

Thanks for reporting this! :)

Carlos



El mié., 15 ago. 2018 a las 2:50, JoeBoxer (<[hidden email]>) escribió:
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.setRequestHeader("Content-Type", "application/x-amf; charset=UTF-8");

would need to be

xhr.setRequestHeader("Content-Type", "application/x-amf");

Thanks again for taking the time to look into this.  Not sure how to address
this unless I compile my own version everytime.  Any suggestions?

Regards



--
Sent from: http://apache-royale-users.20374.n8.nabble.com/

--