<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments for Jeff Sinclair's Website</title>
	<atom:link href="http://www.cooljeff.co.uk/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.cooljeff.co.uk</link>
	<description>my 2 pence to the world</description>
	<lastBuildDate>Sun, 13 Dec 2009 13:02:13 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Custom URL protocols and multiple classloaders by admin</title>
		<link>http://www.cooljeff.co.uk/2009/12/12/custom-url-protocols-and-multiple-classloaders/comment-page-1/#comment-128</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Sun, 13 Dec 2009 13:02:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.cooljeff.co.uk/?p=172#comment-128</guid>
		<description>Stuart, thanks for this, I was not fully aware of how OSGI works around the various issues and Chapter 11 does a good job at explaining it.</description>
		<content:encoded><![CDATA[<p>Stuart, thanks for this, I was not fully aware of how OSGI works around the various issues and Chapter 11 does a good job at explaining it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Custom URL protocols and multiple classloaders by Stuart McCulloch</title>
		<link>http://www.cooljeff.co.uk/2009/12/12/custom-url-protocols-and-multiple-classloaders/comment-page-1/#comment-127</link>
		<dc:creator>Stuart McCulloch</dc:creator>
		<pubDate>Sun, 13 Dec 2009 02:13:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.cooljeff.co.uk/?p=172#comment-127</guid>
		<description>You might want to look at the URL Handlers Service (chapter 11 of the OSGi core specification http://www.osgi.org/download/r4v42/r4.core.pdf)

It defines a service-based approach for registering URL handlers in a modular, dynamic application. The basic idea is that you can register an implementation of URLStreamHandlerService with the OSGi service registry - the various service implementations are then discovered by the real (singleton) URLStreamHandler that&#039;s registered by the OSGi framework. The framework handler is responsible for sending incoming requests to the right handler service.

You can find a concrete example over at http://wiki.ops4j.org/display/paxurl/Pax+URL which also works in a standard Java environment, except without the dynamic part.

Of course, there are some wrinkles (mostly when embedding frameworks inside other containers) but most OSGi frameworks can also support this by using reflection to chain to existing handler factories.</description>
		<content:encoded><![CDATA[<p>You might want to look at the URL Handlers Service (chapter 11 of the OSGi core specification <a href="http://www.osgi.org/download/r4v42/r4.core.pdf)" rel="nofollow">http://www.osgi.org/download/r4v42/r4.core.pdf)</a></p>
<p>It defines a service-based approach for registering URL handlers in a modular, dynamic application. The basic idea is that you can register an implementation of URLStreamHandlerService with the OSGi service registry &#8211; the various service implementations are then discovered by the real (singleton) URLStreamHandler that&#8217;s registered by the OSGi framework. The framework handler is responsible for sending incoming requests to the right handler service.</p>
<p>You can find a concrete example over at <a href="http://wiki.ops4j.org/display/paxurl/Pax+URL" rel="nofollow">http://wiki.ops4j.org/display/paxurl/Pax+URL</a> which also works in a standard Java environment, except without the dynamic part.</p>
<p>Of course, there are some wrinkles (mostly when embedding frameworks inside other containers) but most OSGi frameworks can also support this by using reflection to chain to existing handler factories.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Handling native dependencies with Apache Ivy by admin</title>
		<link>http://www.cooljeff.co.uk/2009/08/01/handling-native-dependencies-with-apache-ivy/comment-page-1/#comment-123</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Wed, 09 Sep 2009 20:14:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.cooljeff.co.uk/?p=129#comment-123</guid>
		<description>Thanks Andrei. I need to update this blog entry based on the feedback I got from the IvyDE mailing lists however I&#039;m most of the way through implementing:

&lt;ul&gt;
	&lt;li&gt;A type filter in IvyDE for JNI.&lt;/li&gt;
	&lt;li&gt;Populating the -Djava.library.path automatically from resolved artifacts in the type filter.&lt;/li&gt;
&lt;/ul&gt;

I&#039;ve been quite busy at work, however I hope to have something working over the weekend. I&#039;ll then feed this back to IvyDE and will ping you when I have something for you to try.

Jeff</description>
		<content:encoded><![CDATA[<p>Thanks Andrei. I need to update this blog entry based on the feedback I got from the IvyDE mailing lists however I&#8217;m most of the way through implementing:</p>
<ul>
<li>A type filter in IvyDE for JNI.</li>
<li>Populating the -Djava.library.path automatically from resolved artifacts in the type filter.</li>
</ul>
<p>I&#8217;ve been quite busy at work, however I hope to have something working over the weekend. I&#8217;ll then feed this back to IvyDE and will ping you when I have something for you to try.</p>
<p>Jeff</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Handling native dependencies with Apache Ivy by Andrei</title>
		<link>http://www.cooljeff.co.uk/2009/08/01/handling-native-dependencies-with-apache-ivy/comment-page-1/#comment-122</link>
		<dc:creator>Andrei</dc:creator>
		<pubDate>Wed, 09 Sep 2009 17:54:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.cooljeff.co.uk/?p=129#comment-122</guid>
		<description>Hi Jeff,

  Do you have a working prototype of your suggestion?  I&#039;ve read through your other thoughts on the Apache site and I think you&#039;ve got some wonderful ideas. 

 In general, the lack of this functionality is a major problem with the IvyDE implementation and may be a showstopper for us, unless a comprehensive solution is available.

 Any feedback would be greatly appreciated.

thanks
andrei</description>
		<content:encoded><![CDATA[<p>Hi Jeff,</p>
<p>  Do you have a working prototype of your suggestion?  I&#8217;ve read through your other thoughts on the Apache site and I think you&#8217;ve got some wonderful ideas. </p>
<p> In general, the lack of this functionality is a major problem with the IvyDE implementation and may be a showstopper for us, unless a comprehensive solution is available.</p>
<p> Any feedback would be greatly appreciated.</p>
<p>thanks<br />
andrei</p>
]]></content:encoded>
	</item>
</channel>
</rss>
