<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="http://www.bytemycode.com/rssformat.xsl"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/">
	<channel>
		<title>byteMyCode: Snippet Revisions</title>
		<link>http://www.bytemycode.com</link>
		<description>Revisions for this snippet.</description>
		<pubDate>Sun, 23 Nov 2008 08:59:10 +0000</pubDate>
		<copyright>1998-2008 </copyright>
		<language>en-us</language>
		<image>
		      <link>http://www.bytemycode.com</link>
		      <url>http://www.bytemycode.com/img/rss_title.gif</url>
		      <title>byteMyCode</title>
		</image>

	
	<item>
		<title>workaround network properties inconsistencies under Java Web Start 1</title>
		<link>http://www.bytemycode.com/snippets/snippet/211/1/</link>
		<comments>http://www.bytemycode.com/snippets/snippet/211/comments/</comments>
		<pubDate>Tue, 16 May 2006 06:26:09 +0000</pubDate>
		<dc:creator>jbuchberger</dc:creator>
		<category>Java</category>
		<guid isPermaLink="false">http://www.bytemycode.com/snippets/snippet/211/</guid>
		<description>
			<![CDATA[
				<p>With Java Web Start 1.5.0 all of a sudden new proxy properties were introduced (deployment.proxy.http.host, deployment.proxy.http.port and deployment.proxy.bypass.list) valid only for the webstart environment - and if that was not enough yet, it does not support the existing proxy properties, neither the standard, nor the deprecated ones from old Java releases. To topple even that, for the bypass-list the delimiters were changed to semicolon (http.nonProxyHosts has the pipe char as delimiter) ... </p>
			]]>
		</description>
	</item>

	
	<item>
		<title>workaround network properties inconsistencies under Java Web Start 2</title>
		<link>http://www.bytemycode.com/snippets/snippet/211/2/</link>
		<comments>http://www.bytemycode.com/snippets/snippet/211/comments/</comments>
		<pubDate>Tue, 16 May 2006 06:29:21 +0000</pubDate>
		<dc:creator>jbuchberger</dc:creator>
		<category>Java</category>
		<guid isPermaLink="false">http://www.bytemycode.com/snippets/snippet/211/</guid>
		<description>
			<![CDATA[
				<p>With Java Web Start 1.5.0 all of a sudden new proxy properties were introduced (deployment.proxy.http.host, deployment.proxy.http.port and deployment.proxy.bypass.list) valid only for the webstart environment - and if that was not enough yet, it does not support the existing proxy properties, neither the standard, nor the deprecated ones from old Java releases. To topple even that, for the bypass-list the delimiters were changed to semicolon (http.nonProxyHosts has the pipe char as delimiter) ... <br /><br /><a href='http://java.sun.com/j2se/1.5.0/docs/guide/net/properties.html' target="_blank">standard networking properties</a></p>
			]]>
		</description>
	</item>

	
	<item>
		<title>workaround network properties inconsistencies under Java Web Start 3</title>
		<link>http://www.bytemycode.com/snippets/snippet/211/3/</link>
		<comments>http://www.bytemycode.com/snippets/snippet/211/comments/</comments>
		<pubDate>Thu, 18 May 2006 02:02:47 +0000</pubDate>
		<dc:creator>jbuchberger</dc:creator>
		<category>Java</category>
		<guid isPermaLink="false">http://www.bytemycode.com/snippets/snippet/211/</guid>
		<description>
			<![CDATA[
				<p>With Java Web Start 1.5.0 all of a sudden new proxy properties were introduced (deployment.proxy.http.host, deployment.proxy.http.port and deployment.proxy.bypass.list) valid only for the webstart environment - and if that was not enough yet, it does not support the existing proxy properties, neither the standard, nor the deprecated ones from old Java releases. To topple even that, for the bypass-list the delimiters were changed to semicolon (http.nonProxyHosts has the pipe char as delimiter) ... <br /><br /><a href='http://java.sun.com/j2se/1.5.0/docs/guide/net/properties.html' target="_blank">standard networking properties</a><br /><br />the workaround here makes sure, that if any one of these proxy properties (deprecated, standard or webstart-5 ones) are set, that all the others get the same settings - this pays off, if you're using different third-party components relying on one specific set of these proxy properties (especially if it's beyond your power, in what kind of environment the software will be executed respectively integrated...)</p>
			]]>
		</description>
	</item>

	
	</channel>
</rss>