I attended SpringOne last week and there was alot of focus on Spring OSGi. The Spring committers are very active and pushing things forward. OSGi could even become the standard deployment model of J2EE applications within todays application servers.
In my mind I pictured a Magnolia with OSGi-support and to me that sounds promising and like a very good platform to stand on. Although, it is a large change and I doubt it could be possible without serious API-changes and redesign. Perhaps something for a future major release to consider. // Tobias Mattsson > -----Original Message----- > From: [email protected] [mailto:[EMAIL PROTECTED] > Sent: den 26 juni 2007 16:33 > To: [email protected] > Subject: Re: [magnolia-dev] module mechanism: OSGi? > > Am Freitag, 22. Juni 2007 schrieb Philipp Bracher: > [...] > > >> I had a quick look at FELIX (apache), what kind of projects do you > > >> recommend? > > Sorry, I can't really recommend anything because I read a lot early this > year > about OSGi but stopped playing around soon after I made my suggestions on > MAGNOLIA-608 and showing my interest in working on Magnolia/OSGi as Google > SoC project without any response. > > > After an other hour of research I would make the following statement: > > > > I like OSGi and think that magnolia can highly benefit of it. In case > > we use spring it will be a very good idea to use springs OSGi. Since > > OSGi would imply other architecture changes (services, ...) we > > proceed by using our own implementation. We add/change only a few > > things (update, module instantiation). We do also have additional > > concepts like having a GUI, ... > > > > The update mechanism is currently the last missing peace for > > releasing 3.1 and I think we should not invest more than two weeks > > for that. Definitely we should not change more apis as we already > > have done and introducing OSGi would definitely need a lot more changes. > > > > Never else I think we should not invest to much time into things > > which are solved much nicer by OSGi (deployment, registry, ...). > > > > When ever we will have enough courage and enough time to make such a > > move to spring I will be happy ;-) > > Spring/OSGi is a major change for Magnolia and I suggest creating a new > experimental branch where we can test different containers and setups and > gain experience. > > I don't understand "We do also have additional concepts like having a > GUI, ..." because Eclipse IDE has also a gui (a "fat" one) and is based on > Equinox - their own OSGi R4 implementation - > http://www.eclipse.org/equinox/. > Have a look at http://www.eclipse.org/equinox/server/http_quickstart.php > and > search the web for "server side eclipse" to find more about web-related > OSGi > stuff. > > O. > > > > ---------------------------------------------------------------- > for list details see > http://documentation.magnolia.info/docs/en/editor/stayupdated.html > ---------------------------------------------------------------- ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/docs/en/editor/stayupdated.html ----------------------------------------------------------------
