More Related Content
Similar to OSGi: Don't let me be Misunderstood
![[FREE PDF sample] Object Oriented Programming and Java Second Edition Danny P...](https://cdn.slidesharecdn.com/ss_thumbnails/34511-250218165353-f258b159-thumbnail.jpg?width=640&height=640&fit=bounds)
OSGi: Don't let me be Misunderstood
- 1. Don’t let me bemisunderstood Mikaël Barbero 6 June 2013 OSGi NOT SURE IF ACCIDENTALLY COMPLEX OR JUST ESSENTIALLY COMPLICATED
- 2. Geek and Pokecartoon, 27 July 2011: Graph Theory for Geeks (CC-BY-ND) Original site: http://geekandpoke.typepad.com/geekandpoke/2011/07/graph-theory-for-geeks.html
- 3.
- 4. java -cp "Test.jar;lib/*"my.package.MainClass
- 5. Execution Environment Factory/Listener patterns are key tomodularity Classes are identified by a unique name Java visibility are sufficient boundaries Module identify == Module artifact PermGen is permanent
- 7. W R ON G ! W R O N G ! W R O N G ! W R O N G !
- 8. minimizing changes needto support the evolution of itself and its dependencies Modularity
- 11. Execution Environment Classes are identified bya unique name Java visibility creates sufficient boundaries Mix up module identify and module artifact PermGen is permanent Factory/Listener patterns are key to modularity
- 13. CDLC/MIDP J2SE 1.3, 1.4, 5,6, 7... CDC/FP OSGI Min.
- 14. CDLC/MIDP J2SE 1.3, 1.4, 5,6, 7... CDC/FP OSGI Min. MANIFEST.MF Bundle-RequiredExecutionEnvironment: J2SE-1.6
- 15.
- 16. Execution Environment Classes are identified bya unique name Java visibility creates sufficient boundaries Mix up module identity and module artifact PermGen is permanent Factory/Listener patterns are key to modularity
- 17. guava-14.0.1.jar 15-Mar-2013 2.1 M 69e12f4c6aeac392555f1ea86fab82b5e5e31ad4 <groupId>com.google.guava</groupId> <artifactId>guava</artifactId> <version>14.0.1</version> Bundle-Vendor: Google,Inc Bundle-Name: com.google.guava Bundle-Version: 11.0.2.v201303041551
- 18.
- 19.
- 20. Execution Environment Classes are identified bya unique name Java visibility creates sufficient boundaries Mix up module identify and module artifact PermGen is permanent Factory/Listener patterns are key to modularity
- 21. Good fences makegood neighbors
- 22.
- 23.
- 24.
- 25.
- 26. Bundle com.acme.myApp; version=1.2 Bundleorg.logging.fmk; version=1.0.1 X package com.acme.core package com.acme.core.impl package org.logging.fmk.impl package org.logging.fmk
- 27. Bundle com.acme.myApp; version=1.2 Bundleorg.logging.fmk; version=1.0.1 package com.acme.core package com.acme.core.impl package org.logging.fmk.impl package org.logging.fmk
- 28. Bundle com.acme.myApp; version=1.2 Bundleorg.logging.fmk; version=1.0.1 package com.acme.core package com.acme.core.impl package org.logging.fmk.impl package org.logging.fmk
- 29.
- 30.
- 31. SemanticVersions major.minor.micro.qualifier • major: differentmajor versions are completely incompatible • minor: same major and different minor versions are compatible for consumer only (callers of the API) • micro: used to signal bufixes with no backward incompatibility issues • qualifier: build identity
- 32.
- 33. Execution Environment Classes are identified bya unique name Java visibility creates sufficient boundaries Mix up module identify and module artifact PermGen is permanent Factory/Listener patterns are key to modularity
- 34.
- 35.
- 36. My Killer Application Logging Framework v1 XXXFramework Logging Framework v2
- 38.
- 39. JavaVirtual Machine Application Extension Foundation Basic UI Convenience Borrowedfrom Peter Kriens presentation: http://www.slideshare.net/pkriens/osgi-and-java-modularity-1642537
- 40. Borrowed from PeterKriens presentation: http://www.slideshare.net/pkriens/osgi-and-java-modularity-1642537
- 41. Class Not Found Exception Borrowed from PeterKriens presentation: http://www.slideshare.net/pkriens/osgi-and-java-modularity-1642537
- 42. Class Object Identity == QualifiedClass Name + ClassLoader Object
- 43. Bundle com.acme.myApp; version=1.2 Bundleorg.logging.fmk; version=1.0.1 package com.acme.core;v=1.0 package com.acme.core.impl package org.logging.fmk.impl package org.logging.fmk;v=1.2
- 44. Bundle com.acme.myApp; version=1.2 Bundleorg.logging.fmk; version=1.0.1 X package com.acme.core.impl package org.logging.fmk.impl package com.acme.core;v=1.0 package org.logging.fmk;v=1.2
- 45. Bundle com.acme.myApp; version=1.2 Bundleorg.logging.fmk; version=1.0.1 package com.acme.core.impl package org.logging.fmk.impl package org.logging.fmk package com.acme.core;v=1.0 package org.logging.fmk;v=1.2
- 46. Import-package: com.acme.core;version="[1.0.2, 1.1.0)" ConsumerProvider [X.Y.Z.q, X+1.0.0) [X.Y.Z, X.Y+1.0)
- 47. Bundle com.acme.myApp; version=1.2 Bundleorg.logging.fmk; version=1.0.1 package com.acme.core.impl package org.logging.fmk.impl package org.logging.fmk package com.acme.core;v=1.0 package org.logging.fmk;v=1.2
- 48. Bundle com.acme.myApp; version=1.2 package com.acme.core.impl package com.acme.core;v=1.0 Bundleorg.logging.fmk; version=1.0.1 package org.logging.fmk.impl package org.logging.fmk;v=1.2 Bundle org.logging.fmk; version=2.3.0 package org.logging.fmk.impl package org.logging.fmk;v=2.2 Bundl exxx.fmk; version=1.2 package xxx package org.logging.fmk;v=[2.2,3) package xxx.exported;v=1.0 package org.logging.fmk;v=[1.2,2.0) package xxx.exported
- 49.
- 50. Execution Environment Classes are identified bya unique name Java visibility creates sufficient boundaries Mix up module identify and module artifact PermGen is permanent Factory/Listener patterns are key to modularity
- 51.
- 52. public class Activatorimplements BundleActivator { public void start(BundleContext bc) { ... } public void stop(BundleContext bc) { ... } }
- 53.
- 54. Execution Environment Classes are identified bya unique name Java visibility creates sufficient boundaries Mix up module identify and module artifact PermGen is permanent Factory/Listener patterns are keys to modularity
- 55.
- 56.
- 57.
- 58.
- 59.
- 60.
- 61. Declaring and gettingservices Programmatically Declaratively Service Registry ServiceTracker Decl. Services Blueprint
- 62.
- 63.
- 65. Minimizing changes needto support the evolution of itself and its dependencies Modularity
- 66. High cohesion Lowcoupling Encapsulation Modularity
- 68.
- 70. You want tobe an achiever?
- 71. Give Feedback 1} Signin www.eclipsecon.org 2} Select Session Evaluate 3} Vote +1, 0 or -1 ervisevichttp://www.flickr.com/photos/23979265@N07/4745520501/
- 72. Mikaël Barbero mikael.barbero@obeo.fr +Mikaël Barbero @mikbarbero Obeo http://www.obeo.fr (cc)TheAlieness GiselaGiardino²³ http://www.flickr.com/photos/36613169@N00/304120801/
- 73.