Re: Migrating Enterprise Flex Application

I downloaded the nightly build and it is working fine in the nightly build. -- Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

Alex, are you able to view the details in the error page that I have attached? -- Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

Error.PNG Please see the attached error that shows the javascript error. -- Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

Will get to this as soon as I can. Here is another issue that I am having. I am trying to take a look at some of the samples shipped with 0.9.3 release. I am seeing issues while running some of the examples. Please see the attached zip containing the screenshot showing the error while running the

Re: Migrating Enterprise Flex Application

I always get the compile error, but many times it goes ahead and creates the js distribution and the component that I am trying to use works fine. But many times it does not work as expected even though the js distribution gets built successfully. -- Sent from:

Re: Migrating Enterprise Flex Application

I am trying the package paths for swc for the first time. I use it quite a lot in the Flex world. A bit confused about the -js-source-path option. I don't see that option in mxmlc. Am I missing something? -- Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

I am using the package paths for the first time. I use it quite a lot in the Flex world. Bit confused about your -js-source-path. I don't see this option in the mxmlc compiler. Am I missing something? -- Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

Here is another js compiler error that I am trying to resolve. My mxml contains the following fragment. http://ns.adobe.com/mxml/2009; xmlns:mx="library://ns.apache.org/royale/mx" xmlns:js="library://ns.apache.org/royale/basic"

Re: Migrating Enterprise Flex Application

Thank you. I will give it a try commenting out resource bundle usage. -- Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

I am trying to compile a simple mxml file to js using mxmlc. Here is the mxml fie. http://ns.adobe.com/mxml/2009; xmlns:ss="com.infogix.iitap.component.scheduler.view.*"

Re: Migrating Enterprise Flex Application

My current code uses IDataInput/iDataOutput classes in Flash util. What classes can I use to replace them? I saw IBinaryDataOutput in Royale, but it does not have the writeObject() and readObject() apis. -- Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

Tried with the latest build. The earlier error is gone. Getting another resource bundle error now. Do you have to comment out more code? Using Royale Compiler codebase: C:\devenv\GitHub\apache-royale-0.9.3\royale-asjs \js\bin\..\.. Using Royale SDK:

Re: Migrating Enterprise Flex Application

Thank you Carlos for the input. I am trying to migrate a sample BlazeDS application ( which is working fine in Flex ) to Royale in order to identify the steps/changes needed. Here is my orginal mxml that is working in Flex. http://www.adobe.com/2006/mxml; layout="absolute">

Re: Migrating Enterprise Flex Application

Tried js/bin/mxmlc. Getting the following error now. C:\devenv\BlazeDSRemoteObjects\BlazeDsExample\src>C:\devenv\GitHub\royale-asjs/j s/bin/mxmlc -compiler.source-path=C:\devenv\BlazeDSRemoteObjects\BlazeDsExample\ src C:\devenv\BlazeDSRemoteObjects\BlazeDsExample\src/BlazeDsExample.mxml Using

Re: Migrating Enterprise Flex Application

I tried to run the Royale mxmlc compiler using the below command and it errors out. C:\devenv\BlazeDSRemoteObjects\BlazeDsExample\src>C:\devenv\GitHub\royale-asjs/b in/mxmlc -compiler.source-path=C:\devenv\BlazeDSRemoteObjects\BlazeDsExample\src

Re: Migrating Enterprise Flex Application

How do I migrate the flash.util, flash.xml, flashx.text etc APIs in my existing application? -- Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

I have generated API reports for another Flex application that I am trying to migrate to Royale. Please see the attached reports. reportFlexACRRepository.txt reportFlexDataMart.txt

Re: Migrating Enterprise Flex Application

I just tried to run my application gradle script to build. I modified the FLEX_HOME in the script to point to the ROYALE install home. I have the ROYALE installed under C:\devenv\GitHub folder. The output is attached. RoyaleCompileOutput.txt

Re: Migrating Enterprise Flex Application

My application consists of a number of components. Each of these components has got a UI portion which is in Flex. For e.g I have got components like FlexUIPlatform, Directory, ProcessModel etc. Here FlexUIPlatform is the lowest in the hierarchy and does not have any dependency on other components

Re: Migrating Enterprise Flex Application

Great. I will take a look. I am starting to get the application compiledusing royale js. Should I use compc or mxmlc? Can you provide a sample command for me to get started? -- Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

Very helpful posts indeed. Can you tell me a couple of classic emulation examples that I can look at? I am hoping to take a look at them and understand the pattern. -- Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

I believe I have convinced the management to go with Apache Royale as part the Deflexing effort of our Flex applications. The first project is going to be very important and they are going to monitor it closely. I want to be realistic and figure out the best approach and I need your help on

Re: Migrating Enterprise Flex Application

Spot on. The directory was not getting configured because I had the GOOG_HOME environment variable already set ( pointing to a different folder ). I deleted it and everything started working fine. -- Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

I had the source that I had downloaded a week or so ago. I was able to compile that source and use it successfully. I implemented the stub for an emulation component and was able to get it working after the build. So the issue appears to be in the latest branch ( for me at least ) -- Sent from:

Re: Migrating Enterprise Flex Application

I am using Java 1.8.0_161 for compiling and running. -- Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

It looks like the a couple of JS files are generated before the process fails. Compile.PNG -- Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

I switched to the MxRoyale branch and did the build and it the build was successful. Then I ran the same command to transpile. C:\devenv\GitHub\royale-asjs\royale-asjs\js\bin\mxmlc -targets=JSRoyale

Re: Migrating Enterprise Flex Application

No I am using the develop branch. I will switch to feature/MxRoyale and see. Thank you. -- Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

Met with the Management. They insisted on POC including the development of at least one emulation component by me in order to proceed with the project. I am starting on the POC work now. I got the Apache-Royale source tree cloned and did the build without any issues. I just tried to transpile a

Re: Migrating Enterprise Flex Application

I have a meeting with the management tomorrow. I will try to convince them without spending time on the POC if possible. Here is the high level plan that I am going to present to them. The plan is to perform the migration component by component using emulation wherever needed. I will also

Re: Migrating Enterprise Flex Application

Can I go ahead and create an issue with the list of APIs to be emulated? I am thinking the flash,mx and Spark components from the below list needs to be emulated. I am not sure about the com.adobe classes in the list. I did a quick search for the JS implementation for the 3rd party libraries that

Re: Migrating Enterprise Flex Application

I am trying to compile my mxml and action script sources. I am using the latest emulation build. So I expect most of my source code to compile because of the emulation build that I am compiling against. I expect to see compile errors if any of the MX/SPARK components that I am using is not

Re: Migrating Enterprise Flex Application

I have uploaded 2 console outputs. console.out consoleAS.out The first output ( console.out ) got generated when I tried to compile one of

Re: Migrating Enterprise Flex Application

Good point. I had tried to compile one component. It seems to have worked fine. No errors. But did not generate the JS output. I am going back and trying small sets now. The first set worked just fine and generated the JS output successfully. -- Sent from:

Re: Migrating Enterprise Flex Application

Sorry. I missed Alex's response. This is exactly what I was looking for. Let me work on it. Great. Thank you. -- Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

I agree with you on the important points that you brought up. I have around 1767 action scripts ( mainly controller code, POJOS and business logic ) and 647 mxml ( mainly UI stuff ) in my application. I was hoping to get most of my action scripts converted to javascript. This is my initial task. I

Re: Migrating Enterprise Flex Application

Thank you Carlos for your input. It is not a bad idea. But I am trying to convince myself first. After going through the Royale docs, I had communicated to the management that a lot of our code ( probably 60% ) would get migrated to JS without much effort ( just by using the Royale compiler ).

Re: Migrating Enterprise Flex Application

Thank you for the quick response. The management's confidence level is low at the moment. They are considering ReactJS to move the UI to. I am the product owner and I strongly believe it is going to take a lot longer to move to React. They might get convinced if I can show one simple application

Re: Migrating Enterprise Flex Application

The management has asked me to do a POC and demo it to them before they can fund the migration project. Can I just convert couple of screens in the existing Flex web app to Apache Royale JS? Do you think it is doable in 2 weeks? What are the step that I should take to make this happen? Please

Re: Migrating Enterprise Flex Application

So most of the components listed below that are in the mx and spark packages would have to be implemented. Some of the components may have been defined ( the skeletons ) but not implemented. I can download the latest Royale source and take a look to figure this out. Please correct me if I am

