subject:"Migration of Adobe Flex to Apache Royale \- Support needed"

Re: Migration of Adobe Flex to Apache Royale - Support needed

2020-06-11 Thread Liju Thomas (OSV)

Hi Alex,

I have created a issue in Git

https://github.com/apache/royale-asjs/issues/861#issue-637500135
[https://avatars3.githubusercontent.com/u/47359?s=400=4]<https://github.com/apache/royale-asjs/issues/861#issue-637500135>
Migration of Adobe Flex to Apache Royale - Support needed · Issue #861 · 
apache/royale-asjs<https://github.com/apache/royale-asjs/issues/861#issue-637500135>
Hi Team, Im from Development Team for FedEx, we have an application built 
on Adobe Flex, since Flex is not longer supported after Dec 2020, we need to 
migrate the application to Apache Royale ...
github.com

Regards,

Liju


From: Alex Harui 
Sent: Thursday, June 11, 2020 9:37 PM
To: dev@royale.apache.org 
Cc: Arya Sankar (OSV) 
Subject: [EXTERNAL] Re: Migration of Adobe Flex to Apache Royale - Support 
needed

Hil Liju,

I think the mailing list server strips attachments.  You can open a Github 
issue at 
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_royale-2Dasjs_issues_=DwIGaQ=fpIeS8RwmHkY2r_dFRL5tQ=aanc4j4xsg3RIhiBfaN9onX6bLCpzFkPa2kojuuTVUQ=it1qzA8GNovxL5951OX3uuw4HkNF8MOHs3nQdq2eKvE=E8ifmw3JFEeld0y6LkJamVMt-5J2ZY-th-iCaXaxINo=
But be careful about posting your company’s code.  It could be that the Royale 
compiler has a bug about interface verification for write-only properties 
(setter but no getter).  Maybe another volunteer will find time to test that.  
I’ve got a few other things in my queue right now.

-Alex

From: "Liju Thomas (OSV)" 
Reply-To: "dev@royale.apache.org" 
Date: Thursday, June 11, 2020 at 7:09 AM
To: "dev@royale.apache.org" 
Cc: "Arya Sankar (OSV)" 
Subject: Re: Migration of Adobe Flex to Apache Royale - Support needed

Hey Alex,

Please find the mxml file. IFedexManagedComponent is just a interface.

public interface IFedexManagedComponent
{
function set workFlowManager(value:BaseWorkFlowManager):void;  // this takes 
over the Appl Event Broadcaster
function displayErrors(showErrDIColl:ArrayCollection, 
hideErrDIColl:ArrayCollection=null):void;
function handleEvent(evt:FedExEvent,wfmFeedback:IWFMFeedback):void;
function prepared4Event(event:FedExEvent, wfmFeedback:IWFMFeedback):Boolean;
}

Regards,

Liju

From: Alex Harui 
Sent: Thursday, June 11, 2020 1:41 PM
To: dev@royale.apache.org 
Cc: Arya Sankar (OSV) 
Subject: [EXTERNAL] Re: Migration of Adobe Flex to Apache Royale - Support 
needed

Hi Liju

Please post the relevant code (don't need the code in the function) and the 
actual error.

Your application should look something like:
https://nam03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009data=02%7C01%7Cliju.thomas.osv%40fedex.com%7C63e25d872cd44f2c5e5b08d80e21abe1%7Cb945c813dce641f884575a12c2fe15bf%7C1%7C0%7C637274885075556634sdata=2Hdksvo2bl7J8t0mvIhK3Dsra2tDIIjq4eK74YlHpps%3Dreserved=0<https://urldefense.proofpoint.com/v2/url?u=https-3A__nam04.safelinks.protection.outlook.com_-3Furl-3Dhttp-253A-252F-252Fns.adobe.com-252Fmxml-252F2009-26data-3D02-257C01-257Caharui-2540adobe.com-257C6e3c5245048c429daaed08d80e111e09-257Cfa7b1b5a7b34438794aed2c178decee1-257C0-257C1-257C637274813981660609-26sdata-3DOKtEEa8Sum-252FM8astUBQgQazc6SxO1b1rqYhLlPcDFHs-253D-26reserved-3D0=DwIGaQ=fpIeS8RwmHkY2r_dFRL5tQ=aanc4j4xsg3RIhiBfaN9onX6bLCpzFkPa2kojuuTVUQ=it1qzA8GNovxL5951OX3uuw4HkNF8MOHs3nQdq2eKvE=1QJM429N5sSgpb7XCXkJaJKPPdt2HmDHwfBDBuuutLU=
 >"
  xmlns:mx="library://ns.apache.org/royale/mx"
  implements="IManagedComponent">





Also post the part of IManagedComponent that specifies the workFlowManager API.

I have to stop work for today, but Yishay and others can help.

-Alex

On 6/11/20, 12:51 AM, "Liju Thomas (OSV)"  
wrote:

HI Yishay,

Error still same after making the change.

Regards,

Liju


From: Yishay Weiss 
Sent: Thursday, June 11, 2020 12:26 PM
    To: dev@royale.apache.org 
    Cc: Arya Sankar (OSV) 
Subject: [EXTERNAL] RE: Migration of Adobe Flex to Apache Royale - Support 
needed


Try fx:Script instead of mx:Script



From: Liju Thomas (OSV)<mailto:liju.thomas@fedex.com.INVALID>
Sent: Thursday, June 11, 2020 9:52 AM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
    Cc: Arya Sankar (OSV)<mailto:arya.sankar@fedex.com>
Subject: Re: Migration of Adobe Flex to Apache Royale - Support needed



Hi Alex,



workFlowManager method is there in the MXML file inside 



public function set workFlowManager(wfm:BaseWorkFlowManager):void {

trace("received event: ");

}



I understand it is blank method, with only a trace. Same goes for 
DisplayError. Attaching the complete log.



Regards,



Liju



From: Alex Harui 
Sent: Thursday, June 11, 2020 12:06 PM
    To: dev@

Re: Migration of Adobe Flex to Apache Royale - Support needed

2020-06-11 Thread Alex Harui

Hil Liju,

I think the mailing list server strips attachments.  You can open a Github 
issue at https://github.com/apache/royale-asjs/issues/
But be careful about posting your company’s code.  It could be that the Royale 
compiler has a bug about interface verification for write-only properties 
(setter but no getter).  Maybe another volunteer will find time to test that.  
I’ve got a few other things in my queue right now.

-Alex

From: "Liju Thomas (OSV)" 
Reply-To: "dev@royale.apache.org" 
Date: Thursday, June 11, 2020 at 7:09 AM
To: "dev@royale.apache.org" 
Cc: "Arya Sankar (OSV)" 
Subject: Re: Migration of Adobe Flex to Apache Royale - Support needed

Hey Alex,

Please find the mxml file. IFedexManagedComponent is just a interface.

public interface IFedexManagedComponent
{
function set workFlowManager(value:BaseWorkFlowManager):void;  // this takes 
over the Appl Event Broadcaster
function displayErrors(showErrDIColl:ArrayCollection, 
hideErrDIColl:ArrayCollection=null):void;
function handleEvent(evt:FedExEvent,wfmFeedback:IWFMFeedback):void;
function prepared4Event(event:FedExEvent, wfmFeedback:IWFMFeedback):Boolean;
}

Regards,

Liju

From: Alex Harui 
Sent: Thursday, June 11, 2020 1:41 PM
To: dev@royale.apache.org 
Cc: Arya Sankar (OSV) 
Subject: [EXTERNAL] Re: Migration of Adobe Flex to Apache Royale - Support 
needed

Hi Liju

Please post the relevant code (don't need the code in the function) and the 
actual error.

Your application should look something like:
https://nam03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009data=02%7C01%7Cliju.thomas.osv%40fedex.com%7C063a96d3b32b4186900808d80ddf12d2%7Cb945c813dce641f884575a12c2fe15bf%7C1%7C0%7C637274599038160268sdata=PDFkUDIfhK98A3nE5i666II7PeQ%2BMHO%2Bed89PtgBjVI%3Dreserved=0<https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009=02%7C01%7Caharui%40adobe.com%7C6e3c5245048c429daaed08d80e111e09%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637274813981660609=OKtEEa8Sum%2FM8astUBQgQazc6SxO1b1rqYhLlPcDFHs%3D=0>"
  xmlns:mx="library://ns.apache.org/royale/mx"
  implements="IManagedComponent">





Also post the part of IManagedComponent that specifies the workFlowManager API.

I have to stop work for today, but Yishay and others can help.

-Alex

On 6/11/20, 12:51 AM, "Liju Thomas (OSV)"  
wrote:

HI Yishay,

Error still same after making the change.

Regards,

Liju


From: Yishay Weiss 
Sent: Thursday, June 11, 2020 12:26 PM
    To: dev@royale.apache.org 
Cc: Arya Sankar (OSV) 
    Subject: [EXTERNAL] RE: Migration of Adobe Flex to Apache Royale - Support 
needed


Try fx:Script instead of mx:Script



From: Liju Thomas (OSV)<mailto:liju.thomas@fedex.com.INVALID>
Sent: Thursday, June 11, 2020 9:52 AM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Cc: Arya Sankar (OSV)<mailto:arya.sankar@fedex.com>
Subject: Re: Migration of Adobe Flex to Apache Royale - Support needed



Hi Alex,



workFlowManager method is there in the MXML file inside 



public function set workFlowManager(wfm:BaseWorkFlowManager):void {

trace("received event: ");

}



I understand it is blank method, with only a trace. Same goes for 
DisplayError. Attaching the complete log.



Regards,



Liju



From: Alex Harui 
Sent: Thursday, June 11, 2020 12:06 PM
    To: dev@royale.apache.org 
    Cc: Arya Sankar (OSV) 
Subject: [EXTERNAL] Re: Migration of Adobe Flex to Apache Royale - Support 
needed



Hi Liju,

I no longer see the error " FLEX.mxml(2): col: 1 Error: This tag could not 
be resolved to an ActionScript class. It will be ignored." In your output.  
Instead I am seeing different errors.

The error: " interface method workFlowManager in interface 
IManagedComponent not implemented by class FLEX" indicates that a method called 
"workFlowManager" is missing in your application.  What is the package for 
IManagedComponent?  Is it from your code or some other SWC/library?  Did your 
Flex 3 version have a workFlowManager method?

Thanks,
-Alex

On 6/10/20, 11:27 PM, "Liju Thomas (OSV)" 
 wrote:

Hi Alex,

I have corrected it. Errors are still same.

createsrcswf:
 [echo] *** create D:\\FLEX/../FLEX/Integration.swf ***
[mxmlc] MXMLJSC
[mxmlc] -compiler.keep-generated-actionscript=false
[mxmlc] -compiler.debug=false
[mxmlc] 
+royalelib=C:/Users//AppData/Roaming/npm/node_modules/@apache-royale/royale-js/royale-asjs/frameworks/
[mxmlc] -compiler.actionscript-file-encoding=UTF-8
[mxmlc] -compiler.locale=

Re: Migration of Adobe Flex to Apache Royale - Support needed

2020-06-11 Thread Liju Thomas (OSV)

Hey Alex,

Please find the mxml file. IFedexManagedComponent is just a interface.

public interface IFedexManagedComponent
{
function set workFlowManager(value:BaseWorkFlowManager):void;  // this takes 
over the Appl Event Broadcaster
function displayErrors(showErrDIColl:ArrayCollection, 
hideErrDIColl:ArrayCollection=null):void;
function handleEvent(evt:FedExEvent,wfmFeedback:IWFMFeedback):void;
function prepared4Event(event:FedExEvent, wfmFeedback:IWFMFeedback):Boolean;
}

Regards,

Liju

From: Alex Harui 
Sent: Thursday, June 11, 2020 1:41 PM
To: dev@royale.apache.org 
Cc: Arya Sankar (OSV) 
Subject: [EXTERNAL] Re: Migration of Adobe Flex to Apache Royale - Support 
needed

Hi Liju

Please post the relevant code (don't need the code in the function) and the 
actual error.

Your application should look something like:
https://nam03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009data=02%7C01%7Cliju.thomas.osv%40fedex.com%7C063a96d3b32b4186900808d80ddf12d2%7Cb945c813dce641f884575a12c2fe15bf%7C1%7C0%7C637274599038160268sdata=PDFkUDIfhK98A3nE5i666II7PeQ%2BMHO%2Bed89PtgBjVI%3Dreserved=0;
  xmlns:mx="library://ns.apache.org/royale/mx"
  implements="IManagedComponent">





Also post the part of IManagedComponent that specifies the workFlowManager API.

I have to stop work for today, but Yishay and others can help.

-Alex

On 6/11/20, 12:51 AM, "Liju Thomas (OSV)"  
wrote:

HI Yishay,

Error still same after making the change.

Regards,

Liju


From: Yishay Weiss 
Sent: Thursday, June 11, 2020 12:26 PM
To: dev@royale.apache.org 
Cc: Arya Sankar (OSV) 
Subject: [EXTERNAL] RE: Migration of Adobe Flex to Apache Royale - Support 
needed


Try fx:Script instead of mx:Script



From: Liju Thomas (OSV)<mailto:liju.thomas@fedex.com.INVALID>
Sent: Thursday, June 11, 2020 9:52 AM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Cc: Arya Sankar (OSV)<mailto:arya.sankar....@fedex.com>
Subject: Re: Migration of Adobe Flex to Apache Royale - Support needed



Hi Alex,



workFlowManager method is there in the MXML file inside 



public function set workFlowManager(wfm:BaseWorkFlowManager):void {

trace("received event: ");

}



I understand it is blank method, with only a trace. Same goes for 
DisplayError. Attaching the complete log.



Regards,



Liju



From: Alex Harui 
Sent: Thursday, June 11, 2020 12:06 PM
To: dev@royale.apache.org 
    Cc: Arya Sankar (OSV) 
    Subject: [EXTERNAL] Re: Migration of Adobe Flex to Apache Royale - Support 
needed



Hi Liju,

I no longer see the error " FLEX.mxml(2): col: 1 Error: This tag could not 
be resolved to an ActionScript class. It will be ignored." In your output.  
Instead I am seeing different errors.

The error: " interface method workFlowManager in interface 
IManagedComponent not implemented by class FLEX" indicates that a method called 
"workFlowManager" is missing in your application.  What is the package for 
IManagedComponent?  Is it from your code or some other SWC/library?  Did your 
Flex 3 version have a workFlowManager method?

Thanks,
-Alex

On 6/10/20, 11:27 PM, "Liju Thomas (OSV)" 
 wrote:

Hi Alex,

I have corrected it. Errors are still same.

createsrcswf:
 [echo] *** create D:\\FLEX/../FLEX/Integration.swf ***
[mxmlc] MXMLJSC
[mxmlc] -compiler.keep-generated-actionscript=false
[mxmlc] -compiler.debug=false
[mxmlc] 
+royalelib=C:/Users//AppData/Roaming/npm/node_modules/@apache-royale/royale-js/royale-asjs/frameworks/
[mxmlc] -compiler.actionscript-file-encoding=UTF-8
[mxmlc] -compiler.locale=
[mxmlc] -link-report=D:\/FLEX/../FLEX/externs.txt
[mxmlc] +configname=flex
[mxmlc] -default-size
[mxmlc] 800
[mxmlc] 1000
[mxmlc] 
-load-config=C:/Users//AppData/Roaming/npm/node_modules/@apache-royale/royale-js/royale-asjs/frameworks/flex-config.xml
[mxmlc] -output=D:\FLEX\Integration.swf
[mxmlc] --
[mxmlc] D:\/src/FLEX.mxml
[mxmlc] D:\FLEX.mxml Error: interface method 
workFlowManager in interface IManagedComponent not implemented by class FLEX
[mxmlc]
[mxmlc]
[mxmlc] D:\FLEX.mxml Error: interface method 
displayErrors in interface IManagedComponent not implemented by class FLEX

Regards,

Liju

From: Alex Harui 
Sent: Thursday, June 11, 2020 11:26 AM
    To: dev@royale.apache.org 
    Cc: Arya Sankar (OSV) 
Subject: [EXTERNAL] Re: M

Re: Migration of Adobe Flex to Apache Royale - Support needed

2020-06-11 Thread Alex Harui

Hi Liju

Please post the relevant code (don't need the code in the function) and the 
actual error.

Your application should look something like:
http://ns.adobe.com/mxml/2009;
  xmlns:mx="library://ns.apache.org/royale/mx"
  implements="IManagedComponent">





Also post the part of IManagedComponent that specifies the workFlowManager API.

I have to stop work for today, but Yishay and others can help.

-Alex

On 6/11/20, 12:51 AM, "Liju Thomas (OSV)"  
wrote:

HI Yishay,

Error still same after making the change.

Regards,

Liju


From: Yishay Weiss 
Sent: Thursday, June 11, 2020 12:26 PM
To: dev@royale.apache.org 
Cc: Arya Sankar (OSV) 
Subject: [EXTERNAL] RE: Migration of Adobe Flex to Apache Royale - Support 
needed


Try fx:Script instead of mx:Script



From: Liju Thomas (OSV)<mailto:liju.thomas@fedex.com.INVALID>
Sent: Thursday, June 11, 2020 9:52 AM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Cc: Arya Sankar (OSV)<mailto:arya.sankar....@fedex.com>
Subject: Re: Migration of Adobe Flex to Apache Royale - Support needed



Hi Alex,



workFlowManager method is there in the MXML file inside 



public function set workFlowManager(wfm:BaseWorkFlowManager):void {

trace("received event: ");

}



I understand it is blank method, with only a trace. Same goes for 
DisplayError. Attaching the complete log.



Regards,



Liju



From: Alex Harui 
Sent: Thursday, June 11, 2020 12:06 PM
To: dev@royale.apache.org 
    Cc: Arya Sankar (OSV) 
    Subject: [EXTERNAL] Re: Migration of Adobe Flex to Apache Royale - Support 
needed



Hi Liju,

I no longer see the error " FLEX.mxml(2): col: 1 Error: This tag could not 
be resolved to an ActionScript class. It will be ignored." In your output.  
Instead I am seeing different errors.

The error: " interface method workFlowManager in interface 
IManagedComponent not implemented by class FLEX" indicates that a method called 
"workFlowManager" is missing in your application.  What is the package for 
IManagedComponent?  Is it from your code or some other SWC/library?  Did your 
Flex 3 version have a workFlowManager method?

Thanks,
-Alex

On 6/10/20, 11:27 PM, "Liju Thomas (OSV)" 
 wrote:

Hi Alex,

I have corrected it. Errors are still same.

createsrcswf:
 [echo] *** create D:\\FLEX/../FLEX/Integration.swf ***
[mxmlc] MXMLJSC
[mxmlc] -compiler.keep-generated-actionscript=false
[mxmlc] -compiler.debug=false
[mxmlc] 
+royalelib=C:/Users//AppData/Roaming/npm/node_modules/@apache-royale/royale-js/royale-asjs/frameworks/
[mxmlc] -compiler.actionscript-file-encoding=UTF-8
[mxmlc] -compiler.locale=
[mxmlc] -link-report=D:\/FLEX/../FLEX/externs.txt
[mxmlc] +configname=flex
[mxmlc] -default-size
[mxmlc] 800
[mxmlc] 1000
[mxmlc] 
-load-config=C:/Users//AppData/Roaming/npm/node_modules/@apache-royale/royale-js/royale-asjs/frameworks/flex-config.xml
[mxmlc] -output=D:\FLEX\Integration.swf
[mxmlc] --
[mxmlc] D:\/src/FLEX.mxml
[mxmlc] D:\FLEX.mxml Error: interface method 
workFlowManager in interface IManagedComponent not implemented by class FLEX
[mxmlc]
[mxmlc]
[mxmlc] D:\FLEX.mxml Error: interface method 
displayErrors in interface IManagedComponent not implemented by class FLEX

Regards,

Liju

From: Alex Harui 
Sent: Thursday, June 11, 2020 11:26 AM
    To: dev@royale.apache.org 
    Cc: Arya Sankar (OSV) 
Subject: [EXTERNAL] Re: Migration of Adobe Flex to Apache Royale - 
Support needed

Hi Liju,

The option -load-config=C:/.../royale-config.xml should not 
be there.  Are you specifying that or is that in some default launcher we have? 
 You'll know you have it right when it loads flex-config.xml (because of 
+configname=flex) instead of royale-config.xml

HTH,
-Alex

On 6/10/20, 10:52 PM, "Liju Thomas (OSV)" 
 wrote:

Hey Alex,

Yes it is FLEX 3, I updated as per your comment, following error is 
coming. You may check the configuration:

 [echo] *** create 
D:\Work\Clients\FedEx\Apps\WGRT\VCWorkspace\SVN\WGRTFLEX/../WGRTFLEX/WGRTFreightIntegration.swf
 ***
[mxmlc] MXMLJSC
[mxmlc] -

RE: Migration of Adobe Flex to Apache Royale - Support needed

2020-06-11 Thread Yishay Weiss

Hi Liju,

If you post some code I can run locally I can try to help.

Thanks,
Yishay

From: Liju Thomas (OSV)<mailto:liju.thomas@fedex.com.INVALID>
Sent: Thursday, June 11, 2020 10:51 AM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Cc: Arya Sankar (OSV)<mailto:arya.sankar@fedex.com>
Subject: Re: Migration of Adobe Flex to Apache Royale - Support needed

HI Yishay,

Error still same after making the change.

Regards,

Liju


From: Yishay Weiss 
Sent: Thursday, June 11, 2020 12:26 PM
To: dev@royale.apache.org 
Cc: Arya Sankar (OSV) 
Subject: [EXTERNAL] RE: Migration of Adobe Flex to Apache Royale - Support 
needed


Try fx:Script instead of mx:Script



From: Liju Thomas (OSV)<mailto:liju.thomas@fedex.com.INVALID>
Sent: Thursday, June 11, 2020 9:52 AM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Cc: Arya Sankar (OSV)<mailto:arya.sankar@fedex.com>
Subject: Re: Migration of Adobe Flex to Apache Royale - Support needed



Hi Alex,



workFlowManager method is there in the MXML file inside 



public function set workFlowManager(wfm:BaseWorkFlowManager):void {

trace("received event: ");

}



I understand it is blank method, with only a trace. Same goes for DisplayError. 
Attaching the complete log.



Regards,



Liju



From: Alex Harui 
Sent: Thursday, June 11, 2020 12:06 PM
To: dev@royale.apache.org 
Cc: Arya Sankar (OSV) 
Subject: [EXTERNAL] Re: Migration of Adobe Flex to Apache Royale - Support 
needed



Hi Liju,

I no longer see the error " FLEX.mxml(2): col: 1 Error: This tag could not be 
resolved to an ActionScript class. It will be ignored." In your output.  
Instead I am seeing different errors.

The error: " interface method workFlowManager in interface IManagedComponent 
not implemented by class FLEX" indicates that a method called "workFlowManager" 
is missing in your application.  What is the package for IManagedComponent?  Is 
it from your code or some other SWC/library?  Did your Flex 3 version have a 
workFlowManager method?

Thanks,
-Alex

On 6/10/20, 11:27 PM, "Liju Thomas (OSV)"  
wrote:

Hi Alex,

I have corrected it. Errors are still same.

createsrcswf:
 [echo] *** create D:\\FLEX/../FLEX/Integration.swf ***
[mxmlc] MXMLJSC
[mxmlc] -compiler.keep-generated-actionscript=false
[mxmlc] -compiler.debug=false
[mxmlc] 
+royalelib=C:/Users//AppData/Roaming/npm/node_modules/@apache-royale/royale-js/royale-asjs/frameworks/
[mxmlc] -compiler.actionscript-file-encoding=UTF-8
[mxmlc] -compiler.locale=
[mxmlc] -link-report=D:\/FLEX/../FLEX/externs.txt
[mxmlc] +configname=flex
[mxmlc] -default-size
[mxmlc] 800
[mxmlc] 1000
[mxmlc] 
-load-config=C:/Users//AppData/Roaming/npm/node_modules/@apache-royale/royale-js/royale-asjs/frameworks/flex-config.xml
[mxmlc] -output=D:\FLEX\Integration.swf
[mxmlc] --
[mxmlc] D:\/src/FLEX.mxml
[mxmlc] D:\FLEX.mxml Error: interface method workFlowManager 
in interface IManagedComponent not implemented by class FLEX
[mxmlc]
[mxmlc]
[mxmlc] D:\FLEX.mxml Error: interface method displayErrors in 
interface IManagedComponent not implemented by class FLEX

Regards,

Liju

From: Alex Harui 
Sent: Thursday, June 11, 2020 11:26 AM
To: dev@royale.apache.org 
    Cc: Arya Sankar (OSV) 
Subject: [EXTERNAL] Re: Migration of Adobe Flex to Apache Royale - Support 
needed

Hi Liju,

The option -load-config=C:/.../royale-config.xml should not be 
there.  Are you specifying that or is that in some default launcher we have?  
You'll know you have it right when it loads flex-config.xml (because of 
+configname=flex) instead of royale-config.xml

HTH,
-Alex

On 6/10/20, 10:52 PM, "Liju Thomas (OSV)" 
 wrote:

Hey Alex,

Yes it is FLEX 3, I updated as per your comment, following error is 
coming. You may check the configuration:

 [echo] *** create 
D:\Work\Clients\FedEx\Apps\WGRT\VCWorkspace\SVN\WGRTFLEX/../WGRTFLEX/WGRTFreightIntegration.swf
 ***
[mxmlc] MXMLJSC
[mxmlc] -compiler.keep-generated-actionscript=false
[mxmlc] -compiler.debug=false
[mxmlc] 
+royalelib=C:/AppData/Roaming/npm/node_modules/@apache-royale/royale-js/frameworks/
[mxmlc] -compiler.actionscript-file-encoding=UTF-8
[mxmlc] -compiler.locale=
[mxmlc] -link-report=D:\/FLEX/../WGRTFLEX/externs.txt
[mxmlc] +configname=flex
[mxmlc] -default-size
[mxmlc] 800
[mxmlc] 1000
[mxmlc] 
-load-config=C:/AppData/Roaming/npm/node_modules/@apache-royale/royale-js/royale-asjs/frameworks/royale-config.xml
[mxmlc] -output=D:FLEX\WGRTFreight

Re: Migration of Adobe Flex to Apache Royale - Support needed

2020-06-11 Thread Liju Thomas (OSV)

HI Yishay,

Error still same after making the change.

Regards,

Liju


From: Yishay Weiss 
Sent: Thursday, June 11, 2020 12:26 PM
To: dev@royale.apache.org 
Cc: Arya Sankar (OSV) 
Subject: [EXTERNAL] RE: Migration of Adobe Flex to Apache Royale - Support 
needed


Try fx:Script instead of mx:Script



From: Liju Thomas (OSV)<mailto:liju.thomas@fedex.com.INVALID>
Sent: Thursday, June 11, 2020 9:52 AM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Cc: Arya Sankar (OSV)<mailto:arya.sankar@fedex.com>
Subject: Re: Migration of Adobe Flex to Apache Royale - Support needed



Hi Alex,



workFlowManager method is there in the MXML file inside 



public function set workFlowManager(wfm:BaseWorkFlowManager):void {

trace("received event: ");

}



I understand it is blank method, with only a trace. Same goes for DisplayError. 
Attaching the complete log.



Regards,



Liju



From: Alex Harui 
Sent: Thursday, June 11, 2020 12:06 PM
To: dev@royale.apache.org 
Cc: Arya Sankar (OSV) 
Subject: [EXTERNAL] Re: Migration of Adobe Flex to Apache Royale - Support 
needed



Hi Liju,

I no longer see the error " FLEX.mxml(2): col: 1 Error: This tag could not be 
resolved to an ActionScript class. It will be ignored." In your output.  
Instead I am seeing different errors.

The error: " interface method workFlowManager in interface IManagedComponent 
not implemented by class FLEX" indicates that a method called "workFlowManager" 
is missing in your application.  What is the package for IManagedComponent?  Is 
it from your code or some other SWC/library?  Did your Flex 3 version have a 
workFlowManager method?

Thanks,
-Alex

On 6/10/20, 11:27 PM, "Liju Thomas (OSV)"  
wrote:

Hi Alex,

I have corrected it. Errors are still same.

createsrcswf:
 [echo] *** create D:\\FLEX/../FLEX/Integration.swf ***
[mxmlc] MXMLJSC
[mxmlc] -compiler.keep-generated-actionscript=false
[mxmlc] -compiler.debug=false
[mxmlc] 
+royalelib=C:/Users//AppData/Roaming/npm/node_modules/@apache-royale/royale-js/royale-asjs/frameworks/
[mxmlc] -compiler.actionscript-file-encoding=UTF-8
[mxmlc] -compiler.locale=
[mxmlc] -link-report=D:\/FLEX/../FLEX/externs.txt
[mxmlc] +configname=flex
[mxmlc] -default-size
[mxmlc] 800
[mxmlc] 1000
[mxmlc] 
-load-config=C:/Users//AppData/Roaming/npm/node_modules/@apache-royale/royale-js/royale-asjs/frameworks/flex-config.xml
[mxmlc] -output=D:\FLEX\Integration.swf
[mxmlc] --
[mxmlc] D:\/src/FLEX.mxml
[mxmlc] D:\FLEX.mxml Error: interface method workFlowManager 
in interface IManagedComponent not implemented by class FLEX
[mxmlc]
[mxmlc]
[mxmlc] D:\FLEX.mxml Error: interface method displayErrors in 
interface IManagedComponent not implemented by class FLEX

Regards,

Liju

From: Alex Harui 
Sent: Thursday, June 11, 2020 11:26 AM
To: dev@royale.apache.org 
Cc: Arya Sankar (OSV) 
    Subject: [EXTERNAL] Re: Migration of Adobe Flex to Apache Royale - Support 
needed

Hi Liju,

The option -load-config=C:/.../royale-config.xml should not be 
there.  Are you specifying that or is that in some default launcher we have?  
You'll know you have it right when it loads flex-config.xml (because of 
+configname=flex) instead of royale-config.xml

HTH,
-Alex

On 6/10/20, 10:52 PM, "Liju Thomas (OSV)" 
 wrote:

Hey Alex,

Yes it is FLEX 3, I updated as per your comment, following error is 
coming. You may check the configuration:

 [echo] *** create 
D:\Work\Clients\FedEx\Apps\WGRT\VCWorkspace\SVN\WGRTFLEX/../WGRTFLEX/WGRTFreightIntegration.swf
 ***
[mxmlc] MXMLJSC
[mxmlc] -compiler.keep-generated-actionscript=false
[mxmlc] -compiler.debug=false
[mxmlc] 
+royalelib=C:/AppData/Roaming/npm/node_modules/@apache-royale/royale-js/frameworks/
[mxmlc] -compiler.actionscript-file-encoding=UTF-8
[mxmlc] -compiler.locale=
[mxmlc] -link-report=D:\/FLEX/../WGRTFLEX/externs.txt
[mxmlc] +configname=flex
[mxmlc] -default-size
[mxmlc] 800
[mxmlc] 1000
[mxmlc] 
-load-config=C:/AppData/Roaming/npm/node_modules/@apache-royale/royale-js/royale-asjs/frameworks/royale-config.xml
[mxmlc] -output=D:FLEX\WGRTFreightIntegration.swf
[mxmlc] --
[mxmlc] D:\FLEX/../WGRTFLEX/src/WGRTFLEX.mxml
[mxmlc] 6.7364493 seconds
[mxmlc] D:\WGRTFLEX\src\WGRTFLEX.mxml(2): col: 1 Error: 
This tag could not be resolved to an ActionScript class. It will be ignored.
[mxmlc]
[mxmlc] https://nam03.safelinks.protection.outlook.com/?url=htt

RE: Migration of Adobe Flex to Apache Royale - Support needed

2020-06-11 Thread Yishay Weiss

Try fx:Script instead of mx:Script

From: Liju Thomas (OSV)<mailto:liju.thomas@fedex.com.INVALID>
Sent: Thursday, June 11, 2020 9:52 AM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Cc: Arya Sankar (OSV)<mailto:arya.sankar@fedex.com>
Subject: Re: Migration of Adobe Flex to Apache Royale - Support needed

Hi Alex,

workFlowManager method is there in the MXML file inside 

public function set workFlowManager(wfm:BaseWorkFlowManager):void {
trace("received event: ");
}

I understand it is blank method, with only a trace. Same goes for DisplayError. 
Attaching the complete log.

Regards,

Liju

From: Alex Harui 
Sent: Thursday, June 11, 2020 12:06 PM
To: dev@royale.apache.org 
Cc: Arya Sankar (OSV) 
Subject: [EXTERNAL] Re: Migration of Adobe Flex to Apache Royale - Support 
needed

Hi Liju,

I no longer see the error " FLEX.mxml(2): col: 1 Error: This tag could not be 
resolved to an ActionScript class. It will be ignored." In your output.  
Instead I am seeing different errors.

The error: " interface method workFlowManager in interface IManagedComponent 
not implemented by class FLEX" indicates that a method called "workFlowManager" 
is missing in your application.  What is the package for IManagedComponent?  Is 
it from your code or some other SWC/library?  Did your Flex 3 version have a 
workFlowManager method?

Thanks,
-Alex

On 6/10/20, 11:27 PM, "Liju Thomas (OSV)"  
wrote:

Hi Alex,

I have corrected it. Errors are still same.

createsrcswf:
 [echo] *** create D:\\FLEX/../FLEX/Integration.swf ***
[mxmlc] MXMLJSC
[mxmlc] -compiler.keep-generated-actionscript=false
[mxmlc] -compiler.debug=false
[mxmlc] 
+royalelib=C:/Users//AppData/Roaming/npm/node_modules/@apache-royale/royale-js/royale-asjs/frameworks/
[mxmlc] -compiler.actionscript-file-encoding=UTF-8
[mxmlc] -compiler.locale=
[mxmlc] -link-report=D:\/FLEX/../FLEX/externs.txt
[mxmlc] +configname=flex
[mxmlc] -default-size
[mxmlc] 800
[mxmlc] 1000
[mxmlc] 
-load-config=C:/Users//AppData/Roaming/npm/node_modules/@apache-royale/royale-js/royale-asjs/frameworks/flex-config.xml
[mxmlc] -output=D:\FLEX\Integration.swf
[mxmlc] --
[mxmlc] D:\/src/FLEX.mxml
[mxmlc] D:\FLEX.mxml Error: interface method workFlowManager 
in interface IManagedComponent not implemented by class FLEX
[mxmlc]
[mxmlc]
[mxmlc] D:\FLEX.mxml Error: interface method displayErrors in 
interface IManagedComponent not implemented by class FLEX

Regards,

Liju

From: Alex Harui 
Sent: Thursday, June 11, 2020 11:26 AM
To: dev@royale.apache.org 
Cc: Arya Sankar (OSV) 
    Subject: [EXTERNAL] Re: Migration of Adobe Flex to Apache Royale - Support 
needed

Hi Liju,

The option -load-config=C:/.../royale-config.xml should not be 
there.  Are you specifying that or is that in some default launcher we have?  
You'll know you have it right when it loads flex-config.xml (because of 
+configname=flex) instead of royale-config.xml

HTH,
-Alex

On 6/10/20, 10:52 PM, "Liju Thomas (OSV)" 
 wrote:

Hey Alex,

Yes it is FLEX 3, I updated as per your comment, following error is 
coming. You may check the configuration:

 [echo] *** create 
D:\Work\Clients\FedEx\Apps\WGRT\VCWorkspace\SVN\WGRTFLEX/../WGRTFLEX/WGRTFreightIntegration.swf
 ***
[mxmlc] MXMLJSC
[mxmlc] -compiler.keep-generated-actionscript=false
[mxmlc] -compiler.debug=false
[mxmlc] 
+royalelib=C:/AppData/Roaming/npm/node_modules/@apache-royale/royale-js/frameworks/
[mxmlc] -compiler.actionscript-file-encoding=UTF-8
[mxmlc] -compiler.locale=
[mxmlc] -link-report=D:\/FLEX/../WGRTFLEX/externs.txt
[mxmlc] +configname=flex
[mxmlc] -default-size
[mxmlc] 800
[mxmlc] 1000
[mxmlc] 
-load-config=C:/AppData/Roaming/npm/node_modules/@apache-royale/royale-js/royale-asjs/frameworks/royale-config.xml
[mxmlc] -output=D:FLEX\WGRTFreightIntegration.swf
[mxmlc] --
[mxmlc] D:\FLEX/../WGRTFLEX/src/WGRTFLEX.mxml
[mxmlc] 6.7364493 seconds
[mxmlc] D:\WGRTFLEX\src\WGRTFLEX.mxml(2): col: 1 Error: 
This tag could not be resolved to an ActionScript class. It will be ignored.
[mxmlc]
[mxmlc] https://nam03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009data=02%7C01%7Cliju.thomas.osv%40fedex.com%7C1b59ffa3c1de410237a308d80dd1ea58%7Cb945c813dce641f884575a12c2fe15bf%7C1%7C0%7C637274542519901597sdata=gt%2BkQJTW9cLZ4AeHYnVUW9OEYCC34a3aIoe0WbXYRhs%3Dreserved=0;
 xmlns:mx="library://ns.apache.org/royale/mx"
[mxmlc] ^
[mxmlc]

Re: Migration of Adobe Flex to Apache Royale - Support needed

2020-06-11 Thread Liju Thomas (OSV)

Hi Alex,

workFlowManager method is there in the MXML file inside 

public function set workFlowManager(wfm:BaseWorkFlowManager):void {
trace("received event: ");
}

I understand it is blank method, with only a trace. Same goes for DisplayError. 
Attaching the complete log.

Regards,

Liju

From: Alex Harui 
Sent: Thursday, June 11, 2020 12:06 PM
To: dev@royale.apache.org 
Cc: Arya Sankar (OSV) 
Subject: [EXTERNAL] Re: Migration of Adobe Flex to Apache Royale - Support 
needed

Hi Liju,

I no longer see the error " FLEX.mxml(2): col: 1 Error: This tag could not be 
resolved to an ActionScript class. It will be ignored." In your output.  
Instead I am seeing different errors.

The error: " interface method workFlowManager in interface IManagedComponent 
not implemented by class FLEX" indicates that a method called "workFlowManager" 
is missing in your application.  What is the package for IManagedComponent?  Is 
it from your code or some other SWC/library?  Did your Flex 3 version have a 
workFlowManager method?

Thanks,
-Alex

On 6/10/20, 11:27 PM, "Liju Thomas (OSV)"  
wrote:

Hi Alex,

I have corrected it. Errors are still same.

createsrcswf:
 [echo] *** create D:\\FLEX/../FLEX/Integration.swf ***
[mxmlc] MXMLJSC
[mxmlc] -compiler.keep-generated-actionscript=false
[mxmlc] -compiler.debug=false
[mxmlc] 
+royalelib=C:/Users//AppData/Roaming/npm/node_modules/@apache-royale/royale-js/royale-asjs/frameworks/
[mxmlc] -compiler.actionscript-file-encoding=UTF-8
[mxmlc] -compiler.locale=
[mxmlc] -link-report=D:\/FLEX/../FLEX/externs.txt
[mxmlc] +configname=flex
[mxmlc] -default-size
[mxmlc] 800
[mxmlc] 1000
[mxmlc] 
-load-config=C:/Users//AppData/Roaming/npm/node_modules/@apache-royale/royale-js/royale-asjs/frameworks/flex-config.xml
[mxmlc] -output=D:\FLEX\Integration.swf
[mxmlc] --
[mxmlc] D:\/src/FLEX.mxml
[mxmlc] D:\FLEX.mxml Error: interface method workFlowManager 
in interface IManagedComponent not implemented by class FLEX
[mxmlc]
[mxmlc]
[mxmlc] D:\FLEX.mxml Error: interface method displayErrors in 
interface IManagedComponent not implemented by class FLEX

Regards,

Liju

From: Alex Harui 
Sent: Thursday, June 11, 2020 11:26 AM
To: dev@royale.apache.org 
Cc: Arya Sankar (OSV) 
    Subject: [EXTERNAL] Re: Migration of Adobe Flex to Apache Royale - Support 
needed

Hi Liju,

The option -load-config=C:/.../royale-config.xml should not be 
there.  Are you specifying that or is that in some default launcher we have?  
You'll know you have it right when it loads flex-config.xml (because of 
+configname=flex) instead of royale-config.xml

