<?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>The ramblings of a yorkshire tyke &#187; Java</title>
	<atom:link href="http://www.gennard.net/blog/tag/java/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gennard.net/blog</link>
	<description>Life, Rants and Programming In A Blog</description>
	<lastBuildDate>Mon, 31 Oct 2011 23:32:30 +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>Metro up Java</title>
		<link>http://www.gennard.net/blog/2011/09/metro-up-java/</link>
		<comments>http://www.gennard.net/blog/2011/09/metro-up-java/#comments</comments>
		<pubDate>Fri, 23 Sep 2011 22:54:54 +0000</pubDate>
		<dc:creator>spgennard</dc:creator>
				<category><![CDATA[Java]]></category>
		<category><![CDATA[Metro]]></category>
		<category><![CDATA[Windows8]]></category>
		<category><![CDATA[AppStore]]></category>
		<category><![CDATA[Assembly.Load]]></category>
		<category><![CDATA[JVM]]></category>
		<category><![CDATA[LoadLibrary]]></category>
		<category><![CDATA[Perl]]></category>
		<category><![CDATA[Windows 8]]></category>

		<guid isPermaLink="false">http://www.gennard.net/blog/?p=809</guid>
		<description><![CDATA[<a href="http://www.gennard.net/blog/2011/09/metro-up-java/" title="Metro up Java"></a>Microsoft&#8217;s Metro environment is a bit of a closed environment for the Open Source language vendor, so although you can code Metro applications in C/C++, C#, HTML/JavaScript/CSS on both Intel and ARM chipsets the choice of other languages are non-existent. &#8230;<p class="read-more"><a href="http://www.gennard.net/blog/2011/09/metro-up-java/">Read more &#187;</a></p>]]></description>
		<wfw:commentRss>http://www.gennard.net/blog/2011/09/metro-up-java/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Using sun.jvmstat.monitor to see active Java processes</title>
		<link>http://www.gennard.net/blog/2009/12/using-sun-jvmstat-monitor-to-see-active-java-processes/</link>
		<comments>http://www.gennard.net/blog/2009/12/using-sun-jvmstat-monitor-to-see-active-java-processes/#comments</comments>
		<pubDate>Sat, 05 Dec 2009 10:56:38 +0000</pubDate>
		<dc:creator>spgennard</dc:creator>
				<category><![CDATA[Java]]></category>
		<category><![CDATA[JVM]]></category>
		<category><![CDATA[jvmstat]]></category>
		<category><![CDATA[monitor]]></category>

		<guid isPermaLink="false">http://www.gennard.net/blog/?p=335</guid>
		<description><![CDATA[<a href="http://www.gennard.net/blog/2009/12/using-sun-jvmstat-monitor-to-see-active-java-processes/" title="Using sun.jvmstat.monitor to see active Java processes"></a>Monitor&#8217;ing Java processes can be achieved using the jvmstat monitor classes provided in the JVM. The documentation is a bit sketchy but with a little experimenting it can be done. Below is a little example that shows you how to &#8230;<p class="read-more"><a href="http://www.gennard.net/blog/2009/12/using-sun-jvmstat-monitor-to-see-active-java-processes/">Read more &#187;</a></p>]]></description>
		<wfw:commentRss>http://www.gennard.net/blog/2009/12/using-sun-jvmstat-monitor-to-see-active-java-processes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Java process id via java.lang.management</title>
		<link>http://www.gennard.net/blog/2009/12/java-process-id-via-java-lang-management/</link>
		<comments>http://www.gennard.net/blog/2009/12/java-process-id-via-java-lang-management/#comments</comments>
		<pubDate>Fri, 04 Dec 2009 23:53:13 +0000</pubDate>
		<dc:creator>spgennard</dc:creator>
				<category><![CDATA[Java]]></category>
		<category><![CDATA[JVM]]></category>
		<category><![CDATA[Tips]]></category>
		<category><![CDATA[getpid]]></category>

		<guid isPermaLink="false">http://www.gennard.net/blog/?p=329</guid>
		<description><![CDATA[<a href="http://www.gennard.net/blog/2009/12/java-process-id-via-java-lang-management/" title="Java process id via java.lang.management"></a>While working on a project recently I need to find out the current process of the active running Java process (for tracing/auditing), however I never found a 100% perfect solution but did come across an acceptable solution to use the &#8230;<p class="read-more"><a href="http://www.gennard.net/blog/2009/12/java-process-id-via-java-lang-management/">Read more &#187;</a></p>]]></description>
		<wfw:commentRss>http://www.gennard.net/blog/2009/12/java-process-id-via-java-lang-management/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Fiddling with the JVM</title>
		<link>http://www.gennard.net/blog/2009/11/unsafe-java-for-the-wierd/</link>
		<comments>http://www.gennard.net/blog/2009/11/unsafe-java-for-the-wierd/#comments</comments>
		<pubDate>Mon, 09 Nov 2009 20:10:49 +0000</pubDate>
		<dc:creator>spgennard</dc:creator>
				<category><![CDATA[Java]]></category>
		<category><![CDATA[JVM]]></category>
		<category><![CDATA[Tips]]></category>
		<category><![CDATA[sun.misc.Unsafe]]></category>
		<category><![CDATA[unsafe]]></category>

		<guid isPermaLink="false">http://www.gennard.net/blog/?p=25</guid>
		<description><![CDATA[<a href="http://www.gennard.net/blog/2009/11/unsafe-java-for-the-wierd/" title="Fiddling with the JVM"></a>Java is a very safe language if used in a normal way, however just like the CLR it can be used in an unsafe manor. The main reason for using Java in a unsafe manor is performance, some unsafe operations &#8230;<p class="read-more"><a href="http://www.gennard.net/blog/2009/11/unsafe-java-for-the-wierd/">Read more &#187;</a></p>]]></description>
		<wfw:commentRss>http://www.gennard.net/blog/2009/11/unsafe-java-for-the-wierd/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Object COBOL/Java default exception handler</title>
		<link>http://www.gennard.net/blog/2009/11/object-coboljava-default-exception-handler/</link>
		<comments>http://www.gennard.net/blog/2009/11/object-coboljava-default-exception-handler/#comments</comments>
		<pubDate>Tue, 03 Nov 2009 22:16:54 +0000</pubDate>
		<dc:creator>spgennard</dc:creator>
				<category><![CDATA[COBOL]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[Tips]]></category>
		<category><![CDATA[Interop]]></category>

		<guid isPermaLink="false">http://www.gennard.net/blog/?p=49</guid>
		<description><![CDATA[<a href="http://www.gennard.net/blog/2009/11/object-coboljava-default-exception-handler/" title="Object COBOL/Java default exception handler"></a>While working on some support recently for our compiler (Micro Focus COBOL compiler that is), I became annoyed with the lack of a reasonable error messages/stack trace output from our Java/COBOL Object support. I have no idea why our default &#8230;<p class="read-more"><a href="http://www.gennard.net/blog/2009/11/object-coboljava-default-exception-handler/">Read more &#187;</a></p>]]></description>
		<wfw:commentRss>http://www.gennard.net/blog/2009/11/object-coboljava-default-exception-handler/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

