Bug 780636 (SOA-3075) - Need documentation created for JON EDS/Modeshape plugin
Summary: Need documentation created for JON EDS/Modeshape plugin
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-3075
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: Documentation, EDS
Version: 5.1.0 GA
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.2.0 GA
Assignee: David Le Sage
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-16 23:07 UTC by Marc Shirley
Modified: 2011-11-15 03:24 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-15 03:24:35 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-3075 0 None None None Never

Description Marc Shirley 2011-05-16 23:07:49 UTC
Affects: Documentation (Ref Guide, User Guide, etc.)
project_key: SOA

Need documentation for JON EDS/Modeshape plugin describing available connection properties, configuration properties, metrics, operations, etc. for all resource types that the plugin monitors.

Comment 1 Van Halbert 2011-05-17 12:35:54 UTC
What's the process for getting the RHQ documentation that's in the related admin ref. guide reworked and into the JON documentation?

Comment 2 David Le Sage 2011-07-18 03:11:59 UTC
As per IRC discussion....

Comment 3 Van Halbert 2011-07-25 21:05:23 UTC
Link: Added: This issue depends MODE-1227


Comment 4 Randall Hauch 2011-08-02 16:43:47 UTC
Changes to the ModeShape documentation to include a new chapter on the RHQ plugin have been integrated into the '2.5.x' branch. See MODE-1227 for details.

Comment 5 David Le Sage 2011-08-12 02:59:02 UTC
Release Notes Docs Status: Added: Not Required
Writer: Added: dlesage


Comment 8 David Le Sage 2011-11-15 00:22:02 UTC
No, this is in the Modeshape Ref Guide's Admin Console chapter, keeping it in sync with upstream (at this stage.)  Might move it if another location seems more logical next release.


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