Bug 616483 - JBossAS (5.x) Server resource type and its descendant resource types are missing from Managed Resources section of RHQ docs
Summary: JBossAS (5.x) Server resource type and its descendant resource types are miss...
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Documentation
Version: unspecified
Hardware: All
OS: All
urgent
medium vote
Target Milestone: ---
: ---
Assignee: Ian Springer
QA Contact: Mike Foley
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-20 14:53 UTC by Ian Springer
Modified: 2013-08-06 00:37 UTC (History)
2 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2012-08-22 23:52:04 UTC


Attachments (Terms of Use)

Description Ian Springer 2010-07-20 14:53:33 UTC
See http://www.rhq-project.org/display/JOPR2/Managed+Servers.

There is a child page for the JBossAS (4.x) Server type, but not for the 5.x type.

Comment 1 Charles Crouch 2010-07-20 15:05:16 UTC
Ian, can you work with Deon to make sure all of the updated plugin docs are being used in the product documentation

Comment 2 Deon Ballard 2010-07-20 17:44:21 UTC
I don't know if this is related to the docs posted on the RHQ wiki, but the generated plugindocs have the same name for both JBoss AS 4.x and 5.x/6.x plug-ins, so they both output to JBossAS_Server.xml and both have titles of simply "JBossAS Server." Maybe the generated wiki content has the same naming issue, so one version overwrites another when it is published.

Just an idea.

Comment 3 Ian Springer 2010-07-20 20:39:45 UTC
Deon, yep, that's probably what happened. I think in the past, I've just manually renamed one or both of the generated pages - certainly not ideal. It may be easiest just to add a hack to plugindoc along the lines of:

if (typeName.equals("JBossAS Server") { 
  filename += " (" + pluginName + " plugin)"; 
  pageTitle += " (" + pluginName + " plugin)"; 
}

Comment 4 Deon Ballard 2010-12-20 03:39:52 UTC
I am reassigning this to Ian just because I don't think anyone wants me to be the one who attempts to hack plugindoc. :)


Note You need to log in before you can comment on or make changes to this bug.