Cytoscape Wiki|
← Revision 1 as of 2014-12-16 20:40:41
Size: 266
Comment:
|
← Revision 2 as of 2014-12-16 20:50:43 →
Size: 1740
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 4: | Line 4: |
| === Process === | |
| Line 7: | Line 5: |
| ==== Cytoscape 3 design goals ==== |
==== Cytoscape and OSGi ==== '''Cytoscape 3 design goals''': |
| Line 15: | Line 15: |
|
'''Definition of OSGi from Wikipedia:''' '''''The OSGi framework is a module system and service pla9orm for the Java programming language that implements a complete and dynamic component model, something that does not exist in standalone Java/VM environments. ApplicaAons or components (coming in the form of bundles for deployment) can be remotely installed, started, stopped, updated, and uninstalled without requiring a reboot; management of Java packages/ classes is specified in great detail. ApplicaAon life cycle management (start, stop, install, etc.) is done via APIs that allow for remote downloading of management policies. The service registry allows bundles to detect the addiAon of new services, or the removal of services, and adapt accordingly.''''' '''Important definitions:''' * OSGi is service-oriented * A '''bundle''' is the unit of access * Bundles can be started and stopped independently * Bundles implement services * Can be registered and unregistered * Generally, inter-bundle access is through a service * Enforced separation of API and Implementation – Rules are that you can depend on API bundles, but not implementation bundles ===== Anatomy of a Bundle ===== A bundle is a JAR with extra metadata: * Imports: The Java packages used by the bundle * Exports: Java packages in the bundle that other bundles are allowed to use (usually just API) * Activator: Triggered when bundle is started/stopped |
Introduction to Cytoscape App Development
Overview
Cytoscape and OSGi
Cytoscape 3 design goals:
- Scalability
- Performance
- Stability
- Application stability
- API stability
- Modularity
- Enforced by OSGi
Definition of OSGi from Wikipedia: The OSGi framework is a module system and service pla9orm for the Java programming language that implements a complete and dynamic component model, something that does not exist in standalone Java/VM environments. ApplicaAons or components (coming in the form of bundles for deployment) can be remotely installed, started, stopped, updated, and uninstalled without requiring a reboot; management of Java packages/ classes is specified in great detail. ApplicaAon life cycle management (start, stop, install, etc.) is done via APIs that allow for remote downloading of management policies. The service registry allows bundles to detect the addiAon of new services, or the removal of services, and adapt accordingly.
Important definitions:
- OSGi is service-oriented
A bundle is the unit of access
- Bundles can be started and stopped independently
- Bundles implement services
- Can be registered and unregistered
- Generally, inter-bundle access is through a service
- Enforced separation of API and Implementation – Rules are that you can depend on API bundles, but not implementation bundles
Anatomy of a Bundle
A bundle is a JAR with extra metadata:
- Imports: The Java packages used by the bundle
- Exports: Java packages in the bundle that other bundles are allowed to use (usually just API)
- Activator: Triggered when bundle is started/stopped