HTH,
-Alex

On 6/10/20, 10:52 PM, "Liju Thomas (OSV)" 
 wrote:

Hey Alex,

Yes it is FLEX 3, I updated as per your comment, following error is 
coming. You may check the configuration:

 [echo] *** create 
D:\Work\Clients\FedEx\Apps\WGRT\VCWorkspace\SVN\WGRTFLEX/../WGRTFLEX/WGRTFreightIntegration.swf
 ***
[mxmlc] MXMLJSC
[mxmlc] -compiler.keep-generated-actionscript=false
[mxmlc] -compiler.debug=false
[mxmlc] 
+royalelib=C:/AppData/Roaming/npm/node_modules/@apache-royale/royale-js/frameworks/
[mxmlc] -compiler.actionscript-file-encoding=UTF-8
[mxmlc] -compiler.locale=
[mxmlc] -link-report=D:\/FLEX/../WGRTFLEX/externs.txt
[mxmlc] +configname=flex
[mxmlc] -default-size
[mxmlc] 800
[mxmlc] 1000
[mxmlc] 
-load-config=C:/AppData/Roaming/npm/node_modules/@apache-royale/royale-js/royale-asjs/frameworks/royale-config.xml
[mxmlc] -output=D:FLEX\WGRTFreightIntegration.swf
[mxmlc] --
[mxmlc] D:\FLEX/../WGRTFLEX/src/WGRTFLEX.mxml
[mxmlc] 6.7364493 seconds
[mxmlc] D:\WGRTFLEX\src\WGRTFLEX.mxml(2): col: 1 Error: 
This tag could not be resolved to an ActionScript class. It will be ignored.
[mxmlc]
[mxmlc] https://nam03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009data=02%7C01%7Cliju.thomas.osv%40fedex.com%7C1b59ffa3c1de410237a308d80dd1ea58%7Cb945c813dce641f884575a12c2fe15bf%7C1%7C0%7C637274542519901597sdata=gt%2BkQJTW9cLZ4AeHYnVUW9OEYCC34a3aIoe0WbXYRhs%3Dreserved=0;
 xmlns:mx="library://ns.apache.org/royale/mx"
