OSGi Technology, Eclipse and Convergence - Jeff McAffer, IBM
- 1. © copyright 2004 by OSGi Alliance All rights reserved. Converging with Eclipse and OSGi
- 2. © copyright 2004 by OSGi Alliance. All rights reserved. Pocket PC
- 3. © copyright 2004 by OSGi Alliance. All rights reserved. Linux/GTK
- 4. © copyright 2004 by OSGi Alliance. All rights reserved. GTK Standalone
- 5. © copyright 2004 by OSGi Alliance. All rights reserved. Mac/Carbon
- 6. © copyright 2004 by OSGi Alliance. All rights reserved. Integrated
- 7. © copyright 2004 by OSGi Alliance. All rights reserved. Observations • Each is running the same application code • Each is running on OSGi • Each uses third party libraries – not written for OSGi or Eclipse • Each looks and feels native to its environment The realities of a converged world
- 8. © copyright 2004 by OSGi Alliance. All rights reserved. Eclipse • Eclipse 3.0 based on OSGi R3++ • Platform for tooling and generic applications • Plug-in model based on OSGi bundles • Extension mechanism • GUI framework and native widget toolkit • 40+ mirrors: 100,000s of downloads
- 9. © copyright 2004 by OSGi Alliance. All rights reserved. OSGi meets Eclipse • OSGi is essential but not enough – Services – Dynamic bundle management • Component model that scales up to the desktop – 1000s of bundles – Declarative extensibility – Lazy installation and activation • UI model that scales down to the handheld – Common programming model – Native widget support Complementary Technologies
- 10. © copyright 2004 by OSGi Alliance. All rights reserved. Technical Challenge: Scaling • Desktop apps today have 1000s of bundles • Embedded applications increasingly componentized • Being lazy – Activate on use (Eclipse) – Extension Registry (Eclipse) – Declarative Services (RFC 80) What is needed, when it is needed
- 11. © copyright 2004 by OSGi Alliance. All rights reserved. Technical Challenge: Dynamics • Dynamic function – On-demand acquisition – Dynamic bundle install/uninstall • Dynamic data – Data migration between devices as needed – General purpose mechanism hard (years of research) – Domain solutions possible/available
- 12. © copyright 2004 by OSGi Alliance. All rights reserved. Technical Challenge: Going Native • Look and feel must be natural • Increase consumer acceptance • Use real window system widgets • Branding show-thru on custom UI libraries That’s running Java?!
- 13. © copyright 2004 by OSGi Alliance. All rights reserved. Eclipse RCP • Rich Client Platform – Runtime (OSGi + extension mechanism) – SWT (widget library) – JFace/UI (GUI framework libraries) – Update (bundle management agent) • Addresses the challenges • Production quality • Open-source • Shipping today
- 14. © copyright 2004 by OSGi Alliance. All rights reserved. embedded RCP (eRCP) • Eclipse Technology project • Nokia, Motorola, IBM et al • Eclipse on devices (i.e., embedded versions of) – Runtime (OSGi + infrastructure) – SWT (widget library) – JFace/UI (GUI framework libraries) – Update (bundle management agent) • Address embedded-specific issues – Speed, space, mobile function, …
- 15. © copyright 2004 by OSGi Alliance. All rights reserved. Summary • Keys to convergence – Scalability => Laziness – Deep integration – Dynamic behaviour • Eclipse and OSGi deliver applications across the enterprise from mobile devices to the desktop
- 16. © copyright 2004 by OSGi Alliance. All rights reserved. Other information • eRCP talk Wednesday • OSGi and Open source panel Thursday • eclipse.org