<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Simon Zambrovski&#187; Simon Zambrovski | Tags : OSGi</title>
	<atom:link href="http://simon.zambrovski.org/tag/osgi/feed/" rel="self" type="application/rss+xml" />
	<link>http://simon.zambrovski.org</link>
	<description>"One Cannot Not Communicate" - Watzlawick</description>
	<lastBuildDate>Thu, 17 Jun 2010 19:39:09 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>OSGi: Why Modularity is Important.</title>
		<link>http://simon.zambrovski.org/2008/09/osgi-why-modularity-is-important/</link>
		<comments>http://simon.zambrovski.org/2008/09/osgi-why-modularity-is-important/#comments</comments>
		<pubDate>Wed, 10 Sep 2008 10:21:11 +0000</pubDate>
		<dc:creator>Simon</dc:creator>
				<category><![CDATA[eclipse]]></category>
		<category><![CDATA[technology]]></category>
		<category><![CDATA[bundle]]></category>
		<category><![CDATA[Event]]></category>
		<category><![CDATA[framework]]></category>
		<category><![CDATA[hamburg]]></category>
		<category><![CDATA[Hotel East]]></category>
		<category><![CDATA[OSGi]]></category>
		<category><![CDATA[Peter Kriens]]></category>

		<guid isPermaLink="false">http://simon.zambrovski.org/2008/09/osgi-why-modularity-is-important/</guid>
		<description><![CDATA[
Yesterday, the 
OSGi session took place in 
Hotel East in Hamburg. 
Peter Kriens, the OSGi evangelist showed a wonderful 
Zen Presentation on OSGi. I wrote a lot during his talk which happens to me very seldom. Here are the core statements I understood:

The core difference between usual plugin architectures and OSGi is that OSGi concentrates [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://farm4.static.flickr.com/3250/2844821687_ea54b10e51_m.jpg" style="border: 1px solid black; margin: 5px" width="120" height="180" alt="OSGi1"/><img src="http://farm4.static.flickr.com/3172/2844822729_ed696da911_m.jpg" style="border: 1px solid black; margin: 5px" width="180" height="120" alt="OSGi2"/><img src="http://farm4.static.flickr.com/3012/2844827273_332a7c565e_m.jpg" style="border: 1px solid black; margin: 5px" width="120" height="180" alt="OSGi3" /></p>
<p>Yesterday, the 
<a  href="http://www.techjava.de/topics/2008/09/osgi-session-in-east-hotel-hamburg/" onclick="javascript:pageTracker._trackPageview('/external/www.techjava.de/topics/2008/09/osgi-session-in-east-hotel-hamburg/');" >OSGi session</a> took place in 
<a  href="http://www.east-hamburg.de/" onclick="javascript:pageTracker._trackPageview('/external/www.east-hamburg.de/');" >Hotel East</a> in Hamburg. 
<a  href="http://www.aqute.biz/Main/HomePage" onclick="javascript:pageTracker._trackPageview('/external/www.aqute.biz/Main/HomePage');" >Peter Kriens</a>, the OSGi evangelist showed a wonderful 
<a  href="http://www.presentationzen.com/" onclick="javascript:pageTracker._trackPageview('/external/www.presentationzen.com/');" >Zen Presentation</a> on OSGi. I wrote a lot during his talk which happens to me very seldom. Here are the core statements I understood:</p>
<ul>
<li>The core difference between usual plugin architectures and OSGi is that OSGi concentrates on collaboration of the components.</li>
<li>OSGi delivers a controlled environment, in which the question if a component runs or not can be answered in beforehand.</li>
<li>OSGi bundles use metadata (about versions, dependencies, etc) to predict an error, not discover it in runtime.</li>
<li>OSGi has a very narrow API containing the minimal common part.</li>
<li>OSGi consists of module, life cycle and services layers. The initially developed services layer required smart class loading mechanisms (module layer).</li>
</ul>
<ol>
<li>The module layer is desigend to control the class loading machanisms (e.G. structureal class loader hierarchies instead of a linear classpath)</li>
<li>Life cycle layer adds a management API (e.G. inform the others about installation event)</li>
<li>Separation of concerns is promoted by definition of services for different tasks.</li>
</ol>
<ul>
<li>Services are used for decoupling of system parts (This is a standard application of service-orientation).</li>
<li>OSGI makes dependencies explicit (private, import, export)</li>
<li>OSGI tries to make the system managable, taking dynamics and lifecycle as fisrst-class citizens</li>
<li>OSGI will be extended to support distribution: the team works on policies, SLAs, etc&#8230;</li>
</ul>
<p>I liked the talk and the way how Peter Kriens addressed the problems of OO in big systems. I was confirmed in some ideas about coupling that will be layed out in my thesis. After the presentation we had a delicious meal and wraped up the evening with interesting discussion about pros and contras of OSGi. 
<a  href="http://www.peterfriese.de/" onclick="javascript:pageTracker._trackPageview('/external/www.peterfriese.de/');" >Peter Friese</a> showed me some 
<a  href="http://r-osgi.sourceforge.net/" onclick="javascript:pageTracker._trackPageview('/external/r-osgi.sourceforge.net/');" >remote OSGi</a> staff, he was playing with. The lack of documentation in this area makes it a little difficult, but I hope he will post some news on it. As usual, you can find other pictures in my 
<a  href="http://www.flickr.com/photos/sza/sets/72157607211061354/" onclick="javascript:pageTracker._trackPageview('/external/www.flickr.com/photos/sza/sets/72157607211061354/');" >FlickR gallery</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://simon.zambrovski.org/2008/09/osgi-why-modularity-is-important/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
