How about moving BlazeDS and parts of the Mavenizer to Royale?

[Christofer Dutz <ch...@c-ware.de>]

Hi folks,

As I’m currently starting to dig myself into migrating my stuff from Flex to Royale, I noticed that BlazeDS could use an update.

So I was thinking: This is actually the last part of the Flex project that might still have a future. So how about we move the BlazeDS component to Royale?
Perhaps even rename it to something like RoyaleDS? I would also like to ask the Spring folks if we could possibly take over the retired Spring Flex module
and build a Spring Royale module from that, but as part of the Royale project.

While at it I think in order to build the Framework and the Compiler with SWF support, we still need some Adobe artifacts.
That’s why we’re still using the Flex Mavenizer.

So how about taking part of that code and have a Royale version (Just for the Flash and Air libs)?

Chris

Re: How about moving BlazeDS and parts of the Mavenizer to Royale?

[Carlos Rovira <ca...@apache.org>]

Hi Chris,

I think it's a very good idea. Royale deserves to have all its key pieces
and as Flex had Flex Data Services then Royale having Royale Data Services
should be considered as a powerful solution with a backend middleware.
I was always thinking that having AMF/RemoteObject but BlazeDS out of
Royale is something strange. It's like to have half of the
implementation/solution.
Also since we need some updates that keep it coming with the rest of
royale, I think that would be the best
Also trying to bring Spring Flex Integration will be very needed so we can
take over it. We use SFI in all our apps in Codeoscopic with Spring.

So +1 to both.

Thanks for proposing

Carlos


El sáb., 18 jul. 2020 a las 15:26, Christofer Dutz (<
christofer.dutz@c-ware.de>) escribió:

> Hi folks,
>
> As I’m currently starting to dig myself into migrating my stuff from Flex
> to Royale, I noticed that BlazeDS could use an update.
>
> So I was thinking: This is actually the last part of the Flex project that
> might still have a future. So how about we move the BlazeDS component to
> Royale?
> Perhaps even rename it to something like RoyaleDS? I would also like to
> ask the Spring folks if we could possibly take over the retired Spring Flex
> module
> and build a Spring Royale module from that, but as part of the Royale
> project.
>
> While at it I think in order to build the Framework and the Compiler with
> SWF support, we still need some Adobe artifacts.
> That’s why we’re still using the Flex Mavenizer.
>
> So how about taking part of that code and have a Royale version (Just for
> the Flash and Air libs)?
>
> Chris
>
>

-- 
Carlos Rovira
http://about.me/carlosrovira