File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes JSF and the fly likes Issue after upgrading to Tomcat 7 Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Java Interview Guide this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Java » JSF
Bookmark "Issue after upgrading to Tomcat 7" Watch "Issue after upgrading to Tomcat 7" New topic

Issue after upgrading to Tomcat 7

Paolo Pinkel
Ranch Hand

Joined: May 04, 2011
Posts: 35
after upgrading from tomcat 6 to tomcat 7, i get a PropertyNotFoundException that says:

the exception is raised after a button is pressed. it is rendered fine the first time it is invoked. any ideas why? value is a proper property.

it works fine with tomcat 6.

i'm using jsf 2 (myfaces).

thank you!
Rob Shoults

Joined: Nov 06, 2011
Posts: 14
Did you ever get this answered? I am also seeing something like this on Tomcat 7.
Tim Holloway
Saloon Keeper

Joined: Jun 25, 2001
Posts: 17421

Putting a parameter in a value wouldn't have worked at all in JSF version 1, and even in version 2, I don't recommend it. It tends to pollute the core concept of Model/View/Controller by placing logic in the View.

What the message is actually saying is that it's looking for a pair of public accessor methods named "getDoSomething()" and "setDoSomething()" in the class com.someproject.SomeClass and not finding them.

An IDE is no substitute for an Intelligent Developer.
Rob Shoults

Joined: Nov 06, 2011
Posts: 14
That makes sense.

In my case, the error message is similar but my scenrio is a little different. I am not trying to pass parameters.

I am brand new to JSF and using tomcat 7 and JSF 2.1. I am just trying to get a simple login page to work with a managed bean (using annotation). My managed bean (user) has a single property with getter/setter. However, when I reference in it in my NetBeans 7.0 IDE, the page editor says the properity is unknown. And when I drop the app on a Tomcat 7 server and try to access the page, I get an error on the JSF error page stating "property not found on type user". The user is instantiated in the session according to the JSF error page.

I saw this post and thought maybe it was a Tomcat 7 issue but it seems like such basic functionality, i would be surprised if it was.

I think I will have to post a new topic on the issue so someone can help me troubleshoot my configuration. Thanks for the reply.

I agree. Here's the link:
subject: Issue after upgrading to Tomcat 7
It's not a secret anymore!