[#HQ-305] Implement a screen for deep-dive Karaf Features

Fuse HQ

HQ-146

Implement a screen for deep-dive Karaf Features

Created: 05/Nov/09 04:52 PM Updated: 23/Oct/12 02:20 PM

Component/s:

Affects Version/s:

None

Fix Version/s:

4.1

All

Comments

Change History

Sort Order:

[ Permlink | « Hide ]

David Grigglestone added a comment - 06/Nov/09 06:30 PM

Based on feedback and ideas to date:

This screen will be attached as a sub-tab of the "Views" tab of HQ server resources of the type "KARAF" ("KARAF" is subject to change).
The sub-tab title will be "Features"
Tab will display a table with a row of action buttons above
- The Karaf admin MBean ObjectName will be retrieved from the config response using the key "karafFeaturesName"
- Values for table will be obtained by getting the "Features" JMX attribute
Table will have following columns (obtained using CompositData key from tabular data):
- Name ("Name")
- Version ("Version")
- Installed ("Installed")
- Bundles ("Bundles") .. this is an array of Strings so looking for ways to render .. maybe we show as a comma delimited list and if selected it appears as a popup table of all values (the delimited string could end in "..." if everything cannot be displayed within the cell)
- Dependencies ("Dependencies") .. this is a table (JMX TabularData) of feature "Name" and "Version" so again looking for ways to render .. maybe we show as a comma delimited list and if selected it appears as a popup table of all name/version values (the delimited string could end in "..." if everything cannot be displayed within the cell)
- Configurations ("Configurations").. this is a table (JMX TabularData) of configuration "PID" and "Elements" so again looking for ways to render .. this is further complicated by "Elements" being a table (JMX TabularData) of "Key" and "Value" pairs
Action buttons:
- "Install"
  - applicable to a single selected instance [can't do multiples as the JMX API does not support it .. but should we support impression of multiples by making multiples calls to the backend?], calls the JMX operation "installFeature" with 2 params:
    - param1 = the name of the selected feature
    - param2 = the version of the selected feature
- "Uninstall"
  - applicable to a single selected instance [can't do multiples as the JMX API does not support it .. but should we support impression of multiples by making multiples calls to the backend?], calls the JMX operation "uninstallFeature" with 2 params:
    - param1 = the name of the selected feature
    - param2 = the version of the selected feature

[ Show » ]

David Grigglestone added a comment - 06/Nov/09 06:30 PM Based on feedback and ideas to date:

This screen will be attached as a sub-tab of the "Views" tab of HQ server resources of the type "KARAF" ("KARAF" is subject to change).
The sub-tab title will be "Features"
Tab will display a table with a row of action buttons above
- The Karaf admin MBean ObjectName will be retrieved from the config response using the key "karafFeaturesName"
- Values for table will be obtained by getting the "Features" JMX attribute
Table will have following columns (obtained using CompositData key from tabular data):
- Name ("Name")
- Version ("Version")
- Installed ("Installed")
- Bundles ("Bundles") .. this is an array of Strings so looking for ways to render .. maybe we show as a comma delimited list and if selected it appears as a popup table of all values (the delimited string could end in "..." if everything cannot be displayed within the cell)
- Dependencies ("Dependencies") .. this is a table (JMX TabularData) of feature "Name" and "Version" so again looking for ways to render .. maybe we show as a comma delimited list and if selected it appears as a popup table of all name/version values (the delimited string could end in "..." if everything cannot be displayed within the cell)
- Configurations ("Configurations").. this is a table (JMX TabularData) of configuration "PID" and "Elements" so again looking for ways to render .. this is further complicated by "Elements" being a table (JMX TabularData) of "Key" and "Value" pairs
Action buttons:
- "Install"
  - applicable to a single selected instance [can't do multiples as the JMX API does not support it .. but should we support impression of multiples by making multiples calls to the backend?], calls the JMX operation "installFeature" with 2 params:
    - param1 = the name of the selected feature
    - param2 = the version of the selected feature
- "Uninstall"
  - applicable to a single selected instance [can't do multiples as the JMX API does not support it .. but should we support impression of multiples by making multiples calls to the backend?], calls the JMX operation "uninstallFeature" with 2 params:
    - param1 = the name of the selected feature
    - param2 = the version of the selected feature

[ Permlink | « Hide ]

Amit Verma added a comment - 15/Dec/09 05:41 AM

Checked in the features tab.