[mxmlc] ^
[mxmlc]
FLEX.mxml(2): col: 1 Error: This tag could not be resolved to an 
ActionScript class. It will be ignored.
[mxmlc]
[mxmlc] https://nam03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009data=02%7C01%7Cliju.thomas.osv%40fedex.com%7C1b59f

Re: Migration of Adobe Flex to Apache Royale - Support needed

2020-06-11 Thread Alex Harui

Hi Liju,

I no longer see the error " FLEX.mxml(2): col: 1 Error: This tag could not be 
resolved to an ActionScript class. It will be ignored." In your output.  
Instead I am seeing different errors.

The error: " interface method workFlowManager in interface IManagedComponent 
not implemented by class FLEX" indicates that a method called "workFlowManager" 
is missing in your application.  What is the package for IManagedComponent?  Is 
it from your code or some other SWC/library?  Did your Flex 3 version have a 
workFlowManager method?

Thanks,
-Alex

On 6/10/20, 11:27 PM, "Liju Thomas (OSV)"  
wrote:

Hi Alex,

I have corrected it. Errors are still same.

createsrcswf:
 [echo] *** create D:\\FLEX/../FLEX/Integration.swf ***
[mxmlc] MXMLJSC
[mxmlc] -compiler.keep-generated-actionscript=false
[mxmlc] -compiler.debug=false
[mxmlc] 
+royalelib=C:/Users//AppData/Roaming/npm/node_modules/@apache-royale/royale-js/royale-asjs/frameworks/
[mxmlc] -compiler.actionscript-file-encoding=UTF-8
[mxmlc] -compiler.locale=
[mxmlc] -link-report=D:\/FLEX/../FLEX/externs.txt
[mxmlc] +configname=flex
[mxmlc] -default-size
[mxmlc] 800
[mxmlc] 1000
[mxmlc] 
-load-config=C:/Users//AppData/Roaming/npm/node_modules/@apache-royale/royale-js/royale-asjs/frameworks/flex-config.xml
[mxmlc] -output=D:\FLEX\Integration.swf
[mxmlc] --
[mxmlc] D:\/src/FLEX.mxml
[mxmlc] D:\FLEX.mxml Error: interface method workFlowManager 
in interface IManagedComponent not implemented by class FLEX
[mxmlc]
[mxmlc]
[mxmlc] D:\FLEX.mxml Error: interface method displayErrors in 
interface IManagedComponent not implemented by class FLEX

Regards,

Liju

From: Alex Harui 
Sent: Thursday, June 11, 2020 11:26 AM
To: dev@royale.apache.org 
Cc: Arya Sankar (OSV) 
    Subject: [EXTERNAL] Re: Migration of Adobe Flex to Apache Royale - Support 
needed

Hi Liju,

The option -load-config=C:/.../royale-config.xml should not be 
there.  Are you specifying that or is that in some default launcher we have?  
You'll know you have it right when it loads flex-config.xml (because of 
+configname=flex) instead of royale-config.xml

HTH,
-Alex

On 6/10/20, 10:52 PM, "Liju Thomas (OSV)" 
 wrote:

Hey Alex,

Yes it is FLEX 3, I updated as per your comment, following error is 
coming. You may check the configuration:

 [echo] *** create 
D:\Work\Clients\FedEx\Apps\WGRT\VCWorkspace\SVN\WGRTFLEX/../WGRTFLEX/WGRTFreightIntegration.swf
 ***
[mxmlc] MXMLJSC
[mxmlc] -compiler.keep-generated-actionscript=false
[mxmlc] -compiler.debug=false
[mxmlc] 
+royalelib=C:/AppData/Roaming/npm/node_modules/@apache-royale/royale-js/frameworks/
[mxmlc] -compiler.actionscript-file-encoding=UTF-8
[mxmlc] -compiler.locale=
[mxmlc] -link-report=D:\/FLEX/../WGRTFLEX/externs.txt
[mxmlc] +configname=flex
[mxmlc] -default-size
[mxmlc] 800
[mxmlc] 1000
[mxmlc] 
-load-config=C:/AppData/Roaming/npm/node_modules/@apache-royale/royale-js/royale-asjs/frameworks/royale-config.xml
[mxmlc] -output=D:FLEX\WGRTFreightIntegration.swf
[mxmlc] --
[mxmlc] D:\FLEX/../WGRTFLEX/src/WGRTFLEX.mxml
[mxmlc] 6.7364493 seconds
[mxmlc] D:\WGRTFLEX\src\WGRTFLEX.mxml(2): col: 1 Error: 
This tag could not be resolved to an ActionScript class. It will be ignored.
[mxmlc]
[mxmlc] https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009data=02%7C01%7Caharui%40adobe.com%7Cdeef0b9ac87f42d565d408d80dd09289%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637274536752600097sdata=GIXMXIoZxJ2UeL0j9jRLEzFumhGa8mT%2BXt7OpFVE3Hg%3Dreserved=0;
 xmlns:mx="library://ns.apache.org/royale/mx"
[mxmlc] ^
[mxmlc]
FLEX.mxml(2): col: 1 Error: This tag could not be resolved to an 
ActionScript class. It will be ignored.
[mxmlc]
[mxmlc] https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009data=02%7C01%7Caharui%40adobe.com%7Cdeef0b9ac87f42d565d408d80dd09289%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637274536752600097sdata=GIXMXIoZxJ2UeL0j9jRLEzFumhGa8mT%2BXt7OpFVE3Hg%3Dreserved=0;
 xmlns:mx="library://ns.apache.org/royale/mx"
[mxmlc] ^
[mxmlc]

Regards,

Liju


From: Alex Harui 
Sent: Thursday, June 11, 2020 11:06 AM
To: dev@royale.apache.org 
    Cc: Arya Sankar (OSV) 
    Subject: [EXTERNAL] Re: Migr

Re: Migration of Adobe Flex to Apache Royale - Support needed

2020-06-11 Thread Liju Thomas (OSV)

Hi Alex,

I have corrected it. Errors are still same.

createsrcswf:
 [echo] *** create D:\\FLEX/../FLEX/Integration.swf ***
[mxmlc] MXMLJSC
[mxmlc] -compiler.keep-generated-actionscript=false
[mxmlc] -compiler.debug=false
[mxmlc] 
+royalelib=C:/Users//AppData/Roaming/npm/node_modules/@apache-royale/royale-js/royale-asjs/frameworks/
[mxmlc] -compiler.actionscript-file-encoding=UTF-8
[mxmlc] -compiler.locale=
[mxmlc] -link-report=D:\/FLEX/../FLEX/externs.txt
[mxmlc] +configname=flex
[mxmlc] -default-size
[mxmlc] 800
[mxmlc] 1000
[mxmlc] 
-load-config=C:/Users//AppData/Roaming/npm/node_modules/@apache-royale/royale-js/royale-asjs/frameworks/flex-config.xml
[mxmlc] -output=D:\FLEX\Integration.swf
[mxmlc] --
[mxmlc] D:\/src/FLEX.mxml
[mxmlc] D:\FLEX.mxml Error: interface method workFlowManager in 
interface IManagedComponent not implemented by class FLEX
[mxmlc]
[mxmlc]
[mxmlc] D:\FLEX.mxml Error: interface method displayErrors in 
interface IManagedComponent not implemented by class FLEX

Regards,

Liju

From: Alex Harui 
Sent: Thursday, June 11, 2020 11:26 AM
To: dev@royale.apache.org 
Cc: Arya Sankar (OSV) 
Subject: [EXTERNAL] Re: Migration of Adobe Flex to Apache Royale - Support 
needed

Hi Liju,

The option -load-config=C:/.../royale-config.xml should not be there. 
 Are you specifying that or is that in some default launcher we have?  You'll 
know you have it right when it loads flex-config.xml (because of 
+configname=flex) instead of royale-config.xml

HTH,
-Alex

On 6/10/20, 10:52 PM, "Liju Thomas (OSV)"  
wrote:

Hey Alex,

Yes it is FLEX 3, I updated as per your comment, following error is coming. 
You may check the configuration:

 [echo] *** create 
D:\Work\Clients\FedEx\Apps\WGRT\VCWorkspace\SVN\WGRTFLEX/../WGRTFLEX/WGRTFreightIntegration.swf
 ***
[mxmlc] MXMLJSC
[mxmlc] -compiler.keep-generated-actionscript=false
[mxmlc] -compiler.debug=false
[mxmlc] 
+royalelib=C:/AppData/Roaming/npm/node_modules/@apache-royale/royale-js/frameworks/
[mxmlc] -compiler.actionscript-file-encoding=UTF-8
[mxmlc] -compiler.locale=
[mxmlc] -link-report=D:\/FLEX/../WGRTFLEX/externs.txt
[mxmlc] +configname=flex
[mxmlc] -default-size
[mxmlc] 800
[mxmlc] 1000
[mxmlc] 
-load-config=C:/AppData/Roaming/npm/node_modules/@apache-royale/royale-js/royale-asjs/frameworks/royale-config.xml
[mxmlc] -output=D:FLEX\WGRTFreightIntegration.swf
[mxmlc] --
[mxmlc] D:\FLEX/../WGRTFLEX/src/WGRTFLEX.mxml
[mxmlc] 6.7364493 seconds
[mxmlc] D:\WGRTFLEX\src\WGRTFLEX.mxml(2): col: 1 Error: This 
tag could not be resolved to an ActionScript class. It will be ignored.
[mxmlc]
[mxmlc] https://nam03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009data=02%7C01%7Cliju.thomas.osv%40fedex.com%7C30ff97f9ec2649af5a6e08d80dcc566b%7Cb945c813dce641f884575a12c2fe15bf%7C1%7C0%7C637274518579342014sdata=og2SYBpgrbpPj3vbi6ve1YjiqtrSR99HEph47Jf3IM8%3Dreserved=0;
 xmlns:mx="library://ns.apache.org/royale/mx"
[mxmlc] ^
[mxmlc]
FLEX.mxml(2): col: 1 Error: This tag could not be resolved to an 
ActionScript class. It will be ignored.
[mxmlc]
[mxmlc] https://nam03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009data=02%7C01%7Cliju.thomas.osv%40fedex.com%7C30ff97f9ec2649af5a6e08d80dcc566b%7Cb945c813dce641f884575a12c2fe15bf%7C1%7C0%7C637274518579342014sdata=og2SYBpgrbpPj3vbi6ve1YjiqtrSR99HEph47Jf3IM8%3Dreserved=0;
 xmlns:mx="library://ns.apache.org/royale/mx"
[mxmlc] ^
[mxmlc]

Regards,

