<?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: Java Bean not found</title>
	<atom:link href="http://iderror.com/errors/java/java-jsp/java-bean-not-found/feed/" rel="self" type="application/rss+xml" />
	<link>http://iderror.com/errors/java/java-jsp/java-bean-not-found/</link>
	<description>You have errors, we have solutions!</description>
	<lastBuildDate>Thu, 07 May 2009 00:45:49 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: admin</title>
		<link>http://iderror.com/errors/java/java-jsp/java-bean-not-found/comment-page-1/#comment-7956</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Fri, 20 Mar 2009 10:28:59 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/idError/?p=8028#comment-7956</guid>
		<description>Here are a few things to check:
   1. Make sure that your beans are compiled properly and that the resulting class file is resident in the hierarchy rooted at the WEB-INF/classes folder.
   2. Be sure that WEB-INF is spelled just that way -- case counts! web-inf, Web-Inf, or any other casing variation will not work.
   3. Always place your bean classes in a package other than the unnamed default package.
   4. Be sure that the fully-qualified class name (including the package) is included in your useBean declaration.
   5. Make sure your class contains the &#039;public&#039; modifier.
   6. If all else fails, carefully check the spelling. Typos in class names and packages are easier to make (and harder to find) than you would think.
</description>
		<content:encoded><![CDATA[<p>Here are a few things to check:<br />
   1. Make sure that your beans are compiled properly and that the resulting class file is resident in the hierarchy rooted at the WEB-INF/classes folder.<br />
   2. Be sure that WEB-INF is spelled just that way &#8212; case counts! web-inf, Web-Inf, or any other casing variation will not work.<br />
   3. Always place your bean classes in a package other than the unnamed default package.<br />
   4. Be sure that the fully-qualified class name (including the package) is included in your useBean declaration.<br />
   5. Make sure your class contains the &#8216;public&#8217; modifier.<br />
   6. If all else fails, carefully check the spelling. Typos in class names and packages are easier to make (and harder to find) than you would think.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
