The bean properties and code portions are down at the end of the message. Now, I know the server has the backing bean. I put a System.out.println statement in the constructor to prove it. When I point my browser to the .jsf page, I can see my output from the constructor of the backing bean on my Tomcat console spew. That tells me it has the bean.
The getAllAgents method is the first method on the .jsp. And yes, I've deleted the application directory and .war file from Tomcat each time I deployed this bugger, which is numbering close to a million.
Other, simpler pages display okay. This one is a little more challenging in that it deals with Lists.
And, most importantly, the offending method in the backing bean. In it's current state you can see where I've hacked at it to try to solve the problem. The System.out.println statements below DO NOT appear in the console. It blows up before it gets to that part.:
Thank you in advance! [ April 18, 2006: Message edited by: Charles McGuire ]
Charles - I've run into what seems to be a similar problem. I can see that backing bean is instantiated, but I get an error accessing it with an expression. Did you ever get anywhere with resolving this?