Last modified 4 years ago
Last modified on 10/07/08 16:07:18
Pages linking to PLUGIN_SUPPORT_LIB_BASE_R0:
TASK_INDEX
SandBox/S
SCS_WIKI_MAINTENANCE_R0
ITERATION_01
UNPLANNED_TEST_TRACKING_MAINTENANCE_R1b/ManualTests
PLUGIN_SUPPORT_LIB_HOT_ENABLE_R0
PLUGIN_SUPPORT_LIB_BASE_R1
TASK_INDEX
SandBox/S
SCS_WIKI_MAINTENANCE_R0
ITERATION_01
UNPLANNED_TEST_TRACKING_MAINTENANCE_R1b/ManualTests
PLUGIN_SUPPORT_LIB_HOT_ENABLE_R0
PLUGIN_SUPPORT_LIB_BASE_R1
Analysis
Overview
Depends on the chosen plug-in framework. We need a library that will reduce the effort of working with plug-ins.
Task requirements
- The library should have capabilities for
- Listing extension points of a given plug-in
- Listing extensions implementing a given extension point.
- Directly extending the extension points
- Extending an extension point, inheriting the given one.
- Easy instantiation of extension classes
- Getting plug-in meta information
- Find places in the application where it can be used and integrate it.
Task result
The result must be source code.
How to demo
Show an use of each of the required capabilities.
Design
The chosen plug-in framework is Apache Felix.
Implementation
For now we have our implementation in modularity module for starting the modules.
The current code can be easily converted into Apache Felix way to do that.
Comments
- Make diagram in the next revision. (Pav)
Log
- Analyzing : Pap - done(1:30h)
- Review: 2 by Tanya. It doesn't apply to the template. It is not clear enough what should be done for finishing the task. - 5 min
- Analyzing 2: Pap (20 min)
- Designing : Pavlina - 20 mins
- Implementing : Pavlina - 2d
- Review : Peko - 3 - 10mins - In my opinion Design and Implementation are poor in terms of the wiki, which is the explanations and howtos. Should be fixed in next revision.
- Testing :