Re: Migrating Enterprise Flex Application

Most of the api's listed in the report are home grown ( not 3rd party ). I guess we need to rewrite then in JS. The true 3rd party apis are alivepdf and granite libraries. I believe there are counterparts in the JS world. I need to do more research. I was reading the doc on writing emulation

Re: Migrating Enterprise Flex Application

I generated the api reports for the components in my application. Please see the attached reports. Please review them. What should be my next steps? reportControlMgmt.txt reportDashboards.txt

Re: Migrating Enterprise Flex Application

I fixed the compile errors and generated the api report for my first component. reportFlexUIPlatform.txt . Please review it and let me know your comments. I will start working on generating the api reports

Re: Migrating Enterprise Flex Application

I skipped the offending mxml and the compiling of my first component completed. It is giving me a bunch of errors. Should I try to fix these compile errors or can I just rerun with the api-report option to generate the report? -- Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

The name of the mxml file is PopupTemplate.mxml. I have attached the ResizableTitleWindow.as -- Sent from: http://apache-royale-development.20373.n8.nabble.com/

RE: Migrating Enterprise Flex Application

I stripped it down to But no luck. I tried changing the name space as well, but didn't work. ResizableTitleWindow.as compiles fine. Thinking of replacing this panel with some other kind of panel and see if I can move along. -- Sent from:

RE: Migrating Enterprise Flex Application

I narrowed the compiler hanging issue down to one mxml file in my source. It is hanging during the compilation of the below mxml file. I removed this file from the source and the compiling seems to be fine. Here is the mxml file for your reference. I couldn't notice anything that could cause the

Re: Migrating Enterprise Flex Application

I got the nightly build apache-royale-0.9.3-bin-js-swf.zip on June 22. It looks like the issue may not be related to the flex-config.xml. I tried to compile another component source and it went ahead and compiled the component giving a bunch of compile errors. It did not hang though. -- Sent

Re: Migrating Enterprise Flex Application

Another road block. The command to compile the first component using compc is the following. C:\devenv\ii\trunk\tools\flex\flex4.1-adobe\bin\compc -compiler.locale=en_US -load-config=C:\devenv\ii\trunk\components\FlexUIPlatform\build/resources/flex/gradle-flex-config.xml

Re: Migrating Enterprise Flex Application

com.infogix is my own. -- Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

I used the nightly build and I am not getting the -api-report option error anymore. But I am getting NullPointerException. Please see the below details. Any ideas what is causing this exception? C:\devenv\apache-royale\royale-asjs>mxmlc -api-report=C:/flex/report.txt -load-c

Re: Migrating Enterprise Flex Application

Thank you for the responses from all of you. I feel confident to take this challenge up. My struggle will be to come up a detailed project plan with clear milestones and deliverables to keep the stakeholders convinced and happy. Thank you Sajith -- Sent from:

Re: Migrating Enterprise Flex Application

I have been using the flex config option in my earlier attempts. That did not work. I tried again, same issue. Is there any debug log or something that I can take a look? -- Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

Has anyone ( big scale ) successfully migrated to Apache Royale from Flex? I want to make sure that this migration path is a viable option for me? Please share your thoughts. Thank you Sajith -- Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

Hi Piotr, I followed the instructions and set up the Royale SDK for generating the report. But the -api-report compiler options does not seem to be supported by the mxmlc compiler in RoyaleSDK. Should I do the whole thing again or is there any way to troubleshoot this? Appreciate your help on

Re: Migrating Enterprise Flex Application

Hi Piotr, Changing the ROYALE_COMPILER_HOME did not help. I tried a different route. I used the command line mxmlc instead of my gradle build. Here is the command I tried running. > mxmlc -api-report="C:\devenv\flex\report.txt" >

Re: Migrating Enterprise Flex Application

Hi Piotr, Thank you for your help on this. I was trying to generate the API report but running into some issues. I used ant/InstallAdobeSDKs.xml and installed the royale-asjs. We use gradle scripts ( which in turn uses the ant tasks ) to build the application including the flex portion. I

Migrating Enterprise Flex Application

Hi, I have an Enterprise web application that uses Flex as the UI/front-end with java EJB back end. I have around 180 Flex pages in the application. The application is component based, with each component having its own set of UI pages. The gradle script builds the application. The UI in each