<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.1" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Adopting OSGi as architectural asset for internal development</title>
	<link>http://www.pierocampanelli.info/articles/2006/11/09/adopting-osgi-as-architectural-asset-for-company-development/</link>
	<description>Software Architect, Passionate Developer, Computer Geek, Internet Addicted, ...</description>
	<pubDate>Sat, 22 Nov 2008 06:29:31 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.1</generator>

	<item>
		<title>By: Behrang</title>
		<link>http://www.pierocampanelli.info/articles/2006/11/09/adopting-osgi-as-architectural-asset-for-company-development/#comment-492</link>
		<author>Behrang</author>
		<pubDate>Wed, 10 Oct 2007 10:08:13 +0000</pubDate>
		<guid>http://www.pierocampanelli.info/articles/2006/11/09/adopting-osgi-as-architectural-asset-for-company-development/#comment-492</guid>
		<description>Comparing EJBs to OSGI is a little bit non sense. OSGI is a general purpose component model. EJBs are components for building enterprise apps. In the same way that we do not build a desktop application on top of EJBs, OSGI, out of the box, does not have the features necessary for building an enterprise app such as transactions, messaging, etc. But if we could have an enterprise stack (we already have a few experimental ones) built around OSGI it would be very great. Then we could compare  that to EJB/J2EE.</description>
		<content:encoded><![CDATA[<p>Comparing EJBs to OSGI is a little bit non sense. OSGI is a general purpose component model. EJBs are components for building enterprise apps. In the same way that we do not build a desktop application on top of EJBs, OSGI, out of the box, does not have the features necessary for building an enterprise app such as transactions, messaging, etc. But if we could have an enterprise stack (we already have a few experimental ones) built around OSGI it would be very great. Then we could compare  that to EJB/J2EE.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
