project using nightly build

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

project using nightly build

Olivier Dion

Looks like these were added on the nightly build JS version

 

                import org.apache.royale.net.events.ResultEvent;

                import org.apache.royale.net.events.FaultEvent;

 

and idea when these events will be completed?

 

Right now, I am not sure what to use with HTTPService when the first version will be released

 

Thanks!

Reply | Threaded
Open this post in threaded view
|

Re: project using nightly build

Alex Harui-2

Hi Oliver,

 

Unlike Apache Flex, Apache Royale offers a choice of component sets.  There is a basic org.apache.royale.net.HTTPService with pay-as-you-go (PAYG) functionality.  There is an MXRoyale HTTPService that tries to emulate the Flex HTTPService.  If you are migrating Flex code, you will have to tweak your code more to use the basic version.

 

The basic HTTPService does not dispatch org.apache.royale.net.events.ResultEvent or FaultEvent, nor does it support Operations.  That makes it much more PAYG and lightweight, but then you have more work to do when migrating.

 

The MXRoyale HTTPService should support Operations that dispatch mx.rpc.events.ResultEvent.

 

HTH,

-Alex

 

 

From: Olivier Dion <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Wednesday, May 15, 2019 at 10:21 AM
To: "[hidden email]" <[hidden email]>
Subject: project using nightly build

 

Looks like these were added on the nightly build JS version

 

                import org.apache.royale.net.events.ResultEvent;

                import org.apache.royale.net.events.FaultEvent;

 

and idea when these events will be completed?

 

Right now, I am not sure what to use with HTTPService when the first version will be released

 

Thanks!

Reply | Threaded
Open this post in threaded view
|

RE: project using nightly build

Olivier Dion

Correct but in the nightly builds, I can’t access

 

    import mx.rpc.http.HTTPService;

    import mx.rpc.events.ResultEvent;

    import mx.rpc.events.FaultEvent;

 

should I be expecting these to go away?

 

 

From: Alex Harui <[hidden email]>
Sent: Wednesday, May 15, 2019 1:58 PM
To: [hidden email]
Subject: Re: project using nightly build

 

Hi Oliver,

 

Unlike Apache Flex, Apache Royale offers a choice of component sets.  There is a basic org.apache.royale.net.HTTPService with pay-as-you-go (PAYG) functionality.  There is an MXRoyale HTTPService that tries to emulate the Flex HTTPService.  If you are migrating Flex code, you will have to tweak your code more to use the basic version.

 

The basic HTTPService does not dispatch org.apache.royale.net.events.ResultEvent or FaultEvent, nor does it support Operations.  That makes it much more PAYG and lightweight, but then you have more work to do when migrating.

 

The MXRoyale HTTPService should support Operations that dispatch mx.rpc.events.ResultEvent.

 

HTH,

-Alex

 

 

From: Olivier Dion <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Wednesday, May 15, 2019 at 10:21 AM
To: "[hidden email]" <[hidden email]>
Subject: project using nightly build

 

Looks like these were added on the nightly build JS version

 

                import org.apache.royale.net.events.ResultEvent;

                import org.apache.royale.net.events.FaultEvent;

 

and idea when these events will be completed?

 

Right now, I am not sure what to use with HTTPService when the first version will be released

 

Thanks!

Reply | Threaded
Open this post in threaded view
|

Re: project using nightly build

Alex Harui-2

I would expect them to stay and work pretty much like they did in Flex.

 

In the nightly builds, you have to use the compiler option

 

+configname=flex

 

(yes, that’s a “+” and not a “-“) and the console output should show it loads flex-config.xml instead of royale-config.xml

 

HTH,

-Alex

 

From: Olivier Dion <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Wednesday, May 15, 2019 at 11:51 AM
To: "[hidden email]" <[hidden email]>
Subject: RE: project using nightly build

 

Correct but in the nightly builds, I can’t access

 

    import mx.rpc.http.HTTPService;

    import mx.rpc.events.ResultEvent;

    import mx.rpc.events.FaultEvent;

 

should I be expecting these to go away?

 

 

From: Alex Harui <[hidden email]>
Sent: Wednesday, May 15, 2019 1:58 PM
To: [hidden email]
Subject: Re: project using nightly build

 

Hi Oliver,

 

Unlike Apache Flex, Apache Royale offers a choice of component sets.  There is a basic org.apache.royale.net.HTTPService with pay-as-you-go (PAYG) functionality.  There is an MXRoyale HTTPService that tries to emulate the Flex HTTPService.  If you are migrating Flex code, you will have to tweak your code more to use the basic version.

 

The basic HTTPService does not dispatch org.apache.royale.net.events.ResultEvent or FaultEvent, nor does it support Operations.  That makes it much more PAYG and lightweight, but then you have more work to do when migrating.

 

The MXRoyale HTTPService should support Operations that dispatch mx.rpc.events.ResultEvent.

 

HTH,

-Alex

 

 

From: Olivier Dion <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Wednesday, May 15, 2019 at 10:21 AM
To: "[hidden email]" <[hidden email]>
Subject: project using nightly build

 

Looks like these were added on the nightly build JS version

 

                import org.apache.royale.net.events.ResultEvent;

                import org.apache.royale.net.events.FaultEvent;

 

and idea when these events will be completed?

 

Right now, I am not sure what to use with HTTPService when the first version will be released

 

Thanks!