OSGi in Practice

So I was thinking about writing a modular program in Java. By modular I mean extensible via plugins, a l Firefox, Chrome, Launchy, etc., but of course on a simpler scale.

I got into reading about OSGi for this purpose but I don't find that it makes a whole lot of sense to me. I think this is because I can't quite understand how this fits together for my purpose. I hear a lot about writing plugins, but how would I go about writing the *core* to make it extensible via plugins?

Help would be appreciated. Read a whole lot and learnt a whole little.

Forget it, it's NP-complete.

Java
Stop wasting your time on gimmick technologies. It's incredibly simple in sane languages like C and Perl.

I plan to do something similar in C++ later on down the line, but I'd like to get something working in Java first.

I don't do Java, but I guess that you'd need to dynamically load Java modules, and then use reflection to see whether the module exports an interface you designed. Read the Java docs.

Sepples
Stop wasting your time on gimmick technologies. It's incredibly simple in sane languages like C and Python.

This can be done easily with TextMate, watch the screencast of me having sex with my TextMate.

Watch the screencast of me having sex with my TextMate.

>>6
I remember when I first needed to use dlopen(). It really is a walk in the park.

Using dlopen() is like a walk in the park, except the trees are rabid dinosaur mutants and the path is covered in chainsaws.

>>10
That's nothing! You should learn C.

OSGi
If there's just one thing that could be considered ENTERPRISE BULLSHITE, this is it.