Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

OSGi DevCon US 2010 Review


Published on

OSGi DevCon US review by Neil Bartlett at OSGi Users' Forum UK meeting on 27th April 2010.

Published in: Technology
  • Be the first to comment

OSGi DevCon US 2010 Review

  1. 1. OSGi DevCon 2010 Review Neil Bartlett
  2. 2. With Thanks...
  3. 3. Themes Enterprise OSGi Sun, Oracle and Jigsaw Tooling Future of App Servers Cloud Computing
  4. 4. News
  5. 5. OSGi Enterprise Specification Released
  6. 6. Enterprise Release JNDI Blueprint JDBC Remote Services JMX Remote Services Admin JPA SCA JTA Web Container
  7. 7. Next Release...? JCA OBR Asynchronous Command Shell Services Config Admin JMS extensions META-INF/services Multiple Extenders JAAS JPA weaving
  8. 8. Sun/Oracle Keynote
  9. 9. Sun/Oracle Keynote Re-iterated commitment to OSGi :-) Re-iterated commitment to Jigsaw :-( First public mention of “Java Module System Framework”
  10. 10. a.k.a. Qwylt Image Credit:
  11. 11. Qwylt APIs for interacting with modules SPIs for building module systems Platform for sharing classes between module systems
  12. 12. Pros Seems to offer interop between OSGi and Jigsaw at runtime Oracle claim to have implemented 90% of OSGi on Qwylt (“Lyra”), based on Felix code.
  13. 13. Cons No common module format Library authors targeting both module systems will have to compile, build and test twice.
  14. 14. Getting Involved Qwylt discussions likely to be held within a resurrected JSR 277 Though this requires resurrecting the JCP itself...
  15. 15. OSGi Cloud Computing Workshop
  16. 16. Tycho Moving to Eclipse
  17. 17. Tycho PDE gets a proper build system “Manifest first” vs “POM first” Already used by EGit & others
  18. 18. Interesting Talks
  19. 19. OSGi Best and Worst Practices
  20. 20. OSGi Best and Worst... Paul Vanderlei, Martin Lippert, Jeff McAffer, Chris Aniszczyk
  21. 21. OSGi Best and Worst... Don’t Program OSGi (use DS instead!) Use Import-Package (not Require- Bundle!) Mind your versions
  22. 22. Modular Architecture
  23. 23. Modular Architecture Kirk Knoernschild, Neil Bartlett Tutorial format: high level architecture from Kirk, low level details from me Focus on DS and simplicity seemed to go down well
  24. 24. Feedback “This presentation epitomises everyone [sic] that is wrong with software architecture. Nonesense [sic]” – Anonymous
  25. 25. OSGi Shells
  26. 26. OSGi Shells Robert Dunne (Paremus) Current situation is annoying for writers of tutorials & other docs Existing shells are underpowered RFC 147 describes the new standard shell, GoGo is a prototype
  27. 27. Paremus Nimble Shell and provisioning system Understands service dependencies, not just imports/requires. Not open source, but free to use (renewable licence)
  28. 28. Future of Application Servers Panel
  29. 29. Future of App Servers Host: John Rymer (Forrester Research) Panelists: Graham Charters (IBM), Glyn Normington (SpringSource), Greg Wilkins (Mortbay/Jetty), Oracle guy, JBoss guy.
  30. 30. Challenges Cloud deployment Reduced footprint Modularity and “profiles”
  31. 31. Memorable Quotes “Profiles are Rubbish!” – Greg Wilkins, Mortbay
  32. 32. Memorable Quotes Panelists asked for 3 core focus for future of their product
  33. 33. Graham Charters (IBM) “Enabling the OSGi development model in the enterprise...” “Enabling the OSGi development model in the enterprise...” and “Enabling the OSGi development model in the enterprise...”
  34. 34. ScalaModules
  35. 35. ScalaModules A DSL to ease development with OSGi services Complements DS, Blueprint etc Gives access to full power of low-level APIs... but much easier & safer to use.
  36. 36. ScalaModules Size of the core Scala library was discussed: 4Mb Clearly creates a barrier to adoption of Scala Needs to be modularised!
  37. 37. OSGi Cloud Workshop
  38. 38. Battle Of The “Cloud Picture” Slides
  39. 39. Image Credit: NASA
  40. 40. OSGi Cloud Workshop Lots of participants! Key Question: What needs to be specified, vs “value added” features that vendors may implement? Likelihood of a new “Cloud Expert Group” in the near future?