OSGi Best and Worst Practices

23
OSGi Best and Worst Practices Chris Aniszczyk — Red Hat Jeff McAffer — EclipseSource Martin Lippert — it-agile Paul VanderLei — Band XI

description

A presentation I gave with Jeff McAffer, Paul Vanderlei and Martin Lippert at EclipseCon 2010.

Transcript of OSGi Best and Worst Practices

Page 1: OSGi Best and Worst Practices

OSGi Best and Worst Practices

Chris Aniszczyk — Red HatJeff McAffer — EclipseSource

Martin Lippert — it-agilePaul VanderLei — Band XI

Page 2: OSGi Best and Worst Practices

Don’t Program OSGi

Page 3: OSGi Best and Worst Practices
Page 4: OSGi Best and Worst Practices

Sometimes it better not to know

Ignorance is bliss

Page 5: OSGi Best and Worst Practices

It's bad mojo to pollute the

POJO

Page 6: OSGi Best and Worst Practices

Your code sucks.Versioning can help.

Page 7: OSGi Best and Worst Practices

Good fences make good neighbors

Page 8: OSGi Best and Worst Practices

Size Does Matter

Page 9: OSGi Best and Worst Practices

Manage your dependencies

Page 10: OSGi Best and Worst Practices

Useservices

Page 11: OSGi Best and Worst Practices
Page 12: OSGi Best and Worst Practices
Page 13: OSGi Best and Worst Practices

Not everything should be a service

Page 14: OSGi Best and Worst Practices

...and OSGi made all the apps dynamic

Page 15: OSGi Best and Worst Practices

The Easter Bunny is dead

Page 16: OSGi Best and Worst Practices
Page 17: OSGi Best and Worst Practices

If you don't test it,it doesn't work!

Page 18: OSGi Best and Worst Practices

OSGi is not a religion

Page 19: OSGi Best and Worst Practices
Page 20: OSGi Best and Worst Practices

Lets look at some controversy

Now some controversy

Page 21: OSGi Best and Worst Practices

Require-Bundle Import-Package

Page 22: OSGi Best and Worst Practices

Services or Extensions?

Page 23: OSGi Best and Worst Practices

http://equinoxosgi.org

Got Questions?