Using OSGi Bundles in NetBeans Modules and vice versa

1. Frankenstein's IDE Anton Epple Eppleton IT Consulting http://www.eppleton.de Frankenstein's IDE: Running NetBeans on OSGi and vice versa

3. Service Infrastructure

4. Project netigso: bringing it all together

5. Demos

7. Plugins & Updates

8. Dynamic Service Infrastructure

9. Dependency management

10. Controlled API export (information hiding) Module Systems like OSGi & NetBeans Module System add this

12. Usable as independent platform for many years

13. Used on client & server

14. Many commercial and institutional users ( Nokia, Boeing, UNESCO, EADS, US Army ... )

15. Duke's Choice Award 2009

16. Duke's Choice Award 2009 What's the difference between OSGi and NB Platform?

18. Basic Services provide reusable functionality

19. API/SPI Modules provide Extension Points and Utility Classes

20. User Modules provide application functionality

22. Basic Services provide reusable functionality

23. API/SPI Modules provide Extension Points and Utility Classes

24. User Modules provide application functionality

26. Starts the Modules

27. ClassLoader: Every Module has it's own classloader. It can only load classes from other Modules if it has declared a dependency. Loading is then delegated to the other modules ClassLoader

29. Starts the Modules

30. ClassLoader: Every Module has it's own classloader. It can only load classes from other Modules if it has declared a dependency. Loading is then delegated to the other modules ClassLoader

31. Tip : Cross-check mailing list for third-party lib problems

33. Version

34. Public API

37. Version

38. Public API

40. Module System Meta-Data: NetBeans OSGi Identifier OpenIDE-Module: X Bundle-SymbolicName: X Version number OpenIDE-Module-Specification-Version: 7.3 Bundle-Version: 7.3 Activator OpenIDE-Module-Install: x.y.z.Activator Bundle-Activator: x.y.z.Activator Exported Packages OpenIDE-Module-Public-Packages: x.y.z Export-Package: x.y.z Imported Dependencies OpenIDE-Module-Module-Dependencies: another.module > 2.1 Require-Bundle: another.module;bundle-version="(2.1 )"

41. Module System Conclusion: Great minds think alike … but not always

43. Resolved

48. Service Infrastructure

49. Project netigso: bringing it all together

50. Demos

52. Dynamic Services

53. Declarative Services

54. Eclipse Extension Points

55. ...

57. + Listening for Changes

58. + Lazy Loading

59. + Ordering

61. Extension points are folders in the FileSystem

62. Extensions are virtual files in the FileSystem

63. Files can represent resources or instances

66. One extension can contribute to an indefinite number of Extension points

67. Extension point definer queries registry when needed ( lazy loading )

68. Extensions need not be associated with executable Java code

71. Service Infrastructure

72. Project netigso: bringing it all together

73. Demos

75. OSGi 4.2 Distributed OSGi: Use the same code to work with local and remote services

77. http://wiki.netbeans.org/OSGiAndNetBeans

83. XML registry & Lookup works

84. Project Netigso Runtime: When a bundle is available, launch embedded felix: configMap.put(&quot;felix.cache.profiledir&quot;, cache); configMap.put(&quot;felix.cache.dir&quot;, cache); configMap.put(Constants.FRAMEWORK_STORAGE, cache); activator = new NetigsoActivator(); // listen to changes List<BundleActivator> activators = new ArrayList<BundleActivator>(); activators.add(activator); configMap.put(&quot;felix.systembundle.activators&quot;, activators); felix = new Felix(configMap); felix.init();

85. Project Netigso Expose all Modules as bundles to felix: private static final InputStream fakeBundle(Module m) throws IOException { // create in memory jar containing manifest for OSGi container ByteArrayOutputStream os = new ByteArrayOutputStream(); Manifest man = new Manifest(); man.getMainAttributes().putValue(&quot;Manifest-Version&quot;, &quot;1.0&quot;); man.getMainAttributes().putValue(&quot;Bundle-ManifestVersion&quot;, &quot;2&quot;); .... JarOutputStream jos = new JarOutputStream(os, man); jos.close(); return new ByteArrayInputStream(os.toByteArray()); } // later inject the Module ClassLoader into the Bundle

86. Project Netigso Expose all Bundles as Modules to Module system: final class NetigsoModule extends Module { final Bundle bundle; private NetigsoLoader loader; ... @Override public String getCodeName() { return bundle.getSymbolicName(); } @Override public String getCodeNameBase() { return bundle.getSymbolicName(); } ...

88. OSGi

89. Service Infrastructure

90. Project Netigso

91. Demo

93. Example: Felix Remote Shell

94. Diagnosis and Management Tool

95. telnet localhost 6666

96. Installing and uninstalling bundles

98. HTTPService serves SUDOKU game

99. RPC Layer for communication between JavaScript frontend and server

100. Based on Eclipse Equinox

101. In Suite add to project.properties: run.args.extra=--nosplash -J-Dorg.osgi.service.http.port=8080

107. Modules and Bundles can communicate & depend on each other

108. Standard services are running without problems (J1)

109. Advanced Examples run in NetBeans

110. My next project: Running Glassfish

111. Blog: http://eppleton.sharedhost.de/blog

112. Q&A