Bug 564534 - Inconsistent display of WAR package details
Summary: Inconsistent display of WAR package details
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Content
Version: 1.3
Hardware: All
OS: Linux
low
low
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact: Rajan Timaniya
URL:
Whiteboard:
Depends On:
Blocks: rhq_spearhead
TreeView+ depends on / blocked
 
Reported: 2010-02-13 03:14 UTC by Ondřej Žižka
Modified: 2013-09-02 07:19 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-02 07:19:54 UTC
Embargoed:

Attachments (Terms of Use)

Description Ondřej Žižka 2010-02-13 03:14:17 UTC 
StR:

1) Install Tomcat 5.5.28 and set up monitoring
   (can take one from EWS 1.0.1)
2) In Jon, go to Tomcat (8080) > Tomcat VHost (localhost) > Tomcat WAR (/admin)
3) Go to CONTENT > DEPLOYED > click "admin", notice the page layout
4) Go to CONTENT > NEW      > click "admin" - now the details are on separate page.

Clicking back button is inconvenient and the behavior is inconsistent...
Comment 1 wes hayutin 2010-02-16 16:54:58 UTC 
Temporarily adding the keyword "SubBug" so we can be sure we have accounted for all the bugs.

keyword:
new = Tracking + FutureFeature + SubBug
Comment 2 wes hayutin 2010-02-16 17:00:14 UTC 
making sure we're not missing any bugs in rhq_triage
Comment 3 Corey Welton 2010-02-16 20:24:24 UTC 
Should this be filed under Plugins?
Comment 4 Corey Welton 2010-12-16 13:48:38 UTC 
Rajan, please take a look at this one, see if you can figure out what's going on.
Comment 5 Ondřej Žižka 2010-12-16 13:56:47 UTC 
This will probably become obsolete once you switch to GWT. So I guess this can be closed as WONTFIX.
Comment 6 Mike Foley 2011-06-13 15:34:14 UTC 
obsolete after switching to GWT.
Comment 7 Heiko W. Rupp 2013-09-02 07:19:54 UTC 
Bulk closing of issues that were VERIFIED, had no target release and where the status changed more than a year ago.
Note You need to log in before you can comment on or make changes to this bug.