Hi Alex,
workFlowManager method is there in the MXML file inside <mx:Script>
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 <aha...@adobe.com.INVALID>
Sent: Thursday, June 11, 2020 12:06 PM
To: dev@royale.apache.org <dev@royale.apache.org>
Cc: Arya Sankar (OSV) <arya.sankar....@fedex.com>
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)" <liju.thomas....@fedex.com.INVALID>
wrote:
Hi Alex,
I have corrected it. Errors are still same.
createsrcswf:
[echo] *** create D:\<fakepath>\FLEX/../FLEX/Integration.swf ***
[mxmlc] MXMLJSC
[mxmlc] -compiler.keep-generated-actionscript=false
[mxmlc] -compiler.debug=false
[mxmlc]
+royalelib=C:/Users/<fakepath>/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:\<fakepath>/FLEX/../FLEX/externs.txt
[mxmlc] +configname=flex
[mxmlc] -default-size
[mxmlc] 800
[mxmlc] 1000
[mxmlc]
-load-config=C:/Users/<fakepath>/AppData/Roaming/npm/node_modules/@apache-royale/royale-js/royale-asjs/frameworks/flex-config.xml
[mxmlc] -output=D:\<fakepath>FLEX\Integration.swf
[mxmlc] --
[mxmlc] D:\<fakepath>/src/FLEX.mxml
[mxmlc] D:\<fakepath>FLEX.mxml Error: interface method workFlowManager
in interface IManagedComponent not implemented by class FLEX
[mxmlc]
[mxmlc]
[mxmlc] D:\<fakepath>FLEX.mxml Error: interface method displayErrors in
interface IManagedComponent not implemented by class FLEX
Regards,
Liju
________________________________
From: Alex Harui <aha...@adobe.com.INVALID>
Sent: Thursday, June 11, 2020 11:26 AM
To: dev@royale.apache.org <dev@royale.apache.org>
Cc: Arya Sankar (OSV) <arya.sankar....@fedex.com>
Subject: [EXTERNAL] Re: Migration of Adobe Flex to Apache Royale - Support
needed
Hi Liju,
The option -load-config=C:/<fakepath>.../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)"
<liju.thomas....@fedex.com.INVALID> 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:/<fakepath>AppData/Roaming/npm/node_modules/@apache-royale/royale-js/frameworks/
[mxmlc] -compiler.actionscript-file-encoding=UTF-8
[mxmlc] -compiler.locale=
[mxmlc] -link-report=D:\<fakepath>/FLEX/../WGRTFLEX/externs.txt
[mxmlc] +configname=flex
[mxmlc] -default-size
[mxmlc] 800
[mxmlc] 1000
[mxmlc]
-load-config=C:/<fakepath>AppData/Roaming/npm/node_modules/@apache-royale/royale-js/royale-asjs/frameworks/royale-config.xml
[mxmlc] -output=D:<fakepath>FLEX\WGRTFreightIntegration.swf
[mxmlc] --
[mxmlc] D:\<fakepath>FLEX/../WGRTFLEX/src/WGRTFLEX.mxml
[mxmlc] 6.7364493 seconds
[mxmlc] D:\<fakepath>WGRTFLEX\src\WGRTFLEX.mxml(2): col: 1 Error:
This tag could not be resolved to an ActionScript class. It will be ignored.
[mxmlc]
[mxmlc] <mx:Application
xmlns:fx="https://nam03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009&data=02%7C01%7Cliju.thomas.osv%40fedex.com%7C1b59ffa3c1de410237a308d80dd1ea58%7Cb945c813dce641f884575a12c2fe15bf%7C1%7C0%7C637274542519901597&sdata=gt%2BkQJTW9cLZ4AeHYnVUW9OEYCC34a3aIoe0WbXYRhs%3D&reserved=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] <mx:Application
xmlns:fx="https://nam03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009&data=02%7C01%7Cliju.thomas.osv%40fedex.com%7C1b59ffa3c1de410237a308d80dd1ea58%7Cb945c813dce641f884575a12c2fe15bf%7C1%7C0%7C637274542519901597&sdata=gt%2BkQJTW9cLZ4AeHYnVUW9OEYCC34a3aIoe0WbXYRhs%3D&reserved=0";
xmlns:mx="library://ns.apache.org/royale/mx"
[mxmlc] ^
[mxmlc]
Regards,
Liju
________________________________
From: Alex Harui <aha...@adobe.com.INVALID>
Sent: Thursday, June 11, 2020 11:06 AM
To: dev@royale.apache.org <dev@royale.apache.org>
Cc: Arya Sankar (OSV) <arya.sankar....@fedex.com>
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%2F2009&data=02%7C01%7Cliju.thomas.osv%40fedex.com%7C1b59ffa3c1de410237a308d80dd1ea58%7Cb945c813dce641f884575a12c2fe15bf%7C1%7C0%7C637274542519901597&sdata=gt%2BkQJTW9cLZ4AeHYnVUW9OEYCC34a3aIoe0WbXYRhs%3D&reserved=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)"
<liju.thomas....@fedex.com.INVALID> 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://nam03.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%3D&data=02%7C01%7Cliju.thomas.osv%40fedex.com%7C1b59ffa3c1de410237a308d80dd1ea58%7Cb945c813dce641f884575a12c2fe15bf%7C1%7C0%7C637274542519901597&sdata=gEMR9IRf4wOi2sCY5vqq21WWEB8rNQfGxpOQpzsagWw%3D&reserved=0
> 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%2Fmxml&data=02%7C01%7Cliju.thomas.osv%40fedex.com%7C1b59ffa3c1de410237a308d80dd1ea58%7Cb945c813dce641f884575a12c2fe15bf%7C1%7C0%7C637274542519901597&sdata=Bj77p0uuBpiOANkiqR5astAJCjOifZLWjuL2ude1%2BrA%3D&reserved=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] <mx:Application
xmlns:mx="library://ns.apache.org/royale/mx"
2. If I change the url to library://ns.apache.org/royale/basic I
get huge number of errors:
.mxml Error: interface method workFlowManager in interface
IManagedComponent not implemented by class WGRTFLEX
Above interface is impplemented in the MXML file under <mx:Script>
<