<?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>Jakub Korab &#187; jsr-277</title>
	<atom:link href="http://www.jakubkorab.net/category/technology/jsr-277/feed" rel="self" type="application/rss+xml" />
	<link>http://www.jakubkorab.net</link>
	<description>Adventures in technology consulting</description>
	<lastBuildDate>Wed, 11 Jan 2012 23:59:16 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>OSGi vs. JSR-277</title>
		<link>http://www.jakubkorab.net/2007/02/osgi-vs-jsr-277.html?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=osgi-vs-jsr-277</link>
		<comments>http://www.jakubkorab.net/2007/02/osgi-vs-jsr-277.html#comments</comments>
		<pubDate>Tue, 06 Feb 2007 13:27:00 +0000</pubDate>
		<dc:creator>Jake</dc:creator>
				<category><![CDATA[java]]></category>
		<category><![CDATA[jsr-277]]></category>
		<category><![CDATA[osgi]]></category>

		<guid isPermaLink="false">http://www.jakubkorab.net/2007/02/osgi-vs-jsr-277</guid>
		<description><![CDATA[<p>I checked out the OSGi presentation from the Parleys site http://www.bejug.org/confluenceBeJUG/display/PARLEYS/Spring+OSGi. Wow. I haven&#8217;t really spent any time thinking about this stuff in the past, but it seems that yet again the JSR process is trying to formalize something that doesn&#8217;t need it. OSGi seems to be a much lighter, more powerful model whereby you can switch bundles, the JSR-277 module equivalents, at runtime via an OSGi console or JMX. Check out http://www.osgi.org and http://en.wikipedia.org/wiki/OSGi for good synopses of the ...read more]]></description>
			<content:encoded><![CDATA[<p><font SIZE=2 FACE="Arial">I checked out the OSGi presentation from the Parleys site </font><a HREF="http://www.bejug.org/confluenceBeJUG/display/PARLEYS/Spring+OSGi"><u><font COLOR="#0000FF" SIZE=2 FACE="Arial">http://www.bejug.org/confluenceBeJUG/display/PARLEYS/Spring+OSGi</font></u></a><font SIZE=2 FACE="Arial">. Wow. I haven&#8217;t really spent any time thinking about this stuff in the past, but it seems that yet again the JSR process is trying to formalize something that doesn&#8217;t need it. OSGi seems to be a much lighter, more powerful model whereby you can switch bundles, the JSR-277 module equivalents, at runtime via an OSGi console or JMX. Check out </font><a HREF="http://www.osgi.org"><u><font COLOR="#0000FF" SIZE=2 FACE="Arial">http://www.osgi.org</font></u></a><font SIZE=2 FACE="Arial"> and </font><a HREF="http://en.wikipedia.org/wiki/OSGi"><u><font COLOR="#0000FF" SIZE=2 FACE="Arial">http://en.wikipedia.org/wiki/OSGi</font></u></a><font SIZE=2 FACE="Arial"> for good synopses of the technology and what it can offer.</font></p>
<p><font SIZE=2 FACE="Arial">The huge advantage here is that the technology is stable, mature and available to use right now (there are a number of open-source implementations) rather than needing to wait for something that won&#8217;t be around until Java 7. All that and no new language structures. </font></p>
<p><font SIZE=2 FACE="Arial">There&#8217;s an interesting post by Peter Kriens from OSGi about how JSR-277 stacks up at</font> <br /><a HREF="http://www.osgi.org/blog/2006/10/jsr-277-review.html"><u><font COLOR="#0000FF" SIZE=2 FACE="Arial">http://www.osgi.org/blog/2006/10/jsr-277-review.html</font></u></a> </p>
<p><font SIZE=2 FACE="Arial">&quot;The ambition level of JSR 277 is significantly lower than where the OSGi specifications are today, even way lower than we set out in 1998. In a way, for me the JSR 277 proposal feels rather<i> toyish</i>. &quot;</font></p>
<p><font SIZE=2 FACE="Arial">It&#8217;s time to kick the tires on this one, and see where it might be useful.</font> </p>
]]></content:encoded>
			<wfw:commentRss>http://www.jakubkorab.net/2007/02/osgi-vs-jsr-277.html/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>An end to classloader nightmares</title>
		<link>http://www.jakubkorab.net/2007/02/an-end-to-classloader-nightmares.html?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=an-end-to-classloader-nightmares</link>
		<comments>http://www.jakubkorab.net/2007/02/an-end-to-classloader-nightmares.html#comments</comments>
		<pubDate>Fri, 02 Feb 2007 17:34:00 +0000</pubDate>
		<dc:creator>Jake</dc:creator>
				<category><![CDATA[java]]></category>
		<category><![CDATA[jsr-277]]></category>

		<guid isPermaLink="false">http://www.jakubkorab.net/2007/02/an-end-to-classloader-nightmares</guid>
		<description><![CDATA[<p>I have been going through some of the presentations from the Javapolis 2006 conference, and I stumbled upon a talk by Stanley Ho from Sun Microsystems about JSR-277 Java Modules &#8211; http://www.bejug.org/confluenceBeJUG/display/PARLEYS/JSR-277+Java+Module+System. The spec finally provides Java programmers the ability to programmatically enforce version dependencies within their code. No more classpath hell!! Woohoo! Once you have tried to work out which one of the 1000 xerces.jar files the classloader is loading a few times, it tends to lose its novelty. ...read more]]></description>
			<content:encoded><![CDATA[<p><span style=";font-family:Arial;font-size:100%;"  >I have been going through some of the presentations from the Javapolis 2006 conference, and I stumbled upon a talk by Stanley Ho from Sun Microsystems about JSR-277 Java Modules &#8211; </span><span style="font-size:100%;"><a href="http://www.bejug.org/confluenceBeJUG/display/PARLEYS/JSR-277+Java+Module+System"><u><span style="color: rgb(0, 0, 255);font-family:Arial;" >http://www.bejug.org/confluenceBeJUG/display/PARLEYS/JSR-277+Java+Module+System</span></u></a></span><span style=";font-family:Arial;font-size:100%;"  >. The spec finally provides Java programmers the ability to programmatically enforce version dependencies within their code. No more classpath hell!! Woohoo! Once you have tried to work out which one of the 1000 xerces.jar files the classloader is loading a few times, it tends to lose its novelty. </span></p>
<p><span style=";font-family:Arial;font-size:100%;"  >One of the really cool things about it is the ability to instruct the classloader to load different versions of the same library (or module as it is now referred to) programmatically at runtime &#8211; loading different versions when you need them! Very powerful. Can&#8217;t wait to see an implementation.<br /></span></p>
<p><span style=";font-family:Arial;font-size:85%;"  ><span style="font-size:100%;">It&#8217;s about time too&#8230;</span><br /></span></p>
<p></p>
]]></content:encoded>
			<wfw:commentRss>http://www.jakubkorab.net/2007/02/an-end-to-classloader-nightmares.html/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

