You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@royale.apache.org by radu birsan <ra...@gmail.com> on 2019/01/17 11:58:43 UTC
BlazeDS ChanelSet login convert to Royale
Hello,
I have a simple flex login module that uses mx:ChannelSet. Any idea on
how to make this work with Roylale js.
<?xml version="1.0" encoding="utf-8"?><mx:Application
xmlns:fx="http://ns.adobe.com/mxml/2009"
xmlns:mx="library://ns.adobe.com/flex/mx" creationComplete="main()">
<fx:Script>
<![CDATA[
import mx.messaging.ChannelSet;
import mx.messaging.channels.AMFChannel;
import mx.messaging.channels.StreamingAMFChannel;
import mx.messaging.messages.CommandMessage;
import mx.rpc.AsyncResponder;
import mx.rpc.AsyncToken;
import mx.rpc.events.FaultEvent;
import mx.rpc.events.ResultEvent;
public var cs:ChannelSet=null;
private var amfChannel:AMFChannel;
public var serverSTUB:String = "http://voip-manager.spherecom.com:9080"
public function main():void
{
cs = new ChannelSet();
amfChannel = new AMFChannel("my-longpolling-amf",serverSTUB +
"/RiaService" + "/messagebroker/amflongpolling");
cs.addChannel(amfChannel);
}
public function checkAPIVersion(event:ResultEvent = null,
token:Object = null):void
{
but.label = "checkAPIVersion Success";
}
private function handleLoginFault(event:FaultEvent = null,
token:Object = null):void
{
but.label = "Fault";
}
protected function login(event:MouseEvent=null):void
{
var token:AsyncToken = cs.login('rbirsan'.toUpperCase(), "ThisISWork?");
token.addResponder( new AsyncResponder(checkAPIVersion, handleLoginFault));
}
]]>
</fx:Script>
<mx:Button label="Login!" id="but" width="200" click="login(event)"
/></mx:Application>
Thank you,
Radu
Re: BlazeDS ChanelSet login convert to Royale
Posted by Greg Dove <gr...@gmail.com>.
I pushed updates a short while ago. Note the caveats I mentioned earlier
about ArrayCollection and ArrayList.
Please let me know any feedback or issues.
cheers
Greg
On Fri, Jan 18, 2019 at 5:56 PM Greg Dove <gr...@gmail.com> wrote:
>
> fyi I will aim to get something in tomorrow. I'm short of time today with
> family commitments tonight.
> -Greg
>
>
>
>
> On Fri, Jan 18, 2019 at 9:02 AM Carlos Rovira <ca...@apache.org>
> wrote:
>
>> Hi Greg,
>>
>> for me is ok to commit in the actual state, and form that point continue
>> fixing things in Apache Royale.
>> But is up to you to manage this.
>>
>> thanks
>>
>>
>>
>> El jue., 17 ene. 2019 a las 20:38, Greg Dove (<gr...@gmail.com>)
>> escribió:
>>
>>> AC = mx ArrayCollection
>>> AL = royale ArrayList
>>>
>>> The custom stuff is to send *both* AC and AL as AC (which the server
>>> side was always expecting), but always receive AC as AL.
>>>
>>> I think it was always receiving AC as plain Array in the past, so if
>>> this is acceptable for now, then I could do what you suggest.
>>> If yes, I will look at that towards end of my day today - if it needs a
>>> bit of tweaking then it might not be until tomorrow that I get it in.
>>> The other main change is in AMFNetConnection to support concurrent
>>> requests - this still needs further updates to support 'batching' calls
>>> into a single request (but that is less of an issue than the fix for
>>> concurrent requests, because subsequent requests were cancelling earlier
>>> ones that were not yet complete).
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Fri, Jan 18, 2019 at 8:23 AM Alex Harui <ah...@adobe.com> wrote:
>>>
>>>> IMO, if it isn’t going to break anything and will allow this potential
>>>> user to test something, check in what you have and make it general later.
>>>>
>>>>
>>>>
>>>> My 2 cents,
>>>>
>>>> -Alex
>>>>
>>>>
>>>>
>>>> *From: *Greg Dove <gr...@gmail.com>
>>>> *Reply-To: *"users@royale.apache.org" <us...@royale.apache.org>
>>>> *Date: *Thursday, January 17, 2019 at 11:06 AM
>>>> *To: *"users@royale.apache.org" <us...@royale.apache.org>
>>>> *Subject: *Re: BlazeDS ChanelSet login convert to Royale
>>>>
>>>>
>>>>
>>>>
>>>> Hi Alex,
>>>>
>>>>
>>>>
>>>> I can answer that. It's not customer approval. The changes are for
>>>> AMFBinaryData mainly. But I put in a bunch of custom stuff - which
>>>> represent an incomplete and custom IExternalizable support that only
>>>> targets ArrayCollection/ArrayList for now.
>>>>
>>>>
>>>>
>>>> I need to remove that, and re-implement as a general solution
>>>> (preferably retaining some opt-in/PAYG support for the 'custom' approach we
>>>> are using which is good for transition management between legacy code and
>>>> royale-specific work )
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Fri, Jan 18, 2019 at 7:53 AM Alex Harui <ah...@adobe.com> wrote:
>>>>
>>>> Carlos, why do you need your customer’s approval to commit fixes for
>>>> RemoteObject? The sooner you can commit those changes, the better it will
>>>> be for the community, IMO.
>>>>
>>>>
>>>>
>>>> -Alex
>>>>
>>>>
>>>>
>>>> *From: *Carlos Rovira <ca...@apache.org>
>>>> *Reply-To: *"users@royale.apache.org" <us...@royale.apache.org>
>>>> *Date: *Thursday, January 17, 2019 at 7:48 AM
>>>> *To: *"users@royale.apache.org" <us...@royale.apache.org>
>>>> *Subject: *Re: BlazeDS ChanelSet login convert to Royale
>>>>
>>>>
>>>>
>>>> Hi Radu,
>>>>
>>>>
>>>>
>>>> we'll do at some time, but that would be when our client want to show
>>>> it into public, so this could be not soon...As he give us green flag, hope
>>>> to share it since I think it's becoming very cool Apache Royale App :)
>>>>
>>>>
>>>>
>>>> El jue., 17 ene. 2019 a las 16:17, radu birsan (<ra...@gmail.com>)
>>>> escribió:
>>>>
>>>> Hi Carlos,
>>>>
>>>>
>>>>
>>>> Thank you for your effort. Having a complex AMF application ported
>>>> to Royal would encourage us to start porting our app.
>>>>
>>>> Hope you can share a sample of the finished product.
>>>>
>>>>
>>>>
>>>> Thank you,
>>>>
>>>> Radu
>>>>
>>>>
>>>>
>>>> On Thu, Jan 17, 2019 at 4:51 PM Carlos Rovira <ca...@apache.org>
>>>> wrote:
>>>>
>>>> Hi Radu,
>>>>
>>>>
>>>>
>>>> this is actually working in Royale. Being said that We (Greg and I)
>>>> have some fixes for RemoteObject that still didn't put on Apache Royale.
>>>> Will upload soon as we end our migration (hopefully 1-2 weeks from now).
>>>> But you can start trying a simple example.
>>>>
>>>>
>>>>
>>>> I recomend you to create a try the following test app :
>>>>
>>>>
>>>>
>>>> Java part:
>>>>
>>>>
>>>> https://github.com/apache/royale-asjs/tree/develop/examples/amf/SampleAmfWebApp
>>>> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Ftree%2Fdevelop%2Fexamples%2Famf%2FSampleAmfWebApp&data=02%7C01%7Caharui%40adobe.com%7C1c64482358ee410406d408d67caecb19%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833487513053128&sdata=ChslhnSNDpsJQCpzwNw6FFS70MrKDj2ny0ThA88d2GQ%3D&reserved=0>
>>>>
>>>>
>>>>
>>>> Royale client:
>>>>
>>>>
>>>> https://github.com/apache/royale-asjs/tree/develop/examples/mxroyale/RemoteObjectAMFTest
>>>> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Ftree%2Fdevelop%2Fexamples%2Fmxroyale%2FRemoteObjectAMFTest&data=02%7C01%7Caharui%40adobe.com%7C1c64482358ee410406d408d67caecb19%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833487513053128&sdata=i55MDcSkyl6Xl2zLCtIkqOvUGoD3dn%2Fub3KKk36VcJc%3D&reserved=0>
>>>>
>>>>
>>>>
>>>> and check this:
>>>>
>>>>
>>>> https://github.com/apache/royale-asjs/wiki/Apache-Royale-communication-with-AMF-and-RemoteObject
>>>> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FApache-Royale-communication-with-AMF-and-RemoteObject&data=02%7C01%7Caharui%40adobe.com%7C1c64482358ee410406d408d67caecb19%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833487513053128&sdata=WIWNe4udmeGymGmycAU77Z2p8E5%2BwSurbaImdYRoWX0%3D&reserved=0>
>>>>
>>>>
>>>>
>>>> things like turn enable-small-messages to false are very important to
>>>> have success
>>>>
>>>>
>>>>
>>>> Just let you know that we are migrating a flex application using Jewel
>>>> and MX RemoteObject and we are receiving/sending very complex graphs with
>>>> AMF successfully.
>>>>
>>>> As we get some free time (hopefully 2-3 weeks from now), Greg had in
>>>> mind to complete RemoteObject implementation with enable-small-messages
>>>> support too.
>>>>
>>>>
>>>>
>>>> thanks
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> El jue., 17 ene. 2019 a las 13:08, radu birsan (<ra...@gmail.com>)
>>>> escribió:
>>>>
>>>> Hello,
>>>>
>>>>
>>>>
>>>> I have a simple flex login module that uses mx:ChannelSet. Any idea
>>>> on how to make this work with Roylale js.
>>>>
>>>>
>>>>
>>>> *<?xml* version="1.0" encoding="utf-8"?>
>>>>
>>>> <mx:Application xmlns:fx="http://ns.adobe.com/mxml/2009 <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009&data=02%7C01%7Caharui%40adobe.com%7C1c64482358ee410406d408d67caecb19%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833487513053128&sdata=3D5lRGkpxE07WdpqgD8AYer6Ff%2Bg5SOnC10jYSfQBlI%3D&reserved=0>"
>>>>
>>>> xmlns:mx="library://ns.adobe.com/flex/mx <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fflex%2Fmx&data=02%7C01%7Caharui%40adobe.com%7C1c64482358ee410406d408d67caecb19%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833487513053128&sdata=l78ntUxSHwEQI%2FSz9uIJtSByE0UMUZdJ3ylAJTUP2ZA%3D&reserved=0>" creationComplete="main()">
>>>>
>>>> <fx:Script>
>>>>
>>>> <![CDATA[
>>>>
>>>> import mx.messaging.ChannelSet;
>>>>
>>>> import mx.messaging.channels.AMFChannel;
>>>>
>>>> import mx.messaging.channels.StreamingAMFChannel;
>>>>
>>>> import mx.messaging.messages.CommandMessage;
>>>>
>>>> import mx.rpc.AsyncResponder;
>>>>
>>>> import mx.rpc.AsyncToken;
>>>>
>>>> import mx.rpc.events.FaultEvent;
>>>>
>>>> import mx.rpc.events.ResultEvent;
>>>>
>>>> public var cs:ChannelSet=null;
>>>>
>>>> private var amfChannel:AMFChannel;
>>>>
>>>> public var serverSTUB:String = "http://voip-manager.spherecom.com:9080 <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fvoip-manager.spherecom.com%3A9080&data=02%7C01%7Caharui%40adobe.com%7C1c64482358ee410406d408d67caecb19%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833487513053128&sdata=aU2pum4pDssalbk4tMOG56ClDFsVfHHE9HxUTgEANkk%3D&reserved=0>"
>>>>
>>>>
>>>>
>>>> public function main():void
>>>>
>>>> {
>>>>
>>>> cs = new ChannelSet();
>>>>
>>>> amfChannel = new AMFChannel("my-longpolling-amf",serverSTUB + "/RiaService" + "/messagebroker/amflongpolling");
>>>>
>>>> cs.addChannel(amfChannel);
>>>>
>>>> }
>>>>
>>>>
>>>>
>>>> public function checkAPIVersion(event:ResultEvent = null, token:Object = null):void
>>>>
>>>> {
>>>>
>>>> but.label = "checkAPIVersion Success";
>>>>
>>>> }
>>>>
>>>>
>>>>
>>>> private function handleLoginFault(event:FaultEvent = null, token:Object = null):void
>>>>
>>>> {
>>>>
>>>> but.label = "Fault";
>>>>
>>>> }
>>>>
>>>>
>>>>
>>>> protected function login(event:MouseEvent=null):void
>>>>
>>>> {
>>>>
>>>> var token:AsyncToken = cs.login('rbirsan'.toUpperCase(), "ThisISWork?");
>>>>
>>>> token.addResponder( new AsyncResponder(checkAPIVersion, handleLoginFault));
>>>>
>>>> }
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> ]]>
>>>>
>>>> </fx:Script>
>>>>
>>>> <mx:Button label="Login!" id="but" width="200" click="login(event)" />
>>>>
>>>> </mx:Application>
>>>>
>>>>
>>>>
>>>> Thank you,
>>>>
>>>> Radu
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Carlos Rovira
>>>>
>>>> http://about.me/carlosrovira
>>>> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C1c64482358ee410406d408d67caecb19%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833487513053128&sdata=L2EEn42ISRv6I%2Fs5UdKRNSpx0%2F0n%2BHkx5BYd%2Bi8TeJI%3D&reserved=0>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Carlos Rovira
>>>>
>>>> http://about.me/carlosrovira
>>>> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C1c64482358ee410406d408d67caecb19%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833487513053128&sdata=L2EEn42ISRv6I%2Fs5UdKRNSpx0%2F0n%2BHkx5BYd%2Bi8TeJI%3D&reserved=0>
>>>>
>>>>
>>>>
>>>>
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>>
Re: BlazeDS ChanelSet login convert to Royale
Posted by Greg Dove <gr...@gmail.com>.
fyi I will aim to get something in tomorrow. I'm short of time today with
family commitments tonight.
-Greg
On Fri, Jan 18, 2019 at 9:02 AM Carlos Rovira <ca...@apache.org>
wrote:
> Hi Greg,
>
> for me is ok to commit in the actual state, and form that point continue
> fixing things in Apache Royale.
> But is up to you to manage this.
>
> thanks
>
>
>
> El jue., 17 ene. 2019 a las 20:38, Greg Dove (<gr...@gmail.com>)
> escribió:
>
>> AC = mx ArrayCollection
>> AL = royale ArrayList
>>
>> The custom stuff is to send *both* AC and AL as AC (which the server side
>> was always expecting), but always receive AC as AL.
>>
>> I think it was always receiving AC as plain Array in the past, so if this
>> is acceptable for now, then I could do what you suggest.
>> If yes, I will look at that towards end of my day today - if it needs a
>> bit of tweaking then it might not be until tomorrow that I get it in.
>> The other main change is in AMFNetConnection to support concurrent
>> requests - this still needs further updates to support 'batching' calls
>> into a single request (but that is less of an issue than the fix for
>> concurrent requests, because subsequent requests were cancelling earlier
>> ones that were not yet complete).
>>
>>
>>
>>
>>
>>
>> On Fri, Jan 18, 2019 at 8:23 AM Alex Harui <ah...@adobe.com> wrote:
>>
>>> IMO, if it isn’t going to break anything and will allow this potential
>>> user to test something, check in what you have and make it general later.
>>>
>>>
>>>
>>> My 2 cents,
>>>
>>> -Alex
>>>
>>>
>>>
>>> *From: *Greg Dove <gr...@gmail.com>
>>> *Reply-To: *"users@royale.apache.org" <us...@royale.apache.org>
>>> *Date: *Thursday, January 17, 2019 at 11:06 AM
>>> *To: *"users@royale.apache.org" <us...@royale.apache.org>
>>> *Subject: *Re: BlazeDS ChanelSet login convert to Royale
>>>
>>>
>>>
>>>
>>> Hi Alex,
>>>
>>>
>>>
>>> I can answer that. It's not customer approval. The changes are for
>>> AMFBinaryData mainly. But I put in a bunch of custom stuff - which
>>> represent an incomplete and custom IExternalizable support that only
>>> targets ArrayCollection/ArrayList for now.
>>>
>>>
>>>
>>> I need to remove that, and re-implement as a general solution
>>> (preferably retaining some opt-in/PAYG support for the 'custom' approach we
>>> are using which is good for transition management between legacy code and
>>> royale-specific work )
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Fri, Jan 18, 2019 at 7:53 AM Alex Harui <ah...@adobe.com> wrote:
>>>
>>> Carlos, why do you need your customer’s approval to commit fixes for
>>> RemoteObject? The sooner you can commit those changes, the better it will
>>> be for the community, IMO.
>>>
>>>
>>>
>>> -Alex
>>>
>>>
>>>
>>> *From: *Carlos Rovira <ca...@apache.org>
>>> *Reply-To: *"users@royale.apache.org" <us...@royale.apache.org>
>>> *Date: *Thursday, January 17, 2019 at 7:48 AM
>>> *To: *"users@royale.apache.org" <us...@royale.apache.org>
>>> *Subject: *Re: BlazeDS ChanelSet login convert to Royale
>>>
>>>
>>>
>>> Hi Radu,
>>>
>>>
>>>
>>> we'll do at some time, but that would be when our client want to show it
>>> into public, so this could be not soon...As he give us green flag, hope to
>>> share it since I think it's becoming very cool Apache Royale App :)
>>>
>>>
>>>
>>> El jue., 17 ene. 2019 a las 16:17, radu birsan (<ra...@gmail.com>)
>>> escribió:
>>>
>>> Hi Carlos,
>>>
>>>
>>>
>>> Thank you for your effort. Having a complex AMF application ported to
>>> Royal would encourage us to start porting our app.
>>>
>>> Hope you can share a sample of the finished product.
>>>
>>>
>>>
>>> Thank you,
>>>
>>> Radu
>>>
>>>
>>>
>>> On Thu, Jan 17, 2019 at 4:51 PM Carlos Rovira <ca...@apache.org>
>>> wrote:
>>>
>>> Hi Radu,
>>>
>>>
>>>
>>> this is actually working in Royale. Being said that We (Greg and I) have
>>> some fixes for RemoteObject that still didn't put on Apache Royale. Will
>>> upload soon as we end our migration (hopefully 1-2 weeks from now). But you
>>> can start trying a simple example.
>>>
>>>
>>>
>>> I recomend you to create a try the following test app :
>>>
>>>
>>>
>>> Java part:
>>>
>>>
>>> https://github.com/apache/royale-asjs/tree/develop/examples/amf/SampleAmfWebApp
>>> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Ftree%2Fdevelop%2Fexamples%2Famf%2FSampleAmfWebApp&data=02%7C01%7Caharui%40adobe.com%7C1c64482358ee410406d408d67caecb19%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833487513053128&sdata=ChslhnSNDpsJQCpzwNw6FFS70MrKDj2ny0ThA88d2GQ%3D&reserved=0>
>>>
>>>
>>>
>>> Royale client:
>>>
>>>
>>> https://github.com/apache/royale-asjs/tree/develop/examples/mxroyale/RemoteObjectAMFTest
>>> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Ftree%2Fdevelop%2Fexamples%2Fmxroyale%2FRemoteObjectAMFTest&data=02%7C01%7Caharui%40adobe.com%7C1c64482358ee410406d408d67caecb19%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833487513053128&sdata=i55MDcSkyl6Xl2zLCtIkqOvUGoD3dn%2Fub3KKk36VcJc%3D&reserved=0>
>>>
>>>
>>>
>>> and check this:
>>>
>>>
>>> https://github.com/apache/royale-asjs/wiki/Apache-Royale-communication-with-AMF-and-RemoteObject
>>> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FApache-Royale-communication-with-AMF-and-RemoteObject&data=02%7C01%7Caharui%40adobe.com%7C1c64482358ee410406d408d67caecb19%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833487513053128&sdata=WIWNe4udmeGymGmycAU77Z2p8E5%2BwSurbaImdYRoWX0%3D&reserved=0>
>>>
>>>
>>>
>>> things like turn enable-small-messages to false are very important to
>>> have success
>>>
>>>
>>>
>>> Just let you know that we are migrating a flex application using Jewel
>>> and MX RemoteObject and we are receiving/sending very complex graphs with
>>> AMF successfully.
>>>
>>> As we get some free time (hopefully 2-3 weeks from now), Greg had in
>>> mind to complete RemoteObject implementation with enable-small-messages
>>> support too.
>>>
>>>
>>>
>>> thanks
>>>
>>>
>>>
>>>
>>>
>>> El jue., 17 ene. 2019 a las 13:08, radu birsan (<ra...@gmail.com>)
>>> escribió:
>>>
>>> Hello,
>>>
>>>
>>>
>>> I have a simple flex login module that uses mx:ChannelSet. Any idea
>>> on how to make this work with Roylale js.
>>>
>>>
>>>
>>> *<?xml* version="1.0" encoding="utf-8"?>
>>>
>>> <mx:Application xmlns:fx="http://ns.adobe.com/mxml/2009 <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009&data=02%7C01%7Caharui%40adobe.com%7C1c64482358ee410406d408d67caecb19%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833487513053128&sdata=3D5lRGkpxE07WdpqgD8AYer6Ff%2Bg5SOnC10jYSfQBlI%3D&reserved=0>"
>>>
>>> xmlns:mx="library://ns.adobe.com/flex/mx <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fflex%2Fmx&data=02%7C01%7Caharui%40adobe.com%7C1c64482358ee410406d408d67caecb19%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833487513053128&sdata=l78ntUxSHwEQI%2FSz9uIJtSByE0UMUZdJ3ylAJTUP2ZA%3D&reserved=0>" creationComplete="main()">
>>>
>>> <fx:Script>
>>>
>>> <![CDATA[
>>>
>>> import mx.messaging.ChannelSet;
>>>
>>> import mx.messaging.channels.AMFChannel;
>>>
>>> import mx.messaging.channels.StreamingAMFChannel;
>>>
>>> import mx.messaging.messages.CommandMessage;
>>>
>>> import mx.rpc.AsyncResponder;
>>>
>>> import mx.rpc.AsyncToken;
>>>
>>> import mx.rpc.events.FaultEvent;
>>>
>>> import mx.rpc.events.ResultEvent;
>>>
>>> public var cs:ChannelSet=null;
>>>
>>> private var amfChannel:AMFChannel;
>>>
>>> public var serverSTUB:String = "http://voip-manager.spherecom.com:9080 <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fvoip-manager.spherecom.com%3A9080&data=02%7C01%7Caharui%40adobe.com%7C1c64482358ee410406d408d67caecb19%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833487513053128&sdata=aU2pum4pDssalbk4tMOG56ClDFsVfHHE9HxUTgEANkk%3D&reserved=0>"
>>>
>>>
>>>
>>> public function main():void
>>>
>>> {
>>>
>>> cs = new ChannelSet();
>>>
>>> amfChannel = new AMFChannel("my-longpolling-amf",serverSTUB + "/RiaService" + "/messagebroker/amflongpolling");
>>>
>>> cs.addChannel(amfChannel);
>>>
>>> }
>>>
>>>
>>>
>>> public function checkAPIVersion(event:ResultEvent = null, token:Object = null):void
>>>
>>> {
>>>
>>> but.label = "checkAPIVersion Success";
>>>
>>> }
>>>
>>>
>>>
>>> private function handleLoginFault(event:FaultEvent = null, token:Object = null):void
>>>
>>> {
>>>
>>> but.label = "Fault";
>>>
>>> }
>>>
>>>
>>>
>>> protected function login(event:MouseEvent=null):void
>>>
>>> {
>>>
>>> var token:AsyncToken = cs.login('rbirsan'.toUpperCase(), "ThisISWork?");
>>>
>>> token.addResponder( new AsyncResponder(checkAPIVersion, handleLoginFault));
>>>
>>> }
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> ]]>
>>>
>>> </fx:Script>
>>>
>>> <mx:Button label="Login!" id="but" width="200" click="login(event)" />
>>>
>>> </mx:Application>
>>>
>>>
>>>
>>> Thank you,
>>>
>>> Radu
>>>
>>>
>>>
>>>
>>> --
>>>
>>> Carlos Rovira
>>>
>>> http://about.me/carlosrovira
>>> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C1c64482358ee410406d408d67caecb19%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833487513053128&sdata=L2EEn42ISRv6I%2Fs5UdKRNSpx0%2F0n%2BHkx5BYd%2Bi8TeJI%3D&reserved=0>
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>>
>>> Carlos Rovira
>>>
>>> http://about.me/carlosrovira
>>> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C1c64482358ee410406d408d67caecb19%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833487513053128&sdata=L2EEn42ISRv6I%2Fs5UdKRNSpx0%2F0n%2BHkx5BYd%2Bi8TeJI%3D&reserved=0>
>>>
>>>
>>>
>>>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>
Re: BlazeDS ChanelSet login convert to Royale
Posted by Carlos Rovira <ca...@apache.org>.
Hi Greg,
for me is ok to commit in the actual state, and form that point continue
fixing things in Apache Royale.
But is up to you to manage this.
thanks
El jue., 17 ene. 2019 a las 20:38, Greg Dove (<gr...@gmail.com>)
escribió:
> AC = mx ArrayCollection
> AL = royale ArrayList
>
> The custom stuff is to send *both* AC and AL as AC (which the server side
> was always expecting), but always receive AC as AL.
>
> I think it was always receiving AC as plain Array in the past, so if this
> is acceptable for now, then I could do what you suggest.
> If yes, I will look at that towards end of my day today - if it needs a
> bit of tweaking then it might not be until tomorrow that I get it in.
> The other main change is in AMFNetConnection to support concurrent
> requests - this still needs further updates to support 'batching' calls
> into a single request (but that is less of an issue than the fix for
> concurrent requests, because subsequent requests were cancelling earlier
> ones that were not yet complete).
>
>
>
>
>
>
> On Fri, Jan 18, 2019 at 8:23 AM Alex Harui <ah...@adobe.com> wrote:
>
>> IMO, if it isn’t going to break anything and will allow this potential
>> user to test something, check in what you have and make it general later.
>>
>>
>>
>> My 2 cents,
>>
>> -Alex
>>
>>
>>
>> *From: *Greg Dove <gr...@gmail.com>
>> *Reply-To: *"users@royale.apache.org" <us...@royale.apache.org>
>> *Date: *Thursday, January 17, 2019 at 11:06 AM
>> *To: *"users@royale.apache.org" <us...@royale.apache.org>
>> *Subject: *Re: BlazeDS ChanelSet login convert to Royale
>>
>>
>>
>>
>> Hi Alex,
>>
>>
>>
>> I can answer that. It's not customer approval. The changes are for
>> AMFBinaryData mainly. But I put in a bunch of custom stuff - which
>> represent an incomplete and custom IExternalizable support that only
>> targets ArrayCollection/ArrayList for now.
>>
>>
>>
>> I need to remove that, and re-implement as a general solution (preferably
>> retaining some opt-in/PAYG support for the 'custom' approach we are using
>> which is good for transition management between legacy code and
>> royale-specific work )
>>
>>
>>
>>
>>
>>
>>
>> On Fri, Jan 18, 2019 at 7:53 AM Alex Harui <ah...@adobe.com> wrote:
>>
>> Carlos, why do you need your customer’s approval to commit fixes for
>> RemoteObject? The sooner you can commit those changes, the better it will
>> be for the community, IMO.
>>
>>
>>
>> -Alex
>>
>>
>>
>> *From: *Carlos Rovira <ca...@apache.org>
>> *Reply-To: *"users@royale.apache.org" <us...@royale.apache.org>
>> *Date: *Thursday, January 17, 2019 at 7:48 AM
>> *To: *"users@royale.apache.org" <us...@royale.apache.org>
>> *Subject: *Re: BlazeDS ChanelSet login convert to Royale
>>
>>
>>
>> Hi Radu,
>>
>>
>>
>> we'll do at some time, but that would be when our client want to show it
>> into public, so this could be not soon...As he give us green flag, hope to
>> share it since I think it's becoming very cool Apache Royale App :)
>>
>>
>>
>> El jue., 17 ene. 2019 a las 16:17, radu birsan (<ra...@gmail.com>)
>> escribió:
>>
>> Hi Carlos,
>>
>>
>>
>> Thank you for your effort. Having a complex AMF application ported to
>> Royal would encourage us to start porting our app.
>>
>> Hope you can share a sample of the finished product.
>>
>>
>>
>> Thank you,
>>
>> Radu
>>
>>
>>
>> On Thu, Jan 17, 2019 at 4:51 PM Carlos Rovira <ca...@apache.org>
>> wrote:
>>
>> Hi Radu,
>>
>>
>>
>> this is actually working in Royale. Being said that We (Greg and I) have
>> some fixes for RemoteObject that still didn't put on Apache Royale. Will
>> upload soon as we end our migration (hopefully 1-2 weeks from now). But you
>> can start trying a simple example.
>>
>>
>>
>> I recomend you to create a try the following test app :
>>
>>
>>
>> Java part:
>>
>>
>> https://github.com/apache/royale-asjs/tree/develop/examples/amf/SampleAmfWebApp
>> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Ftree%2Fdevelop%2Fexamples%2Famf%2FSampleAmfWebApp&data=02%7C01%7Caharui%40adobe.com%7C1c64482358ee410406d408d67caecb19%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833487513053128&sdata=ChslhnSNDpsJQCpzwNw6FFS70MrKDj2ny0ThA88d2GQ%3D&reserved=0>
>>
>>
>>
>> Royale client:
>>
>>
>> https://github.com/apache/royale-asjs/tree/develop/examples/mxroyale/RemoteObjectAMFTest
>> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Ftree%2Fdevelop%2Fexamples%2Fmxroyale%2FRemoteObjectAMFTest&data=02%7C01%7Caharui%40adobe.com%7C1c64482358ee410406d408d67caecb19%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833487513053128&sdata=i55MDcSkyl6Xl2zLCtIkqOvUGoD3dn%2Fub3KKk36VcJc%3D&reserved=0>
>>
>>
>>
>> and check this:
>>
>>
>> https://github.com/apache/royale-asjs/wiki/Apache-Royale-communication-with-AMF-and-RemoteObject
>> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FApache-Royale-communication-with-AMF-and-RemoteObject&data=02%7C01%7Caharui%40adobe.com%7C1c64482358ee410406d408d67caecb19%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833487513053128&sdata=WIWNe4udmeGymGmycAU77Z2p8E5%2BwSurbaImdYRoWX0%3D&reserved=0>
>>
>>
>>
>> things like turn enable-small-messages to false are very important to
>> have success
>>
>>
>>
>> Just let you know that we are migrating a flex application using Jewel
>> and MX RemoteObject and we are receiving/sending very complex graphs with
>> AMF successfully.
>>
>> As we get some free time (hopefully 2-3 weeks from now), Greg had in mind
>> to complete RemoteObject implementation with enable-small-messages support
>> too.
>>
>>
>>
>> thanks
>>
>>
>>
>>
>>
>> El jue., 17 ene. 2019 a las 13:08, radu birsan (<ra...@gmail.com>)
>> escribió:
>>
>> Hello,
>>
>>
>>
>> I have a simple flex login module that uses mx:ChannelSet. Any idea on
>> how to make this work with Roylale js.
>>
>>
>>
>> *<?xml* version="1.0" encoding="utf-8"?>
>>
>> <mx:Application xmlns:fx="http://ns.adobe.com/mxml/2009 <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009&data=02%7C01%7Caharui%40adobe.com%7C1c64482358ee410406d408d67caecb19%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833487513053128&sdata=3D5lRGkpxE07WdpqgD8AYer6Ff%2Bg5SOnC10jYSfQBlI%3D&reserved=0>"
>>
>> xmlns:mx="library://ns.adobe.com/flex/mx <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fflex%2Fmx&data=02%7C01%7Caharui%40adobe.com%7C1c64482358ee410406d408d67caecb19%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833487513053128&sdata=l78ntUxSHwEQI%2FSz9uIJtSByE0UMUZdJ3ylAJTUP2ZA%3D&reserved=0>" creationComplete="main()">
>>
>> <fx:Script>
>>
>> <![CDATA[
>>
>> import mx.messaging.ChannelSet;
>>
>> import mx.messaging.channels.AMFChannel;
>>
>> import mx.messaging.channels.StreamingAMFChannel;
>>
>> import mx.messaging.messages.CommandMessage;
>>
>> import mx.rpc.AsyncResponder;
>>
>> import mx.rpc.AsyncToken;
>>
>> import mx.rpc.events.FaultEvent;
>>
>> import mx.rpc.events.ResultEvent;
>>
>> public var cs:ChannelSet=null;
>>
>> private var amfChannel:AMFChannel;
>>
>> public var serverSTUB:String = "http://voip-manager.spherecom.com:9080 <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fvoip-manager.spherecom.com%3A9080&data=02%7C01%7Caharui%40adobe.com%7C1c64482358ee410406d408d67caecb19%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833487513053128&sdata=aU2pum4pDssalbk4tMOG56ClDFsVfHHE9HxUTgEANkk%3D&reserved=0>"
>>
>>
>>
>> public function main():void
>>
>> {
>>
>> cs = new ChannelSet();
>>
>> amfChannel = new AMFChannel("my-longpolling-amf",serverSTUB + "/RiaService" + "/messagebroker/amflongpolling");
>>
>> cs.addChannel(amfChannel);
>>
>> }
>>
>>
>>
>> public function checkAPIVersion(event:ResultEvent = null, token:Object = null):void
>>
>> {
>>
>> but.label = "checkAPIVersion Success";
>>
>> }
>>
>>
>>
>> private function handleLoginFault(event:FaultEvent = null, token:Object = null):void
>>
>> {
>>
>> but.label = "Fault";
>>
>> }
>>
>>
>>
>> protected function login(event:MouseEvent=null):void
>>
>> {
>>
>> var token:AsyncToken = cs.login('rbirsan'.toUpperCase(), "ThisISWork?");
>>
>> token.addResponder( new AsyncResponder(checkAPIVersion, handleLoginFault));
>>
>> }
>>
>>
>>
>>
>>
>>
>>
>> ]]>
>>
>> </fx:Script>
>>
>> <mx:Button label="Login!" id="but" width="200" click="login(event)" />
>>
>> </mx:Application>
>>
>>
>>
>> Thank you,
>>
>> Radu
>>
>>
>>
>>
>> --
>>
>> Carlos Rovira
>>
>> http://about.me/carlosrovira
>> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C1c64482358ee410406d408d67caecb19%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833487513053128&sdata=L2EEn42ISRv6I%2Fs5UdKRNSpx0%2F0n%2BHkx5BYd%2Bi8TeJI%3D&reserved=0>
>>
>>
>>
>>
>>
>>
>> --
>>
>> Carlos Rovira
>>
>> http://about.me/carlosrovira
>> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C1c64482358ee410406d408d67caecb19%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833487513053128&sdata=L2EEn42ISRv6I%2Fs5UdKRNSpx0%2F0n%2BHkx5BYd%2Bi8TeJI%3D&reserved=0>
>>
>>
>>
>>
--
Carlos Rovira
http://about.me/carlosrovira
Re: BlazeDS ChanelSet login convert to Royale
Posted by Greg Dove <gr...@gmail.com>.
AC = mx ArrayCollection
AL = royale ArrayList
The custom stuff is to send *both* AC and AL as AC (which the server side
was always expecting), but always receive AC as AL.
I think it was always receiving AC as plain Array in the past, so if this
is acceptable for now, then I could do what you suggest.
If yes, I will look at that towards end of my day today - if it needs a bit
of tweaking then it might not be until tomorrow that I get it in.
The other main change is in AMFNetConnection to support concurrent requests
- this still needs further updates to support 'batching' calls into a
single request (but that is less of an issue than the fix for concurrent
requests, because subsequent requests were cancelling earlier ones that
were not yet complete).
On Fri, Jan 18, 2019 at 8:23 AM Alex Harui <ah...@adobe.com> wrote:
> IMO, if it isn’t going to break anything and will allow this potential
> user to test something, check in what you have and make it general later.
>
>
>
> My 2 cents,
>
> -Alex
>
>
>
> *From: *Greg Dove <gr...@gmail.com>
> *Reply-To: *"users@royale.apache.org" <us...@royale.apache.org>
> *Date: *Thursday, January 17, 2019 at 11:06 AM
> *To: *"users@royale.apache.org" <us...@royale.apache.org>
> *Subject: *Re: BlazeDS ChanelSet login convert to Royale
>
>
>
>
> Hi Alex,
>
>
>
> I can answer that. It's not customer approval. The changes are for
> AMFBinaryData mainly. But I put in a bunch of custom stuff - which
> represent an incomplete and custom IExternalizable support that only
> targets ArrayCollection/ArrayList for now.
>
>
>
> I need to remove that, and re-implement as a general solution (preferably
> retaining some opt-in/PAYG support for the 'custom' approach we are using
> which is good for transition management between legacy code and
> royale-specific work )
>
>
>
>
>
>
>
> On Fri, Jan 18, 2019 at 7:53 AM Alex Harui <ah...@adobe.com> wrote:
>
> Carlos, why do you need your customer’s approval to commit fixes for
> RemoteObject? The sooner you can commit those changes, the better it will
> be for the community, IMO.
>
>
>
> -Alex
>
>
>
> *From: *Carlos Rovira <ca...@apache.org>
> *Reply-To: *"users@royale.apache.org" <us...@royale.apache.org>
> *Date: *Thursday, January 17, 2019 at 7:48 AM
> *To: *"users@royale.apache.org" <us...@royale.apache.org>
> *Subject: *Re: BlazeDS ChanelSet login convert to Royale
>
>
>
> Hi Radu,
>
>
>
> we'll do at some time, but that would be when our client want to show it
> into public, so this could be not soon...As he give us green flag, hope to
> share it since I think it's becoming very cool Apache Royale App :)
>
>
>
> El jue., 17 ene. 2019 a las 16:17, radu birsan (<ra...@gmail.com>)
> escribió:
>
> Hi Carlos,
>
>
>
> Thank you for your effort. Having a complex AMF application ported to
> Royal would encourage us to start porting our app.
>
> Hope you can share a sample of the finished product.
>
>
>
> Thank you,
>
> Radu
>
>
>
> On Thu, Jan 17, 2019 at 4:51 PM Carlos Rovira <ca...@apache.org>
> wrote:
>
> Hi Radu,
>
>
>
> this is actually working in Royale. Being said that We (Greg and I) have
> some fixes for RemoteObject that still didn't put on Apache Royale. Will
> upload soon as we end our migration (hopefully 1-2 weeks from now). But you
> can start trying a simple example.
>
>
>
> I recomend you to create a try the following test app :
>
>
>
> Java part:
>
>
> https://github.com/apache/royale-asjs/tree/develop/examples/amf/SampleAmfWebApp
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Ftree%2Fdevelop%2Fexamples%2Famf%2FSampleAmfWebApp&data=02%7C01%7Caharui%40adobe.com%7C1c64482358ee410406d408d67caecb19%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833487513053128&sdata=ChslhnSNDpsJQCpzwNw6FFS70MrKDj2ny0ThA88d2GQ%3D&reserved=0>
>
>
>
> Royale client:
>
>
> https://github.com/apache/royale-asjs/tree/develop/examples/mxroyale/RemoteObjectAMFTest
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Ftree%2Fdevelop%2Fexamples%2Fmxroyale%2FRemoteObjectAMFTest&data=02%7C01%7Caharui%40adobe.com%7C1c64482358ee410406d408d67caecb19%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833487513053128&sdata=i55MDcSkyl6Xl2zLCtIkqOvUGoD3dn%2Fub3KKk36VcJc%3D&reserved=0>
>
>
>
> and check this:
>
>
> https://github.com/apache/royale-asjs/wiki/Apache-Royale-communication-with-AMF-and-RemoteObject
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FApache-Royale-communication-with-AMF-and-RemoteObject&data=02%7C01%7Caharui%40adobe.com%7C1c64482358ee410406d408d67caecb19%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833487513053128&sdata=WIWNe4udmeGymGmycAU77Z2p8E5%2BwSurbaImdYRoWX0%3D&reserved=0>
>
>
>
> things like turn enable-small-messages to false are very important to
> have success
>
>
>
> Just let you know that we are migrating a flex application using Jewel and
> MX RemoteObject and we are receiving/sending very complex graphs with AMF
> successfully.
>
> As we get some free time (hopefully 2-3 weeks from now), Greg had in mind
> to complete RemoteObject implementation with enable-small-messages support
> too.
>
>
>
> thanks
>
>
>
>
>
> El jue., 17 ene. 2019 a las 13:08, radu birsan (<ra...@gmail.com>)
> escribió:
>
> Hello,
>
>
>
> I have a simple flex login module that uses mx:ChannelSet. Any idea on
> how to make this work with Roylale js.
>
>
>
> *<?xml* version="1.0" encoding="utf-8"?>
>
> <mx:Application xmlns:fx="http://ns.adobe.com/mxml/2009 <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009&data=02%7C01%7Caharui%40adobe.com%7C1c64482358ee410406d408d67caecb19%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833487513053128&sdata=3D5lRGkpxE07WdpqgD8AYer6Ff%2Bg5SOnC10jYSfQBlI%3D&reserved=0>"
>
> xmlns:mx="library://ns.adobe.com/flex/mx <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fflex%2Fmx&data=02%7C01%7Caharui%40adobe.com%7C1c64482358ee410406d408d67caecb19%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833487513053128&sdata=l78ntUxSHwEQI%2FSz9uIJtSByE0UMUZdJ3ylAJTUP2ZA%3D&reserved=0>" creationComplete="main()">
>
> <fx:Script>
>
> <![CDATA[
>
> import mx.messaging.ChannelSet;
>
> import mx.messaging.channels.AMFChannel;
>
> import mx.messaging.channels.StreamingAMFChannel;
>
> import mx.messaging.messages.CommandMessage;
>
> import mx.rpc.AsyncResponder;
>
> import mx.rpc.AsyncToken;
>
> import mx.rpc.events.FaultEvent;
>
> import mx.rpc.events.ResultEvent;
>
> public var cs:ChannelSet=null;
>
> private var amfChannel:AMFChannel;
>
> public var serverSTUB:String = "http://voip-manager.spherecom.com:9080 <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fvoip-manager.spherecom.com%3A9080&data=02%7C01%7Caharui%40adobe.com%7C1c64482358ee410406d408d67caecb19%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833487513053128&sdata=aU2pum4pDssalbk4tMOG56ClDFsVfHHE9HxUTgEANkk%3D&reserved=0>"
>
>
>
> public function main():void
>
> {
>
> cs = new ChannelSet();
>
> amfChannel = new AMFChannel("my-longpolling-amf",serverSTUB + "/RiaService" + "/messagebroker/amflongpolling");
>
> cs.addChannel(amfChannel);
>
> }
>
>
>
> public function checkAPIVersion(event:ResultEvent = null, token:Object = null):void
>
> {
>
> but.label = "checkAPIVersion Success";
>
> }
>
>
>
> private function handleLoginFault(event:FaultEvent = null, token:Object = null):void
>
> {
>
> but.label = "Fault";
>
> }
>
>
>
> protected function login(event:MouseEvent=null):void
>
> {
>
> var token:AsyncToken = cs.login('rbirsan'.toUpperCase(), "ThisISWork?");
>
> token.addResponder( new AsyncResponder(checkAPIVersion, handleLoginFault));
>
> }
>
>
>
>
>
>
>
> ]]>
>
> </fx:Script>
>
> <mx:Button label="Login!" id="but" width="200" click="login(event)" />
>
> </mx:Application>
>
>
>
> Thank you,
>
> Radu
>
>
>
>
> --
>
> Carlos Rovira
>
> http://about.me/carlosrovira
> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C1c64482358ee410406d408d67caecb19%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833487513053128&sdata=L2EEn42ISRv6I%2Fs5UdKRNSpx0%2F0n%2BHkx5BYd%2Bi8TeJI%3D&reserved=0>
>
>
>
>
>
>
> --
>
> Carlos Rovira
>
> http://about.me/carlosrovira
> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C1c64482358ee410406d408d67caecb19%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833487513053128&sdata=L2EEn42ISRv6I%2Fs5UdKRNSpx0%2F0n%2BHkx5BYd%2Bi8TeJI%3D&reserved=0>
>
>
>
>
Re: BlazeDS ChanelSet login convert to Royale
Posted by Alex Harui <ah...@adobe.com>.
IMO, if it isn’t going to break anything and will allow this potential user to test something, check in what you have and make it general later.
My 2 cents,
-Alex
From: Greg Dove <gr...@gmail.com>
Reply-To: "users@royale.apache.org" <us...@royale.apache.org>
Date: Thursday, January 17, 2019 at 11:06 AM
To: "users@royale.apache.org" <us...@royale.apache.org>
Subject: Re: BlazeDS ChanelSet login convert to Royale
Hi Alex,
I can answer that. It's not customer approval. The changes are for AMFBinaryData mainly. But I put in a bunch of custom stuff - which represent an incomplete and custom IExternalizable support that only targets ArrayCollection/ArrayList for now.
I need to remove that, and re-implement as a general solution (preferably retaining some opt-in/PAYG support for the 'custom' approach we are using which is good for transition management between legacy code and royale-specific work )
On Fri, Jan 18, 2019 at 7:53 AM Alex Harui <ah...@adobe.com>> wrote:
Carlos, why do you need your customer’s approval to commit fixes for RemoteObject? The sooner you can commit those changes, the better it will be for the community, IMO.
-Alex
From: Carlos Rovira <ca...@apache.org>>
Reply-To: "users@royale.apache.org<ma...@royale.apache.org>" <us...@royale.apache.org>>
Date: Thursday, January 17, 2019 at 7:48 AM
To: "users@royale.apache.org<ma...@royale.apache.org>" <us...@royale.apache.org>>
Subject: Re: BlazeDS ChanelSet login convert to Royale
Hi Radu,
we'll do at some time, but that would be when our client want to show it into public, so this could be not soon...As he give us green flag, hope to share it since I think it's becoming very cool Apache Royale App :)
El jue., 17 ene. 2019 a las 16:17, radu birsan (<ra...@gmail.com>>) escribió:
Hi Carlos,
Thank you for your effort. Having a complex AMF application ported to Royal would encourage us to start porting our app.
Hope you can share a sample of the finished product.
Thank you,
Radu
On Thu, Jan 17, 2019 at 4:51 PM Carlos Rovira <ca...@apache.org>> wrote:
Hi Radu,
this is actually working in Royale. Being said that We (Greg and I) have some fixes for RemoteObject that still didn't put on Apache Royale. Will upload soon as we end our migration (hopefully 1-2 weeks from now). But you can start trying a simple example.
I recomend you to create a try the following test app :
Java part:
https://github.com/apache/royale-asjs/tree/develop/examples/amf/SampleAmfWebApp<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Ftree%2Fdevelop%2Fexamples%2Famf%2FSampleAmfWebApp&data=02%7C01%7Caharui%40adobe.com%7C1c64482358ee410406d408d67caecb19%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833487513053128&sdata=ChslhnSNDpsJQCpzwNw6FFS70MrKDj2ny0ThA88d2GQ%3D&reserved=0>
Royale client:
https://github.com/apache/royale-asjs/tree/develop/examples/mxroyale/RemoteObjectAMFTest<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Ftree%2Fdevelop%2Fexamples%2Fmxroyale%2FRemoteObjectAMFTest&data=02%7C01%7Caharui%40adobe.com%7C1c64482358ee410406d408d67caecb19%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833487513053128&sdata=i55MDcSkyl6Xl2zLCtIkqOvUGoD3dn%2Fub3KKk36VcJc%3D&reserved=0>
and check this:
https://github.com/apache/royale-asjs/wiki/Apache-Royale-communication-with-AMF-and-RemoteObject<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FApache-Royale-communication-with-AMF-and-RemoteObject&data=02%7C01%7Caharui%40adobe.com%7C1c64482358ee410406d408d67caecb19%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833487513053128&sdata=WIWNe4udmeGymGmycAU77Z2p8E5%2BwSurbaImdYRoWX0%3D&reserved=0>
things like turn enable-small-messages to false are very important to have success
Just let you know that we are migrating a flex application using Jewel and MX RemoteObject and we are receiving/sending very complex graphs with AMF successfully.
As we get some free time (hopefully 2-3 weeks from now), Greg had in mind to complete RemoteObject implementation with enable-small-messages support too.
thanks
El jue., 17 ene. 2019 a las 13:08, radu birsan (<ra...@gmail.com>>) escribió:
Hello,
I have a simple flex login module that uses mx:ChannelSet. Any idea on how to make this work with Roylale js.
<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:fx="http://ns.adobe.com/mxml/2009<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009&data=02%7C01%7Caharui%40adobe.com%7C1c64482358ee410406d408d67caecb19%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833487513053128&sdata=3D5lRGkpxE07WdpqgD8AYer6Ff%2Bg5SOnC10jYSfQBlI%3D&reserved=0>"
xmlns:mx="library://ns.adobe.com/flex/mx<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fflex%2Fmx&data=02%7C01%7Caharui%40adobe.com%7C1c64482358ee410406d408d67caecb19%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833487513053128&sdata=l78ntUxSHwEQI%2FSz9uIJtSByE0UMUZdJ3ylAJTUP2ZA%3D&reserved=0>" creationComplete="main()">
<fx:Script>
<![CDATA[
import mx.messaging.ChannelSet;
import mx.messaging.channels.AMFChannel;
import mx.messaging.channels.StreamingAMFChannel;
import mx.messaging.messages.CommandMessage;
import mx.rpc.AsyncResponder;
import mx.rpc.AsyncToken;
import mx.rpc.events.FaultEvent;
import mx.rpc.events.ResultEvent;
public var cs:ChannelSet=null;
private var amfChannel:AMFChannel;
public var serverSTUB:String = "http://voip-manager.spherecom.com:9080<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fvoip-manager.spherecom.com%3A9080&data=02%7C01%7Caharui%40adobe.com%7C1c64482358ee410406d408d67caecb19%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833487513053128&sdata=aU2pum4pDssalbk4tMOG56ClDFsVfHHE9HxUTgEANkk%3D&reserved=0>"
public function main():void
{
cs = new ChannelSet();
amfChannel = new AMFChannel("my-longpolling-amf",serverSTUB + "/RiaService" + "/messagebroker/amflongpolling");
cs.addChannel(amfChannel);
}
public function checkAPIVersion(event:ResultEvent = null, token:Object = null):void
{
but.label = "checkAPIVersion Success";
}
private function handleLoginFault(event:FaultEvent = null, token:Object = null):void
{
but.label = "Fault";
}
protected function login(event:MouseEvent=null):void
{
var token:AsyncToken = cs.login('rbirsan'.toUpperCase(), "ThisISWork?");
token.addResponder( new AsyncResponder(checkAPIVersion, handleLoginFault));
}
]]>
</fx:Script>
<mx:Button label="Login!" id="but" width="200" click="login(event)" />
</mx:Application>
Thank you,
Radu
--
Carlos Rovira
http://about.me/carlosrovira<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C1c64482358ee410406d408d67caecb19%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833487513053128&sdata=L2EEn42ISRv6I%2Fs5UdKRNSpx0%2F0n%2BHkx5BYd%2Bi8TeJI%3D&reserved=0>
--
Carlos Rovira
http://about.me/carlosrovira<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C1c64482358ee410406d408d67caecb19%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833487513053128&sdata=L2EEn42ISRv6I%2Fs5UdKRNSpx0%2F0n%2BHkx5BYd%2Bi8TeJI%3D&reserved=0>
Re: BlazeDS ChanelSet login convert to Royale
Posted by Greg Dove <gr...@gmail.com>.
Hi Alex,
I can answer that. It's not customer approval. The changes are for
AMFBinaryData mainly. But I put in a bunch of custom stuff - which
represent an incomplete and custom IExternalizable support that only
targets ArrayCollection/ArrayList for now.
I need to remove that, and re-implement as a general solution (preferably
retaining some opt-in/PAYG support for the 'custom' approach we are using
which is good for transition management between legacy code and
royale-specific work )
On Fri, Jan 18, 2019 at 7:53 AM Alex Harui <ah...@adobe.com> wrote:
> Carlos, why do you need your customer’s approval to commit fixes for
> RemoteObject? The sooner you can commit those changes, the better it will
> be for the community, IMO.
>
>
>
> -Alex
>
>
>
> *From: *Carlos Rovira <ca...@apache.org>
> *Reply-To: *"users@royale.apache.org" <us...@royale.apache.org>
> *Date: *Thursday, January 17, 2019 at 7:48 AM
> *To: *"users@royale.apache.org" <us...@royale.apache.org>
> *Subject: *Re: BlazeDS ChanelSet login convert to Royale
>
>
>
> Hi Radu,
>
>
>
> we'll do at some time, but that would be when our client want to show it
> into public, so this could be not soon...As he give us green flag, hope to
> share it since I think it's becoming very cool Apache Royale App :)
>
>
>
> El jue., 17 ene. 2019 a las 16:17, radu birsan (<ra...@gmail.com>)
> escribió:
>
> Hi Carlos,
>
>
>
> Thank you for your effort. Having a complex AMF application ported to
> Royal would encourage us to start porting our app.
>
> Hope you can share a sample of the finished product.
>
>
>
> Thank you,
>
> Radu
>
>
>
> On Thu, Jan 17, 2019 at 4:51 PM Carlos Rovira <ca...@apache.org>
> wrote:
>
> Hi Radu,
>
>
>
> this is actually working in Royale. Being said that We (Greg and I) have
> some fixes for RemoteObject that still didn't put on Apache Royale. Will
> upload soon as we end our migration (hopefully 1-2 weeks from now). But you
> can start trying a simple example.
>
>
>
> I recomend you to create a try the following test app :
>
>
>
> Java part:
>
>
> https://github.com/apache/royale-asjs/tree/develop/examples/amf/SampleAmfWebApp
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Ftree%2Fdevelop%2Fexamples%2Famf%2FSampleAmfWebApp&data=02%7C01%7Caharui%40adobe.com%7C26ecd56fa26246019d4a08d67c932b84%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833368896446789&sdata=5CRYHcET0cDH1kSVoHTk703wKrQWZfqS4A3hiIvoPOE%3D&reserved=0>
>
>
>
> Royale client:
>
>
> https://github.com/apache/royale-asjs/tree/develop/examples/mxroyale/RemoteObjectAMFTest
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Ftree%2Fdevelop%2Fexamples%2Fmxroyale%2FRemoteObjectAMFTest&data=02%7C01%7Caharui%40adobe.com%7C26ecd56fa26246019d4a08d67c932b84%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833368896446789&sdata=S2p%2BKnPxr%2BE5aSjuKbfTe2sVytn%2Ff73Zor46pMKy2ak%3D&reserved=0>
>
>
>
> and check this:
>
>
> https://github.com/apache/royale-asjs/wiki/Apache-Royale-communication-with-AMF-and-RemoteObject
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FApache-Royale-communication-with-AMF-and-RemoteObject&data=02%7C01%7Caharui%40adobe.com%7C26ecd56fa26246019d4a08d67c932b84%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833368896446789&sdata=tKqP1c5mri1oH8i9BR9ZAAxnoDSANs%2F%2BDkM7UoqOxgY%3D&reserved=0>
>
>
>
> things like turn enable-small-messages to false are very important to
> have success
>
>
>
> Just let you know that we are migrating a flex application using Jewel and
> MX RemoteObject and we are receiving/sending very complex graphs with AMF
> successfully.
>
> As we get some free time (hopefully 2-3 weeks from now), Greg had in mind
> to complete RemoteObject implementation with enable-small-messages support
> too.
>
>
>
> thanks
>
>
>
>
>
> El jue., 17 ene. 2019 a las 13:08, radu birsan (<ra...@gmail.com>)
> escribió:
>
> Hello,
>
>
>
> I have a simple flex login module that uses mx:ChannelSet. Any idea on
> how to make this work with Roylale js.
>
>
>
> *<?xml* version="1.0" encoding="utf-8"?>
>
> <mx:Application xmlns:fx="http://ns.adobe.com/mxml/2009 <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009&data=02%7C01%7Caharui%40adobe.com%7C26ecd56fa26246019d4a08d67c932b84%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833368896446789&sdata=7i9gA%2B9InPufIPQrDwwVqYaYqdEWeGMbQ2VurI4IM0w%3D&reserved=0>"
>
> xmlns:mx="library://ns.adobe.com/flex/mx <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fflex%2Fmx&data=02%7C01%7Caharui%40adobe.com%7C26ecd56fa26246019d4a08d67c932b84%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833368896446789&sdata=zWx7Fv5qT20D3DE8VkX%2FQiIck26OwX67LvlhYaWL42k%3D&reserved=0>" creationComplete="main()">
>
> <fx:Script>
>
> <![CDATA[
>
> import mx.messaging.ChannelSet;
>
> import mx.messaging.channels.AMFChannel;
>
> import mx.messaging.channels.StreamingAMFChannel;
>
> import mx.messaging.messages.CommandMessage;
>
> import mx.rpc.AsyncResponder;
>
> import mx.rpc.AsyncToken;
>
> import mx.rpc.events.FaultEvent;
>
> import mx.rpc.events.ResultEvent;
>
> public var cs:ChannelSet=null;
>
> private var amfChannel:AMFChannel;
>
> public var serverSTUB:String = "http://voip-manager.spherecom.com:9080 <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fvoip-manager.spherecom.com%3A9080&data=02%7C01%7Caharui%40adobe.com%7C26ecd56fa26246019d4a08d67c932b84%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833368896446789&sdata=%2BZDM85dAAz2CdUQPeWoE%2B3arNWvixCXXm%2ByC%2BZOo594%3D&reserved=0>"
>
>
>
> public function main():void
>
> {
>
> cs = new ChannelSet();
>
> amfChannel = new AMFChannel("my-longpolling-amf",serverSTUB + "/RiaService" + "/messagebroker/amflongpolling");
>
> cs.addChannel(amfChannel);
>
> }
>
>
>
> public function checkAPIVersion(event:ResultEvent = null, token:Object = null):void
>
> {
>
> but.label = "checkAPIVersion Success";
>
> }
>
>
>
> private function handleLoginFault(event:FaultEvent = null, token:Object = null):void
>
> {
>
> but.label = "Fault";
>
> }
>
>
>
> protected function login(event:MouseEvent=null):void
>
> {
>
> var token:AsyncToken = cs.login('rbirsan'.toUpperCase(), "ThisISWork?");
>
> token.addResponder( new AsyncResponder(checkAPIVersion, handleLoginFault));
>
> }
>
>
>
>
>
>
>
> ]]>
>
> </fx:Script>
>
> <mx:Button label="Login!" id="but" width="200" click="login(event)" />
>
> </mx:Application>
>
>
>
> Thank you,
>
> Radu
>
>
>
>
> --
>
> Carlos Rovira
>
> http://about.me/carlosrovira
> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C26ecd56fa26246019d4a08d67c932b84%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833368896446789&sdata=zTA4%2B0IcIqQ1Q5XZPg5VzkP%2Fqp%2B%2F9%2B%2FXNsc3jVXb3%2F8%3D&reserved=0>
>
>
>
>
>
>
> --
>
> Carlos Rovira
>
> http://about.me/carlosrovira
> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C26ecd56fa26246019d4a08d67c932b84%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833368896446789&sdata=zTA4%2B0IcIqQ1Q5XZPg5VzkP%2Fqp%2B%2F9%2B%2FXNsc3jVXb3%2F8%3D&reserved=0>
>
>
>
Re: BlazeDS ChanelSet login convert to Royale
Posted by Alex Harui <ah...@adobe.com>.
Carlos, why do you need your customer’s approval to commit fixes for RemoteObject? The sooner you can commit those changes, the better it will be for the community, IMO.
-Alex
From: Carlos Rovira <ca...@apache.org>
Reply-To: "users@royale.apache.org" <us...@royale.apache.org>
Date: Thursday, January 17, 2019 at 7:48 AM
To: "users@royale.apache.org" <us...@royale.apache.org>
Subject: Re: BlazeDS ChanelSet login convert to Royale
Hi Radu,
we'll do at some time, but that would be when our client want to show it into public, so this could be not soon...As he give us green flag, hope to share it since I think it's becoming very cool Apache Royale App :)
El jue., 17 ene. 2019 a las 16:17, radu birsan (<ra...@gmail.com>>) escribió:
Hi Carlos,
Thank you for your effort. Having a complex AMF application ported to Royal would encourage us to start porting our app.
Hope you can share a sample of the finished product.
Thank you,
Radu
On Thu, Jan 17, 2019 at 4:51 PM Carlos Rovira <ca...@apache.org>> wrote:
Hi Radu,
this is actually working in Royale. Being said that We (Greg and I) have some fixes for RemoteObject that still didn't put on Apache Royale. Will upload soon as we end our migration (hopefully 1-2 weeks from now). But you can start trying a simple example.
I recomend you to create a try the following test app :
Java part:
https://github.com/apache/royale-asjs/tree/develop/examples/amf/SampleAmfWebApp<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Ftree%2Fdevelop%2Fexamples%2Famf%2FSampleAmfWebApp&data=02%7C01%7Caharui%40adobe.com%7C26ecd56fa26246019d4a08d67c932b84%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833368896446789&sdata=5CRYHcET0cDH1kSVoHTk703wKrQWZfqS4A3hiIvoPOE%3D&reserved=0>
Royale client:
https://github.com/apache/royale-asjs/tree/develop/examples/mxroyale/RemoteObjectAMFTest<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Ftree%2Fdevelop%2Fexamples%2Fmxroyale%2FRemoteObjectAMFTest&data=02%7C01%7Caharui%40adobe.com%7C26ecd56fa26246019d4a08d67c932b84%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833368896446789&sdata=S2p%2BKnPxr%2BE5aSjuKbfTe2sVytn%2Ff73Zor46pMKy2ak%3D&reserved=0>
and check this:
https://github.com/apache/royale-asjs/wiki/Apache-Royale-communication-with-AMF-and-RemoteObject<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FApache-Royale-communication-with-AMF-and-RemoteObject&data=02%7C01%7Caharui%40adobe.com%7C26ecd56fa26246019d4a08d67c932b84%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833368896446789&sdata=tKqP1c5mri1oH8i9BR9ZAAxnoDSANs%2F%2BDkM7UoqOxgY%3D&reserved=0>
things like turn enable-small-messages to false are very important to have success
Just let you know that we are migrating a flex application using Jewel and MX RemoteObject and we are receiving/sending very complex graphs with AMF successfully.
As we get some free time (hopefully 2-3 weeks from now), Greg had in mind to complete RemoteObject implementation with enable-small-messages support too.
thanks
El jue., 17 ene. 2019 a las 13:08, radu birsan (<ra...@gmail.com>>) escribió:
Hello,
I have a simple flex login module that uses mx:ChannelSet. Any idea on how to make this work with Roylale js.
<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:fx="http://ns.adobe.com/mxml/2009<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009&data=02%7C01%7Caharui%40adobe.com%7C26ecd56fa26246019d4a08d67c932b84%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833368896446789&sdata=7i9gA%2B9InPufIPQrDwwVqYaYqdEWeGMbQ2VurI4IM0w%3D&reserved=0>"
xmlns:mx="library://ns.adobe.com/flex/mx<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fflex%2Fmx&data=02%7C01%7Caharui%40adobe.com%7C26ecd56fa26246019d4a08d67c932b84%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833368896446789&sdata=zWx7Fv5qT20D3DE8VkX%2FQiIck26OwX67LvlhYaWL42k%3D&reserved=0>" creationComplete="main()">
<fx:Script>
<![CDATA[
import mx.messaging.ChannelSet;
import mx.messaging.channels.AMFChannel;
import mx.messaging.channels.StreamingAMFChannel;
import mx.messaging.messages.CommandMessage;
import mx.rpc.AsyncResponder;
import mx.rpc.AsyncToken;
import mx.rpc.events.FaultEvent;
import mx.rpc.events.ResultEvent;
public var cs:ChannelSet=null;
private var amfChannel:AMFChannel;
public var serverSTUB:String = "http://voip-manager.spherecom.com:9080<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fvoip-manager.spherecom.com%3A9080&data=02%7C01%7Caharui%40adobe.com%7C26ecd56fa26246019d4a08d67c932b84%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833368896446789&sdata=%2BZDM85dAAz2CdUQPeWoE%2B3arNWvixCXXm%2ByC%2BZOo594%3D&reserved=0>"
public function main():void
{
cs = new ChannelSet();
amfChannel = new AMFChannel("my-longpolling-amf",serverSTUB + "/RiaService" + "/messagebroker/amflongpolling");
cs.addChannel(amfChannel);
}
public function checkAPIVersion(event:ResultEvent = null, token:Object = null):void
{
but.label = "checkAPIVersion Success";
}
private function handleLoginFault(event:FaultEvent = null, token:Object = null):void
{
but.label = "Fault";
}
protected function login(event:MouseEvent=null):void
{
var token:AsyncToken = cs.login('rbirsan'.toUpperCase(), "ThisISWork?");
token.addResponder( new AsyncResponder(checkAPIVersion, handleLoginFault));
}
]]>
</fx:Script>
<mx:Button label="Login!" id="but" width="200" click="login(event)" />
</mx:Application>
Thank you,
Radu
--
Carlos Rovira
http://about.me/carlosrovira<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C26ecd56fa26246019d4a08d67c932b84%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833368896446789&sdata=zTA4%2B0IcIqQ1Q5XZPg5VzkP%2Fqp%2B%2F9%2B%2FXNsc3jVXb3%2F8%3D&reserved=0>
--
Carlos Rovira
http://about.me/carlosrovira<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C26ecd56fa26246019d4a08d67c932b84%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636833368896446789&sdata=zTA4%2B0IcIqQ1Q5XZPg5VzkP%2Fqp%2B%2F9%2B%2FXNsc3jVXb3%2F8%3D&reserved=0>
Re: BlazeDS ChanelSet login convert to Royale
Posted by Carlos Rovira <ca...@apache.org>.
Hi Radu,
we'll do at some time, but that would be when our client want to show it
into public, so this could be not soon...As he give us green flag, hope to
share it since I think it's becoming very cool Apache Royale App :)
El jue., 17 ene. 2019 a las 16:17, radu birsan (<ra...@gmail.com>)
escribió:
> Hi Carlos,
>
> Thank you for your effort. Having a complex AMF application ported to
> Royal would encourage us to start porting our app.
> Hope you can share a sample of the finished product.
>
> Thank you,
> Radu
>
> On Thu, Jan 17, 2019 at 4:51 PM Carlos Rovira <ca...@apache.org>
> wrote:
>
>> Hi Radu,
>>
>> this is actually working in Royale. Being said that We (Greg and I) have
>> some fixes for RemoteObject that still didn't put on Apache Royale. Will
>> upload soon as we end our migration (hopefully 1-2 weeks from now). But you
>> can start trying a simple example.
>>
>> I recomend you to create a try the following test app :
>>
>> Java part:
>>
>> https://github.com/apache/royale-asjs/tree/develop/examples/amf/SampleAmfWebApp
>>
>> Royale client:
>>
>> https://github.com/apache/royale-asjs/tree/develop/examples/mxroyale/RemoteObjectAMFTest
>>
>> and check this:
>>
>> https://github.com/apache/royale-asjs/wiki/Apache-Royale-communication-with-AMF-and-RemoteObject
>>
>> things like turn enable-small-messages to false are very important to
>> have success
>>
>> Just let you know that we are migrating a flex application using Jewel
>> and MX RemoteObject and we are receiving/sending very complex graphs with
>> AMF successfully.
>> As we get some free time (hopefully 2-3 weeks from now), Greg had in mind
>> to complete RemoteObject implementation with enable-small-messages support
>> too.
>>
>> thanks
>>
>>
>> El jue., 17 ene. 2019 a las 13:08, radu birsan (<ra...@gmail.com>)
>> escribió:
>>
>>> Hello,
>>>
>>> I have a simple flex login module that uses mx:ChannelSet. Any idea
>>> on how to make this work with Roylale js.
>>>
>>> <?xml version="1.0" encoding="utf-8"?><mx:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
>>> xmlns:mx="library://ns.adobe.com/flex/mx" creationComplete="main()">
>>> <fx:Script>
>>> <![CDATA[
>>> import mx.messaging.ChannelSet;
>>> import mx.messaging.channels.AMFChannel;
>>> import mx.messaging.channels.StreamingAMFChannel;
>>> import mx.messaging.messages.CommandMessage;
>>> import mx.rpc.AsyncResponder;
>>> import mx.rpc.AsyncToken;
>>> import mx.rpc.events.FaultEvent;
>>> import mx.rpc.events.ResultEvent;
>>> public var cs:ChannelSet=null;
>>> private var amfChannel:AMFChannel;
>>> public var serverSTUB:String = "http://voip-manager.spherecom.com:9080"
>>>
>>> public function main():void
>>> {
>>> cs = new ChannelSet();
>>> amfChannel = new AMFChannel("my-longpolling-amf",serverSTUB + "/RiaService" + "/messagebroker/amflongpolling");
>>> cs.addChannel(amfChannel);
>>> }
>>>
>>> public function checkAPIVersion(event:ResultEvent = null, token:Object = null):void
>>> {
>>> but.label = "checkAPIVersion Success";
>>> }
>>>
>>> private function handleLoginFault(event:FaultEvent = null, token:Object = null):void
>>> {
>>> but.label = "Fault";
>>> }
>>>
>>> protected function login(event:MouseEvent=null):void
>>> {
>>> var token:AsyncToken = cs.login('rbirsan'.toUpperCase(), "ThisISWork?");
>>> token.addResponder( new AsyncResponder(checkAPIVersion, handleLoginFault));
>>> }
>>>
>>>
>>>
>>> ]]>
>>> </fx:Script>
>>> <mx:Button label="Login!" id="but" width="200" click="login(event)" /></mx:Application>
>>>
>>>
>>> Thank you,
>>> Radu
>>>
>>
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>>
--
Carlos Rovira
http://about.me/carlosrovira
Re: BlazeDS ChanelSet login convert to Royale
Posted by radu birsan <ra...@gmail.com>.
Hi Carlos,
Thank you for your effort. Having a complex AMF application ported to
Royal would encourage us to start porting our app.
Hope you can share a sample of the finished product.
Thank you,
Radu
On Thu, Jan 17, 2019 at 4:51 PM Carlos Rovira <ca...@apache.org>
wrote:
> Hi Radu,
>
> this is actually working in Royale. Being said that We (Greg and I) have
> some fixes for RemoteObject that still didn't put on Apache Royale. Will
> upload soon as we end our migration (hopefully 1-2 weeks from now). But you
> can start trying a simple example.
>
> I recomend you to create a try the following test app :
>
> Java part:
>
> https://github.com/apache/royale-asjs/tree/develop/examples/amf/SampleAmfWebApp
>
> Royale client:
>
> https://github.com/apache/royale-asjs/tree/develop/examples/mxroyale/RemoteObjectAMFTest
>
> and check this:
>
> https://github.com/apache/royale-asjs/wiki/Apache-Royale-communication-with-AMF-and-RemoteObject
>
> things like turn enable-small-messages to false are very important to
> have success
>
> Just let you know that we are migrating a flex application using Jewel and
> MX RemoteObject and we are receiving/sending very complex graphs with AMF
> successfully.
> As we get some free time (hopefully 2-3 weeks from now), Greg had in mind
> to complete RemoteObject implementation with enable-small-messages support
> too.
>
> thanks
>
>
> El jue., 17 ene. 2019 a las 13:08, radu birsan (<ra...@gmail.com>)
> escribió:
>
>> Hello,
>>
>> I have a simple flex login module that uses mx:ChannelSet. Any idea on
>> how to make this work with Roylale js.
>>
>> <?xml version="1.0" encoding="utf-8"?><mx:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
>> xmlns:mx="library://ns.adobe.com/flex/mx" creationComplete="main()">
>> <fx:Script>
>> <![CDATA[
>> import mx.messaging.ChannelSet;
>> import mx.messaging.channels.AMFChannel;
>> import mx.messaging.channels.StreamingAMFChannel;
>> import mx.messaging.messages.CommandMessage;
>> import mx.rpc.AsyncResponder;
>> import mx.rpc.AsyncToken;
>> import mx.rpc.events.FaultEvent;
>> import mx.rpc.events.ResultEvent;
>> public var cs:ChannelSet=null;
>> private var amfChannel:AMFChannel;
>> public var serverSTUB:String = "http://voip-manager.spherecom.com:9080"
>>
>> public function main():void
>> {
>> cs = new ChannelSet();
>> amfChannel = new AMFChannel("my-longpolling-amf",serverSTUB + "/RiaService" + "/messagebroker/amflongpolling");
>> cs.addChannel(amfChannel);
>> }
>>
>> public function checkAPIVersion(event:ResultEvent = null, token:Object = null):void
>> {
>> but.label = "checkAPIVersion Success";
>> }
>>
>> private function handleLoginFault(event:FaultEvent = null, token:Object = null):void
>> {
>> but.label = "Fault";
>> }
>>
>> protected function login(event:MouseEvent=null):void
>> {
>> var token:AsyncToken = cs.login('rbirsan'.toUpperCase(), "ThisISWork?");
>> token.addResponder( new AsyncResponder(checkAPIVersion, handleLoginFault));
>> }
>>
>>
>>
>> ]]>
>> </fx:Script>
>> <mx:Button label="Login!" id="but" width="200" click="login(event)" /></mx:Application>
>>
>>
>> Thank you,
>> Radu
>>
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>
Re: BlazeDS ChanelSet login convert to Royale
Posted by Carlos Rovira <ca...@apache.org>.
Hi Radu,
this is actually working in Royale. Being said that We (Greg and I) have
some fixes for RemoteObject that still didn't put on Apache Royale. Will
upload soon as we end our migration (hopefully 1-2 weeks from now). But you
can start trying a simple example.
I recomend you to create a try the following test app :
Java part:
https://github.com/apache/royale-asjs/tree/develop/examples/amf/SampleAmfWebApp
Royale client:
https://github.com/apache/royale-asjs/tree/develop/examples/mxroyale/RemoteObjectAMFTest
and check this:
https://github.com/apache/royale-asjs/wiki/Apache-Royale-communication-with-AMF-and-RemoteObject
things like turn enable-small-messages to false are very important to have
success
Just let you know that we are migrating a flex application using Jewel and
MX RemoteObject and we are receiving/sending very complex graphs with AMF
successfully.
As we get some free time (hopefully 2-3 weeks from now), Greg had in mind
to complete RemoteObject implementation with enable-small-messages support
too.
thanks
El jue., 17 ene. 2019 a las 13:08, radu birsan (<ra...@gmail.com>)
escribió:
> Hello,
>
> I have a simple flex login module that uses mx:ChannelSet. Any idea on
> how to make this work with Roylale js.
>
> <?xml version="1.0" encoding="utf-8"?><mx:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
> xmlns:mx="library://ns.adobe.com/flex/mx" creationComplete="main()">
> <fx:Script>
> <![CDATA[
> import mx.messaging.ChannelSet;
> import mx.messaging.channels.AMFChannel;
> import mx.messaging.channels.StreamingAMFChannel;
> import mx.messaging.messages.CommandMessage;
> import mx.rpc.AsyncResponder;
> import mx.rpc.AsyncToken;
> import mx.rpc.events.FaultEvent;
> import mx.rpc.events.ResultEvent;
> public var cs:ChannelSet=null;
> private var amfChannel:AMFChannel;
> public var serverSTUB:String = "http://voip-manager.spherecom.com:9080"
>
> public function main():void
> {
> cs = new ChannelSet();
> amfChannel = new AMFChannel("my-longpolling-amf",serverSTUB + "/RiaService" + "/messagebroker/amflongpolling");
> cs.addChannel(amfChannel);
> }
>
> public function checkAPIVersion(event:ResultEvent = null, token:Object = null):void
> {
> but.label = "checkAPIVersion Success";
> }
>
> private function handleLoginFault(event:FaultEvent = null, token:Object = null):void
> {
> but.label = "Fault";
> }
>
> protected function login(event:MouseEvent=null):void
> {
> var token:AsyncToken = cs.login('rbirsan'.toUpperCase(), "ThisISWork?");
> token.addResponder( new AsyncResponder(checkAPIVersion, handleLoginFault));
> }
>
>
>
> ]]>
> </fx:Script>
> <mx:Button label="Login!" id="but" width="200" click="login(event)" /></mx:Application>
>
>
> Thank you,
> Radu
>
--
Carlos Rovira
http://about.me/carlosrovira