<?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: Profile Creation on WebSphere Application Server 6.1.0.19 Fails with Certificate Error</title>
	<atom:link href="http://blog.danzrobok.com/2008/11/04/profile-creation-on-websphere-application-server-61019-fails-with-certificate-error/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.danzrobok.com/2008/11/04/profile-creation-on-websphere-application-server-61019-fails-with-certificate-error/</link>
	<description>Business Integration and SOA with an IBM WebSphere slant</description>
	<lastBuildDate>Fri, 30 Jul 2010 15:35:28 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Follow up to Profile Creation Fails on WebSphere 6.1.0.19: Java Juristiction Policy Files &#124; danzrobok.com</title>
		<link>http://blog.danzrobok.com/2008/11/04/profile-creation-on-websphere-application-server-61019-fails-with-certificate-error/comment-page-1/#comment-3773</link>
		<dc:creator>Follow up to Profile Creation Fails on WebSphere 6.1.0.19: Java Juristiction Policy Files &#124; danzrobok.com</dc:creator>
		<pubDate>Mon, 17 Nov 2008 16:28:58 +0000</pubDate>
		<guid isPermaLink="false">http://blog.danzrobok.com/2008/11/04/profiler-creation-on-websphere-application-server-61019-fails-with-certificate-error/#comment-3773</guid>
		<description>[...] few weeks ago, I discussed an issue where a profile could no longer be created on WebSphere Application Server 6.1.0.19. It boiled down to an issue with the Java security policy files and thier &#8216;restricted&#8217; [...]</description>
		<content:encoded><![CDATA[<p>[...] few weeks ago, I discussed an issue where a profile could no longer be created on WebSphere Application Server 6.1.0.19. It boiled down to an issue with the Java security policy files and thier &#8216;restricted&#8217; [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
