<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Weblogic &#8216;feature&#8217; and Bb Vista SP3</title>
	<atom:link href="http://lauragekeler.com/2009/10/05/weblogic-feature-and-bb-vista-sp3/feed/" rel="self" type="application/rss+xml" />
	<link>http://lauragekeler.com/2009/10/05/weblogic-feature-and-bb-vista-sp3/</link>
	<description>Learning With You</description>
	<lastBuildDate>Sat, 11 Feb 2012 00:35:42 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: LG</title>
		<link>http://lauragekeler.com/2009/10/05/weblogic-feature-and-bb-vista-sp3/#comment-8</link>
		<dc:creator><![CDATA[LG]]></dc:creator>
		<pubDate>Mon, 05 Oct 2009 12:37:20 +0000</pubDate>
		<guid isPermaLink="false">http://lauragekeler.wordpress.com/2009/10/05/weblogic-feature-and-bb-vista-sp3/#comment-8</guid>
		<description><![CDATA[I started the cluster with the schema validation disabled, then went into the weblogic console and toggled hostname verification to NONE, saved, activated, then toggled it back to BEA Hostname verification, the default. Then removed the line which disabled schema validation from my webct.sh STARTUP_OPTIONS, then was able to start the cluster normally. Yes, the config.xml file still contains a param under SSL for the hostname verification setting. Yes, I&#039;m still using the old domain header with URLs pointing to the xsd files...
]]></description>
		<content:encoded><![CDATA[<p>I started the cluster with the schema validation disabled, then went into the weblogic console and toggled hostname verification to NONE, saved, activated, then toggled it back to BEA Hostname verification, the default. Then removed the line which disabled schema validation from my webct.sh STARTUP_OPTIONS, then was able to start the cluster normally. Yes, the config.xml file still contains a param under SSL for the hostname verification setting. Yes, I&#8217;m still using the old domain header with URLs pointing to the xsd files&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

