<?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 on: Fix for log4j bug 45704 &#8211; Failed to load logging.xml for JRE 1.5.0_16 and Webstart</title>
	<atom:link href="http://www.objectdefinitions.com/odblog/2008/fix-for-log4j-bug-45704-failed-to-load-loggingxml-for-jre-150_16-and-webstart/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.objectdefinitions.com/odblog/2008/fix-for-log4j-bug-45704-failed-to-load-loggingxml-for-jre-150_16-and-webstart/</link>
	<description>Software Development - random theories, code snippits and opinions</description>
	<lastBuildDate>Tue, 18 Oct 2011 23:30:17 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Nick</title>
		<link>http://www.objectdefinitions.com/odblog/2008/fix-for-log4j-bug-45704-failed-to-load-loggingxml-for-jre-150_16-and-webstart/comment-page-1/#comment-1027</link>
		<dc:creator>Nick</dc:creator>
		<pubDate>Wed, 01 Oct 2008 14:21:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.objectdefinitions.com/odblog/2008/fix-for-log4j-bug-45704-failed-to-load-loggingxml-for-jre-150_16-and-webstart/#comment-1027</guid>
		<description>It has been pointed out that this fix to work around the problem with the URLs for log4j does not work for the case where the log.xml config file contains external ENTITY references relative to the main log.xml. For self-contained config files (the majority) it should work OK. But really, Sun ought to fix the URL issue, at least for signed apps running with all privileges, since this is not just affecting log4j users</description>
		<content:encoded><![CDATA[<p>It has been pointed out that this fix to work around the problem with the URLs for log4j does not work for the case where the log.xml config file contains external ENTITY references relative to the main log.xml. For self-contained config files (the majority) it should work OK. But really, Sun ought to fix the URL issue, at least for signed apps running with all privileges, since this is not just affecting log4j users</p>
]]></content:encoded>
	</item>
</channel>
</rss>

