Thanks Richard for the nice set of slides and congrats. Just a few comments on the slides (I admit I do not know that much about OSGI but at least I read some docs sometime :))
-In the beginning you mention legacy code and how it is naughty to use stuff like Class.forName. I think several frameworks use such reflection tricks and whether they are legacy code or not sometimes I need to use them. Recently my experience has been so at least with Apache XMLRPC and some REST frameworks (Jersey/Restlet). This seems really hard to fix when there is no support from the framework but if you need that technology what do you do? Is everything legacy if it is not OSGI tested? -You talk about lifecycle and how you can implement your own, mentioning that the rules will just be enforced by "you" then. The previous slide talks about resource management. Does OSGI actually enforce some resource management rules such as checking what threads/files/etc are created and when? -You discuss transitive dependencies and uses constraints. What is a "uses" constraint? I do not see it explained in the slides and I though it was only import or export in OSGI. -Thanks for the few pointers on using the gogo shell. I never found such an explanation of how to use the gogo shell on the Felix website so I am always completely lost with what it is and what I could do with it :). Maybe you could write something similar for the website, just a bit more extensive? That's all for me.. Teemu 2011/1/20 Richard S. Hall <[email protected]> > After some recent experiences I had with some developers trying to use OSGi > without even understanding the basics, I decided to work on a presentation > highlighting what you must understand about OSGi to use it. Please find it > on the presentations page: > > http://felix.apache.org/site/presentations.html > > The direct link to the PDF is here: > > > http://felix.apache.org/site/presentations.data/Learning_to_ignore_OSGi.pdf > > Comments welcome. > > -> richard > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
