<?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>BasePatterns.org &#187; osgi</title>
	<atom:link href="http://basepatterns.org/tag/osgi/feed/" rel="self" type="application/rss+xml" />
	<link>http://basepatterns.org</link>
	<description>Trends in software design</description>
	<lastBuildDate>Thu, 05 Apr 2012 00:13:31 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Bootstrapping an OSGi environment</title>
		<link>http://basepatterns.org/2012/02/bootstrapping-an-osgi-environment/</link>
		<comments>http://basepatterns.org/2012/02/bootstrapping-an-osgi-environment/#comments</comments>
		<pubDate>Thu, 16 Feb 2012 23:26:54 +0000</pubDate>
		<dc:creator>fortuna</dc:creator>
				<category><![CDATA[Build]]></category>
		<category><![CDATA[groovy]]></category>
		<category><![CDATA[osgi]]></category>
		<category><![CDATA[patterns]]></category>

		<guid isPermaLink="false">http://basepatterns.org/?p=149</guid>
		<description><![CDATA[Something I have always lamented about OSGi is a lack of simple examples to get up and running quickly. So here is a simple example using Groovy: First, dependencies are easily added via Maven, adding the following to your pom.xml should do it. Then a simple Groovy script to start the OSGi framework and print [...]]]></description>
		<wfw:commentRss>http://basepatterns.org/2012/02/bootstrapping-an-osgi-environment/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Whiteboard Registry</title>
		<link>http://basepatterns.org/2009/10/whiteboard-registry/</link>
		<comments>http://basepatterns.org/2009/10/whiteboard-registry/#comments</comments>
		<pubDate>Thu, 08 Oct 2009 06:59:44 +0000</pubDate>
		<dc:creator>fortuna</dc:creator>
				<category><![CDATA[Java]]></category>
		<category><![CDATA[osgi]]></category>
		<category><![CDATA[patterns]]></category>
		<category><![CDATA[registry]]></category>
		<category><![CDATA[whiteboard]]></category>

		<guid isPermaLink="false">http://basepatterns.org/?p=86</guid>
		<description><![CDATA[In OSGi using a publisher/subscriber design can be somewhat more complicated that traditional Java environments: To overcome these hurdles the Whiteboard Pattern prescribes registering listeners in the service registry as opposed to services, whereby services can publish events to available listeners at the time of the event. The problem with the Whiteboard Pattern is that [...]]]></description>
		<wfw:commentRss>http://basepatterns.org/2009/10/whiteboard-registry/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>OSGi Service Locator</title>
		<link>http://basepatterns.org/2009/09/osgi-service-locator/</link>
		<comments>http://basepatterns.org/2009/09/osgi-service-locator/#comments</comments>
		<pubDate>Wed, 30 Sep 2009 01:27:10 +0000</pubDate>
		<dc:creator>fortuna</dc:creator>
				<category><![CDATA[Java]]></category>
		<category><![CDATA[osgi]]></category>
		<category><![CDATA[patterns]]></category>
		<category><![CDATA[service locator]]></category>

		<guid isPermaLink="false">http://basepatterns.org/?p=74</guid>
		<description><![CDATA[The Service Locator pattern is a well-established mechanism for accessing local and remote services in a consistent manner: Using a structured service name interface we can improve uniformity and reduce the potential for typos: In an OSGi environment, the recommended approach for retrieving services is via the org.osgi.util.tracker.ServiceTracker class: We can combine these two patterns [...]]]></description>
		<wfw:commentRss>http://basepatterns.org/2009/09/osgi-service-locator/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

