Hey Michael, nice to see you around here! While I haven't read the book, it seems to be the result of a master thesis or the like. Magnolia has in the past discussed the topic but found that for us, the cost of going OSGI outweighs the benefit, especially compared with our existing module mechanism.
One of the biggest perceived benefits of OSGi is the hot deploy mechanism. We don't have that in Magnolia. But we haven't seen any desire by customers to hot deploy. Besides, Magnolia's distributed architecture and module lifecycle management make it easy to install or upgrade modules without service interruption. For what its worth, I have heard that competing products that sport OSGi will be rebooted after a module installation anyways, to ensure that it really works (seems it doesn't otherwise). In other words, while the promise is there, the reality is different. Or are you mainly interested in the topic for its dependency management? Regards - Boris -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=aab62258-863d-41d3-8362-5129890284b4 ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