Liju


From: Alex Harui 
Sent: Thursday, June 11, 2020 11:06 AM
To: dev@royale.apache.org 
Cc: Arya Sankar (OSV) 
Subject: [EXTERNAL] Re: Migration of Adobe Flex to Apache Royale - Support 
needed

Hi Liju,

I posted a reply earlier, but maybe you are having subscription problems.

Are you migrating a Flex 3 application?  If so, then yes, the xmlns have to 
be changed to look like this:

  
xmlns:fx="https://nam03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009data=02%7C01%7Cliju.thomas.osv%40fedex.com%7C30ff97f9ec2649af5a6e08d80dcc566b%7Cb945c813dce641f884575a12c2fe15bf%7C1%7C0%7C637274518579342014sdata=og2SYBpgrbpPj3vbi6ve1YjiqtrSR99HEph47Jf3IM8%3Dreserved=0;
  xmlns:mx="library://ns.apache.org/royale/mx"

And you may need to add the compiler option: +configname=flex
Note the "+" instead of "-".

HTH,
-Alex

On 6/10/20, 9:13 PM, "Liju Thomas (OSV)" 
 wrote:

Hi Team,

I'm from Development Team for FedEx, we have an application built on 
Adobe F

Re: Migration of Adobe Flex to Apache Royale - Support needed

2020-06-10 Thread Alex Harui

Hi Liju,

The option -load-config=C:/.../royale-config.xml should not be there. 
 Are you specifying that or is that in some default launcher we have?  You'll 
know you have it right when it loads flex-config.xml (because of 
+configname=flex) instead of royale-config.xml

HTH,
-Alex

On 6/10/20, 10:52 PM, "Liju Thomas (OSV)"  
wrote:

Hey Alex,

Yes it is FLEX 3, I updated as per your comment, following error is coming. 
You may check the configuration:

 [echo] *** create 
D:\Work\Clients\FedEx\Apps\WGRT\VCWorkspace\SVN\WGRTFLEX/../WGRTFLEX/WGRTFreightIntegration.swf
 ***
[mxmlc] MXMLJSC
[mxmlc] -compiler.keep-generated-actionscript=false
[mxmlc] -compiler.debug=false
[mxmlc] 
+royalelib=C:/AppData/Roaming/npm/node_modules/@apache-royale/royale-js/frameworks/
[mxmlc] -compiler.actionscript-file-encoding=UTF-8
[mxmlc] -compiler.locale=
[mxmlc] -link-report=D:\/FLEX/../WGRTFLEX/externs.txt
[mxmlc] +configname=flex
[mxmlc] -default-size
[mxmlc] 800
[mxmlc] 1000
[mxmlc] 
-load-config=C:/AppData/Roaming/npm/node_modules/@apache-royale/royale-js/royale-asjs/frameworks/royale-config.xml
[mxmlc] -output=D:FLEX\WGRTFreightIntegration.swf
[mxmlc] --
[mxmlc] D:\FLEX/../WGRTFLEX/src/WGRTFLEX.mxml
[mxmlc] 6.7364493 seconds
[mxmlc] D:\WGRTFLEX\src\WGRTFLEX.mxml(2): col: 1 Error: This 
tag could not be resolved to an ActionScript class. It will be ignored.
[mxmlc]
[mxmlc] https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009data=02%7C01%7Caharui%40adobe.com%7C1461f139655a4a79fce708d80dcb978f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637274515361385816sdata=NaTwt7nmEHAZlKewX1YqGSax8R1hk9WXu1d7CBEWFdI%3Dreserved=0;
 xmlns:mx="library://ns.apache.org/royale/mx"
[mxmlc] ^
[mxmlc]
FLEX.mxml(2): col: 1 Error: This tag could not be resolved to an 
ActionScript class. It will be ignored.
[mxmlc]
[mxmlc] https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009data=02%7C01%7Caharui%40adobe.com%7C1461f139655a4a79fce708d80dcb978f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637274515361385816sdata=NaTwt7nmEHAZlKewX1YqGSax8R1hk9WXu1d7CBEWFdI%3Dreserved=0;
 xmlns:mx="library://ns.apache.org/royale/mx"
[mxmlc] ^
[mxmlc]

Regards,

Liju


From: Alex Harui 
Sent: Thursday, June 11, 2020 11:06 AM
To: dev@royale.apache.org 
Cc: Arya Sankar (OSV) 
Subject: [EXTERNAL] Re: Migration of Adobe Flex to Apache Royale - Support 
needed

Hi Liju,

I posted a reply earlier, but maybe you are having subscription problems.

Are you migrating a Flex 3 application?  If so, then yes, the xmlns have to 
be changed to look like this:

  
xmlns:fx="https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009data=02%7C01%7Caharui%40adobe.com%7C1461f139655a4a79fce708d80dcb978f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637274515361395812sdata=DKq3q7smafHdAd%2BULDEMqMocoje8lqIf5DQZAufLwfs%3Dreserved=0;
  xmlns:mx="library://ns.apache.org/royale/mx"

And you may need to add the compiler option: +configname=flex
Note the "+" instead of "-".

HTH,
-Alex

On 6/10/20, 9:13 PM, "Liju Thomas (OSV)" 
 wrote:

Hi Team,

I'm from Development Team for FedEx, we have an application built on 
Adobe Flex, since Flex is not longer supported after Dec 2020, we need to 
migrate the application to Apache Royale asap.

We followed the instruction mentioned in the Migration of Existing 
app<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__nam04.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Fapache.github.io-252Froyale-2Ddocs-252Fmigrate-2Dan-2Dexisting-2Dapp-26amp-3Bdata-3D02-257C01-257Caharui-2540adobe.com-257Ce3b1727569284ddc5acc08d80dbdbbbf-257Cfa7b1b5a7b34438794aed2c178decee1-257C0-257C1-257C637274455834763070-26amp-3Bsdata-3DwcwkQrK2fM1WeMwnXjPePrhfF-252BIJElRVhATgTd9YaXc-253D-26amp-3Breserved-3D0%26d%3DDwIGaQ%26c%3DfpIeS8RwmHkY2r_dFRL5tQ%26r%3Daanc4j4xsg3RIhiBfaN9onX6bLCpzFkPa2kojuuTVUQ%26m%3DSeJk0dxLDPsYL8VXY0OadeGUEoiksl06jaR1aCjcjGE%26s%3Di29z2pt5sfterZHon9FyHkoZJyZgVcHIP_pxkohMxo4%26e%3Ddata=02%7C01%7Caharui%40adobe.com%7C1461f139655a4a79fce708d80dcb978f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637274515361395812sdata=KOEgjJHcBnjXh3kituZjBteG7Xxhh6rVS%2FtNBM67vVQ%3Dreserved=0
 > however, we are facing some issue:


  1.  I have 
xmlns:mx="https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.adobe

Re: Migration of Adobe Flex to Apache Royale - Support needed

2020-06-10 Thread Liju Thomas (OSV)

Hey Alex,

Yes it is FLEX 3, I updated as per your comment, following error is coming. You 
may check the configuration:

 [echo] *** create 
D:\Work\Clients\FedEx\Apps\WGRT\VCWorkspace\SVN\WGRTFLEX/../WGRTFLEX/WGRTFreightIntegration.swf
 ***
[mxmlc] MXMLJSC
[mxmlc] -compiler.keep-generated-actionscript=false
[mxmlc] -compiler.debug=false
[mxmlc] 
+royalelib=C:/AppData/Roaming/npm/node_modules/@apache-royale/royale-js/frameworks/
[mxmlc] -compiler.actionscript-file-encoding=UTF-8
[mxmlc] -compiler.locale=
[mxmlc] -link-report=D:\/FLEX/../WGRTFLEX/externs.txt
[mxmlc] +configname=flex
[mxmlc] -default-size
[mxmlc] 800
[mxmlc] 1000
[mxmlc] 
-load-config=C:/AppData/Roaming/npm/node_modules/@apache-royale/royale-js/royale-asjs/frameworks/royale-config.xml
[mxmlc] -output=D:FLEX\WGRTFreightIntegration.swf
[mxmlc] --
[mxmlc] D:\FLEX/../WGRTFLEX/src/WGRTFLEX.mxml
[mxmlc] 6.7364493 seconds
[mxmlc] D:\WGRTFLEX\src\WGRTFLEX.mxml(2): col: 1 Error: This tag 
could not be resolved to an ActionScript class. It will be ignored.
[mxmlc]
[mxmlc] http://ns.adobe.com/mxml/2009; 
xmlns:mx="library://ns.apache.org/royale/mx"
[mxmlc] ^
[mxmlc]
FLEX.mxml(2): col: 1 Error: This tag could not be resolved to an ActionScript 
class. It will be ignored.
[mxmlc]
[mxmlc] http://ns.adobe.com/mxml/2009; 
xmlns:mx="library://ns.apache.org/royale/mx"
[mxmlc] ^
[mxmlc]

Regards,

Liju


