posted 13 years ago
Unfortunately, there's no diagnostic information available. Sometimes you'll get a "property x not defined on bean y" type of message, but that's usually in cases where lack of a value is fatal. Otherwise, when data just simply fails to show, do the following checklist:
1. Make sure that the bean itself is defined and cataloged as a managed bean and that you have capitalized everything properly. The class name for the bean should begin with an uppercase letter and the actual bean reference (instance name) should begin with a lower-case letter. The @ManagedBean annotation will automatically take care of that, if that's what you are using.
2. Make sure that there's a public "getXxxx" method defined for the referenced property name "xxxx" and that it doesn't return void. Depending on the usage, it may be necessary to also define a public void "setXxxx" method as well.
3. Make sure that "getXxxx" actually is returning a non-blank value if you want a value to display!
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.