Look at the commits and see if the change I made is in the source. Make sure you delete all of your bin/js-debug folders.
HTH, -Alex From: Serkan Taş <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Tuesday, May 7, 2019 at 7:48 AM To: "[email protected]" <[email protected]> Subject: Re: Work on Emulation Hi Alex, After getting the latest version I am still getting the same error. How can I check that I pulled the version that you have fixed ? Thanks, Serkan 25.04.2019 08:46 tarihinde Alex Harui yazdı: File a bug an attach _Super_UserOps.js and _Super_UserOps.as and UserOps.js and UserOps.as Thanks, -Alex From: Serkan Taş <[email protected]><mailto:[email protected]> Reply-To: "[email protected]"<mailto:[email protected]> <[email protected]><mailto:[email protected]> Date: Wednesday, April 24, 2019 at 8:52 PM To: "[email protected]"<mailto:[email protected]> <[email protected]><mailto:[email protected]> Subject: Re: Work on Emulation Hi Alex, I am still working on the issue which is related with third party library that we have discussed months ago. I am not sure how to get rid of the error below, may be anyone on the list have an idea. I am getting error below on chrome console: [cid:[email protected]] Here is the _Super_UserOps.as source piece which couses the error : model_internal::initialize(); converted to _Super_UserOps.js : com.adobe.fiber.core.model_internal.org.apache.royale.utils.Language.closure(this.http_$$www_adobe_com$2008$flex$model$internal__initialize, this, 'http://www.adobe.com/2008/flex/model/internal::initialize')(); content of the file model_internal.as : package com.adobe.fiber.core { public namespace model_internal = "http://www.adobe.com/2008/flex/model/internal";<http://www.adobe.com/2008/flex/model/internal>; } Ant the class piece which initialize the fault and and result functions that is the parent class of _Super_UserOps.as : model_internal function initialize() : void { this.serviceControl.addEventListener(ResultEvent.RESULT,model_internal::propagateEvents); this.serviceControl.addEventListener(FaultEvent.FAULT,model_internal::propagateEvents); } Any help kindly appreciated, Thanks Serkan 13.04.2019 00:34 tarihinde Alex Harui yazdı: Hi Serkan, Does it call the faultHandler instead? If so, there should be an error message in the fault event. What kind of service is UserOps? I would set breakpoints and debug to make sure it actually sent something (and maybe use a network monitor to see what was sent and to where). And then verify that the code that finally sends (maybe via XmlHTTPRequest) also set up listeners for events and set breakpoints on those low-level event handlers. You can also use the network monitor against the Flex app and compare what is being sent to what Royale is sending. HTH, -Alex On 4/12/19, 2:25 PM, "Serkan Taş" <[email protected]><mailto:[email protected]> wrote: Hi Alex, I have service call in my project. <userops:UserOps id="userOpsService" result="userOpsService_resultHandler(event)" fault="userOpsService_faultHandler(event)" /> Normally, I expect to call the result method userOpsService_resultHandler for successfull operations, but it does not. Which way I should go through to find out what is going on after calling the service ? Thanks, Serkan