From: Alex Harui 
Sent: Thursday, June 11, 2020 11:06 AM
To: dev@royale.apache.org 
Cc: Arya Sankar (OSV) 
Subject: [EXTERNAL] Re: Migration of Adobe Flex to Apache Royale - Support 
needed

Hi Liju,

I posted a reply earlier, but maybe you are having subscription problems.

Are you migrating a Flex 3 application?  If so, then yes, the xmlns have to be 
changed to look like this:

  
xmlns:fx="https://nam03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009data=02%7C01%7Cliju.thomas.osv%40fedex.com%7C95d62f533f7243b3794308d80dc96b0d%7Cb945c813dce641f884575a12c2fe15bf%7C1%7C1%7C637274506022941972sdata=jkg6T3sfAKJFQX7K9%2BNy5UjXVQXLZB6rc2Czd%2BVpDbQ%3Dreserved=0;
  xmlns:mx="library://ns.apache.org/royale/mx"

And you may need to add the compiler option: +configname=flex
Note the "+" instead of "-".

HTH,
-Alex

On 6/10/20, 9:13 PM, "Liju Thomas (OSV)"  
wrote:

Hi Team,

I'm from Development Team for FedEx, we have an application built on Adobe 
Flex, since Flex is not longer supported after Dec 2020, we need to migrate the 
application to Apache Royale asap.

We followed the instruction mentioned in the Migration of Existing 
app<https://urldefense.proofpoint.com/v2/url?u=https-3A__nam04.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Fapache.github.io-252Froyale-2Ddocs-252Fmigrate-2Dan-2Dexisting-2Dapp-26amp-3Bdata-3D02-257C01-257Caharui-2540adobe.com-257Ce3b1727569284ddc5acc08d80dbdbbbf-257Cfa7b1b5a7b34438794aed2c178decee1-257C0-257C1-257C637274455834763070-26amp-3Bsdata-3DwcwkQrK2fM1WeMwnXjPePrhfF-252BIJElRVhATgTd9YaXc-253D-26amp-3Breserved-3D0=DwIGaQ=fpIeS8RwmHkY2r_dFRL5tQ=aanc4j4xsg3RIhiBfaN9onX6bLCpzFkPa2kojuuTVUQ=SeJk0dxLDPsYL8VXY0OadeGUEoiksl06jaR1aCjcjGE=i29z2pt5sfterZHon9FyHkoZJyZgVcHIP_pxkohMxo4=
 > however, we are facing some issue:


  1.  I have 
xmlns:mx="https://nam03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.adobe.com%2F2006%2Fmxmldata=02%7C01%7Cliju.thomas.osv%40fedex.com%7C95d62f533f7243b3794308d80dc96b0d%7Cb945c813dce641f884575a12c2fe15bf%7C1%7C1%7C637274506022941972sdata=JAJjxp5Sq6Pl%2B9k8PxG4VP3mszmN9eDRjRREDxfORaE%3Dreserved=0;
 in my .MXML but if  I replace the line with 
xmlns:mx="library://ns.apache.org/royale/mx" Compilation fails with following 
error: .mxml(2): col: 1 Error: This tag could not be resolved to an 
ActionScript class. It will be ignored.
[mxmlc]
[mxmlc]

Re: Migration of Adobe Flex to Apache Royale - Support needed

2020-06-10 Thread Alex Harui

Hi Liju,

I posted a reply earlier, but maybe you are having subscription problems.

Are you migrating a Flex 3 application?  If so, then yes, the xmlns have to be 
changed to look like this:

  xmlns:fx="http://ns.adobe.com/mxml/2009;
  xmlns:mx="library://ns.apache.org/royale/mx"

And you may need to add the compiler option: +configname=flex
Note the "+" instead of "-".

HTH,
-Alex

On 6/10/20, 9:13 PM, "Liju Thomas (OSV)"  
wrote:

Hi Team,

I'm from Development Team for FedEx, we have an application built on Adobe 
Flex, since Flex is not longer supported after Dec 2020, we need to migrate the 
application to Apache Royale asap.

We followed the instruction mentioned in the Migration of Existing 
app
 however, we are facing some issue:


  1.  I have xmlns:mx="http://www.adobe.com/2006/mxml; in my .MXML but if  
I replace the line with xmlns:mx="library://ns.apache.org/royale/mx" 
Compilation fails with following error: .mxml(2): col: 1 Error: This tag could 
not be resolved to an ActionScript class. It will be ignored.
[mxmlc]
[mxmlc]

Migration of Adobe Flex to Apache Royale - Support needed

2020-06-10 Thread Liju Thomas (OSV)

Hi Team,

I'm from Development Team for FedEx, we have an application built on Adobe 
Flex, since Flex is not longer supported after Dec 2020, we need to migrate the 
application to Apache Royale asap.

We followed the instruction mentioned in the Migration of Existing 
app however, we 
are facing some issue:


  1.  I have xmlns:mx="http://www.adobe.com/2006/mxml; in my .MXML but if  I 
replace the line with xmlns:mx="library://ns.apache.org/royale/mx" Compilation 
fails with following error: .mxml(2): col: 1 Error: This tag could not be 
resolved to an ActionScript class. It will be ignored.
[mxmlc]
[mxmlc]

Migration of Adobe Flex to Apache Royale - Support needed

2020-06-10 Thread Liju Thomas (OSV)

Hi Team,

I'm from Development Team for FedEx, we have an application built on Adobe 
Flex, since Flex is not longer supported after Dec 2020, we need to migrate the 
application to Apache Royale asap.

We followed the instruction mentioned in the Migration of Existing 
app however, we 
are facing some issue:


  1.  I have xmlns:mx="http://www.adobe.com/2006/mxml; in my .MXML but if  I 
replace the line with xmlns:mx="library://ns.apache.org/royale/mx" Compilation 
fails with following error: .mxml(2): col: 1 Error: This tag could not be 
resolved to an ActionScript class. It will be ignored.
[mxmlc]
[mxmlc]

Re: Migration of Adobe Flex to Apache Royale - Support needed

2020-06-10 Thread Alex Harui

Hi Liju,

Are you migrating a Flex 3 application?  If so, then yes, the xmlns have to be 
changed to look like this:

  xmlns:fx="http://ns.adobe.com/mxml/2009; 
  xmlns:mx="library://ns.apache.org/royale/mx"

And you may need to add the compiler option: +configname=flex
Note the "+" instead of "-".

HTH,
-Alex

On 6/10/20, 11:13 AM, "Liju Thomas (OSV)"  
wrote:

Hi Team,

I'm from Development Team for FedEx, we have an application built on Adobe 
Flex, since Flex is not longer supported after Dec 2020, we need to migrate the 
application to Apache Royale asap.

We followed the instruction mentioned in the Migration of Existing 
app
 however, we are facing some issue:


  1.  I have xmlns:mx="http://www.adobe.com/2006/mxml; in my .MXML but if  
I replace the line with xmlns:mx="library://ns.apache.org/royale/mx" 
Compilation fails with following error: .mxml(2): col: 1 Error: This tag could 
not be resolved to an ActionScript class. It will be ignored.
[mxmlc]
[mxmlc]

Migration of Adobe Flex to Apache Royale - Support needed

2020-06-10 Thread Liju Thomas (OSV)

Hi Team,

I'm from Development Team for FedEx, we have an application built on Adobe 
Flex, since Flex is not longer supported after Dec 2020, we need to migrate the 
application to Apache Royale asap.

We followed the instruction mentioned in the Migration of Existing 
app however, we 
are facing some issue:


  1.  I have xmlns:mx="http://www.adobe.com/2006/mxml; in my .MXML but if  I 
replace the line with xmlns:mx="library://ns.apache.org/royale/mx" Compilation 
fails with following error: .mxml(2): col: 1 Error: This tag could not be 
resolved to an ActionScript class. It will be ignored.
[mxmlc]
[mxmlc]

Re: Migration of Adobe Flex to Apache Royale - Support needed

Re: Migration of Adobe Flex to Apache Royale - Support needed

Re: Migration of Adobe Flex to Apache Royale - Support needed

Re: Migration of Adobe Flex to Apache Royale - Support needed

RE: Migration of Adobe Flex to Apache Royale - Support needed

Re: Migration of Adobe Flex to Apache Royale - Support needed

RE: Migration of Adobe Flex to Apache Royale - Support needed

Re: Migration of Adobe Flex to Apache Royale - Support needed

Re: Migration of Adobe Flex to Apache Royale - Support needed

Re: Migration of Adobe Flex to Apache Royale - Support needed

Re: Migration of Adobe Flex to Apache Royale - Support needed

Re: Migration of Adobe Flex to Apache Royale - Support needed

Re: Migration of Adobe Flex to Apache Royale - Support needed

Migration of Adobe Flex to Apache Royale - Support needed

Migration of Adobe Flex to Apache Royale - Support needed

Re: Migration of Adobe Flex to Apache Royale - Support needed

Migration of Adobe Flex to Apache Royale - Support needed

17 matches

Site Navigation

Mail list logo

Footer information