A few nights ago John Stevenson (@jR0cket) and I were fortunate enough to be taken through a explanation of OSGi by some of its key proponents: Neil Barlett (@njbarlett), Zoe Slattery (@zoe_slattery) and Alasdair Nottingham.
I have certainly battled JAR hell and have also experienced problems with keeping web and enterprise applications isolated from each other (manipulating parent delegation and CLASSPATHs anyone?). This has been throughout my Java career (~10 years now), but I had never investigated OSGi properly as an alternative. Why? Because I never spent the time investigating OSGi properly and I was under the strong impression that it was better suited for IDE, App Server and tooling development as opposed to application development.
So after a good couple of hours of discussion I came out with a greater appreciation for OSGi and the following conclusions.
Friday, July 15, 2011
Are We There Yet: OSGi - Are we there yet?
Are We There Yet: OSGi - Are we there yet?
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment