Turns out the issue was because these methods in my bean didn't have a setXX() version. Yeah, 'weird' is the word that comes to mind with some of my experiences so far :) -john
________________________________ From: Jeff Bischoff [mailto:[EMAIL PROTECTED] Sent: Fri 6/9/2006 2:14 PM To: MyFaces Discussion Subject: Re: weirdness in tomcat 5.5.16 and my-faces John, If you feel like you are getting stuck with stale files, why not shut down tomcat, delete the "temp" and "work" folders, and then start it back up with your latest .war? Regards, Jeff Bischoff Kenneth L Kurz & Assoc, Inc. P.S. do you start every question with the word "weird"? ;) John Mani wrote: > In my JSF page, I attempt to display certain values from my > backing bean as follows: > <h:inputText value="{backer.selectionFirstName}" id = "s1"/> > > where backer is defined as a session scoped bean. Originally > the method getSelectionFirstName() was not there, it was added > later. > > In my tomcat installation, I removed the original .war file > and corresponding directory from webapps, then copy over the > new .war file with the updated class that has this method. > > However, when I access the page, I see errors in the tomcat logfile > of the form: > javax.faces.el.PropertyNotFoundException: Bean: my.BackingBean, property: > selectionFirstName > > I double-check the class in tomcat's webapp/classes directory by using > javap on that class - I can see that method. > > I've restarted tomcat multiple times, redeployed the .war file, but > this weird issue persists. > > As an aside, when I first access the page, I see a 'session ID' appended > to the URL, but not on subsequent clicks and redraws of the page. My > browser settings support cookies, so why is URL rewriting being used? > > Any thoughts ? > thanx > -john
<<winmail.dat>>
