Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Bugzilla 165566"
Line 40: | Line 40: | ||
This feature will enable the MAX to use notifications to: | This feature will enable the MAX to use notifications to: | ||
− | + | <ol> | |
− | + | <li>Update relationship information by listening on relationship resources</li> | |
− | + | <li>Update service group members by subscribing to membership change events on service groups</li> | |
− | + | <li>Show different operational state of resources</li> | |
+ | <li>Show visually that a resource's properties have changed and which properties have changed</li> | ||
+ | </ol> | ||
</p> | </p> | ||
Latest revision as of 10:22, 12 December 2006
Contents
TPTP feature: 165566
Author: | Balan Subramanian |
email: | [1] |
Last updated: | December 12, 2006 |
Rough workload estimate for design/code/test in person weeks:
Process Sizing Design 1 Code 2 Test 1 Documentation 1 Total
5
Rough workload estimate for build and infrastructure in person days: 3.0
Requirement summary
TPTP today has a notification broker for which a WSDM provider is available in the build to manage download. This enables any plugin in the workbench to register with the broker and receive WS-Notifications from WSDM resources. The MAX is today registered as a listener but processes only PropertyChange events. This feature will enable the MAX to use notifications to:
- Update relationship information by listening on relationship resources
- Update service group members by subscribing to membership change events on service groups
- Show different operational state of resources
- Show visually that a resource's properties have changed and which properties have changed
User interactions
User interface
TBD