Applies to:
NA
Description:
A common problem which occurs when the class loader cannot find beans that the pages reference.That usually results in an error message like “Class xxx cannot be resolved to a type”
Cause:
The class loader could not find beans that the pages referenced.
JAVA-JSP alfresco javabean approvestepname not found, autistic disorders, bean not found error, bean not found in, bean not found in java, bridge bean not found error, error, error 'no java bean found', error java bean was not found, error stating that a java bean was not found, error stating that a javabean was not found, errornojava.jsp, filebean not recognized in java bean, find, getdbtransaction not found in ui java bean, heart transplant, j, jasperstudio javabean, jasperstudio javabeans class not found, java, java bean not detected in war, java bean not found, java bean not found error, java bean not seen, java bean was not found, java bean was not found error, java beans not found, java beans not seen in ie8, java error no java bean found, java no java bean found, java.beans.propertydescriptor not found, java: not found in jms distribution bean, javabean cannot be resolved error message, javabean not found, javabean not found error, javabean was not found, javabean was not found error, javebean not found, jboss jmx console "bean not found", lrm-00118: syntax error at '=' at the end of input, no java bean found, no java bean found error, no java bean found in java, no java bean found java, no javabean found, no javabean properties found, no javabean properties found in, not found, package not found error in javabean, results in an error stating that a javabean was not found, what is no java bean found, what results in an error stating that a javabean was not found?, when java bean was not found error comes, which error stating that a javabean was not found?, which one of the following results in an error stating that a java bean was not found?, which one of the results in an error stating that javabean was not found
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 ‘public’ 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.