You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openmeetings.apache.org by "SebastianWagner (Created) (JIRA)" <ji...@apache.org> on 2012/04/08 11:30:19 UTC
[jira] [Created] (OPENMEETINGS-146) Add mechanism to debug
LocalConnection better
Add mechanism to debug LocalConnection better
---------------------------------------------
Key: OPENMEETINGS-146
URL: https://issues.apache.org/jira/browse/OPENMEETINGS-146
Project: Openmeetings
Issue Type: Improvement
Components: UI
Affects Versions: 2.0 Apache Incubator Release
Reporter: SebastianWagner
Assignee: SebastianWagner
Fix For: 2.0 Apache Incubator Release
Currently sometimes the app switches to state where no call via LocalConnection to the SWF10 receives an answer.
As we directly call the LocalConnection Object in the canvas it is very difficult to find out which LocalConnection Call broke the whole application.
There should be a wrapper that wrapes every call via LC so we can debug which LocalConnection calls are currently processing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (OPENMEETINGS-146) Add mechanism to debug
LocalConnection better
Posted by "Maxim Solodovnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENMEETINGS-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maxim Solodovnik closed OPENMEETINGS-146.
-----------------------------------------
Assignee: Maxim Solodovnik (was: SebastianWagner)
Closing all old 'Resolved' issues
> Add mechanism to debug LocalConnection better
> ---------------------------------------------
>
> Key: OPENMEETINGS-146
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-146
> Project: Openmeetings
> Issue Type: Improvement
> Components: UI
> Affects Versions: 2.0 Apache Incubator Release
> Reporter: SebastianWagner
> Assignee: Maxim Solodovnik
> Fix For: 2.0 Apache Incubator Release
>
>
> Currently sometimes the app switches to state where no call via LocalConnection to the SWF10 receives an answer.
> As we directly call the LocalConnection Object in the canvas it is very difficult to find out which LocalConnection Call broke the whole application.
> There should be a wrapper that wrapes every call via LC so we can debug which LocalConnection calls are currently processing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (OPENMEETINGS-146) Add mechanism to debug
LocalConnection better
Posted by "SebastianWagner (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENMEETINGS-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
SebastianWagner resolved OPENMEETINGS-146.
------------------------------------------
Resolution: Fixed
> Add mechanism to debug LocalConnection better
> ---------------------------------------------
>
> Key: OPENMEETINGS-146
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-146
> Project: Openmeetings
> Issue Type: Improvement
> Components: UI
> Affects Versions: 2.0 Apache Incubator Release
> Reporter: SebastianWagner
> Assignee: SebastianWagner
> Fix For: 2.0 Apache Incubator Release
>
>
> Currently sometimes the app switches to state where no call via LocalConnection to the SWF10 receives an answer.
> As we directly call the LocalConnection Object in the canvas it is very difficult to find out which LocalConnection Call broke the whole application.
> There should be a wrapper that wrapes every call via LC so we can debug which LocalConnection calls are currently processing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira