tag:blogger.com,1999:blog-5585468285320774280.post6992899464060995997..comments2023-09-09T02:39:03.647-07:00Comments on Walking, not falling: JSR 277 Could Be Great for OSGiBryan Atsatthttp://www.blogger.com/profile/03155624388914206954noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-5585468285320774280.post-32030532713915441292008-04-17T04:11:00.000-07:002008-04-17T04:11:00.000-07:00@nickmalthusThat's fine in theory, so long as the ...@nickmalthus<BR/><BR/>That's fine in theory, so long as the result of such an effort was actually an advance on OSGi and also provided a clean migration path for the very large number of existing OSGi bundles.<BR/><BR/>What we got in the EDR in late 2006 was neither of the above. JSR 277 as currently defined is far <I>less</I> powerful and useful than OSGi, and nowhere near as ambitious in its scope. This is despite OSGi being, as you put it, "just a band aid" which works on all versions of Java from 1.1 upwards. Remember, those ancient Java limitations <I>still exist today in Java 6</I>, which is why so many people are adopting OSGi, including Sun themselves who just announced that GlassFish V3 would use it.<BR/><BR/>If the JSR 277 expert group were to define a new module system that was more powerful than OSGi and included compatibility for "legacy" OSGi bundles then I think the majority of the OSGi community would be very pleased. That's exactly what Bryan (the author of this blog and a member of the JSR 277 expert group) has been trying for 2+ years to push Sun towards. And it seems like they might have actually started listening at last. <BR/><BR/>Keep up the good work, Bryan!Neil Bartletthttps://www.blogger.com/profile/08588098030811273044noreply@blogger.comtag:blogger.com,1999:blog-5585468285320774280.post-3853042625688843722008-04-16T14:15:00.000-07:002008-04-16T14:15:00.000-07:00In my opinion, there is good reason for the JSR 2...In my opinion, there is good reason for the JSR 277 group to take a fresh holistic perspective on module management and come up with something new. OSGI is many years old and is based on limitations and technologies that were a part of the old JVM 1.2 specification.OSGI was just a band aid to address legitimate limitations of the Java platform. <BR/><BR/>If Sun and others want to take a fresh approach and address the concept of modules from the top down I don't see why they shouldn't do so.nickmalthushttps://www.blogger.com/profile/13370462544006489908noreply@blogger.com