[ https://issues.jboss.org/browse/EMBJOPR-128?page=com.atlassian.jira.plugi... ]
Ondrej Zizka updated EMBJOPR-128:
---------------------------------
Assignee: Charles Crouch
> Link WAR's context URL from it's Summary tab
> --------------------------------------------
>
> Key: EMBJOPR-128
> URL: https://issues.jboss.org/browse/EMBJOPR-128
> Project: Embedded Jopr
> Issue Type: Feature Request
> Reporter: Ondrej Zizka
> Assignee: Charles Crouch
> Priority: Minor
>
> User's would definitely like to have a direct link to WAR's context URL.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.jboss.org/browse/EMBJOPR-127?page=com.atlassian.jira.plugi... ]
Ondrej Zizka reassigned EMBJOPR-127:
------------------------------------
Assignee: Charles Crouch
> Link app's modules from it's Summary tab
> ----------------------------------------
>
> Key: EMBJOPR-127
> URL: https://issues.jboss.org/browse/EMBJOPR-127
> Project: Embedded Jopr
> Issue Type: Feature Request
> Reporter: Ondrej Zizka
> Assignee: Charles Crouch
> Priority: Minor
>
> Apps that can carry modules, e.g. EARs can contain WARs, could have hyperlinks to these modules, which would lead to the respective module's EmbJopr page.
> Additionally, such module's Summary tab could link back to its parent.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Add Refresh button to Summary tab of Applications node and subnodes
-------------------------------------------------------------------
Key: EMBJOPR-106
URL: https://jira.jboss.org/jira/browse/EMBJOPR-106
Project: Embedded Jopr
Issue Type: Feature Request
Reporter: Ondrej Žižka
Summary tab of Applications node and specific types' subnodes (Wep Applications, etc.) lists the apps and shows their status. It would be convenient to have a refresh button that would stay on the same page (in both meanings - embjopr's page and pagination's page), only re-reading the actual state.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Nav tree JS object (Tree.Item) is not ready after page refresh, causing ScriptException: TypeError: Cannot call method "fireExpansionEvent"
-------------------------------------------------------------------------------------------------------------------------------------------
Key: EMBJOPR-101
URL: https://jira.jboss.org/jira/browse/EMBJOPR-101
Project: Embedded Jopr
Issue Type: Task
Reporter: Ondrej Žižka
Right after page is loaded and test thread is running, JavaScript function object `Tree.Item` is not initialized yet.
This function is created in an externally loaded file, admin-console/a4j/g/3_3_0.GAorg/richfaces/renderkit/html/scripts/tree-item.js .
This problem appears when we click() in tests on some tree node after page load.
It is unlikely that user will be clicking fast enough to trigger this error, moreover IMHO Firefox blocks JS execution until external JS files are all loaded (but not sure), so this is only problem for QA.
Currently we solve this by calling NavTree#waitUntilReady( int intervalMs, int retries ) - e.g. in getNavTreeArrow():
ejtt.navTree.waitUntilReady(100, 15);
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira