wood burning stoves 2.0*
The moose likes JSF and the fly likes javax.el.PropertyNotFoundException Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Java » JSF
Bookmark "javax.el.PropertyNotFoundException" Watch "javax.el.PropertyNotFoundException" New topic
Author

javax.el.PropertyNotFoundException

Gynnad Paullussen
Ranch Hand

Joined: Jan 26, 2011
Posts: 49
HI,

I made a template in the Web Pages/WEB-INF/templates/default.xhtml and that template had one <ui:insert name="content"> and also some links that will be active with the controllerBean. But when I click on the commandLink (for example: <h:commandLink value="Facturen" action="#{controllerBean.facturen}" styleClass="facturen"/>) I get this:


Stack Trace


controllerBean


default.xhtml


What did I wrong?
amit punekar
Ranch Hand

Joined: May 14, 2004
Posts: 511
Hello,
I havent worked much with JSF but these are the questions that would help you resolve the issue.
1) Where is the mapping for "controllerBean" that is used in your code.
2) Also make sure to check if package "Beans" also specified as your "controllerBean" is inside the package "Beans".

Regards,
amit
Gynnad Paullussen
Ranch Hand

Joined: Jan 26, 2011
Posts: 49
amit punekar wrote:Hello,
I havent worked much with JSF but these are the questions that would help you resolve the issue.
1) Where is the mapping for "controllerBean" that is used in your code.
2) Also make sure to check if package "Beans" also specified as your "controllerBean" is inside the package "Beans".

Regards,
amit


The first one I doesn't understand, but my controllerBean is in the package bean.
Tim Holloway
Saloon Keeper

Joined: Jun 25, 2001
Posts: 15962
    
  19

You have violated the Java Standard Naming convention by starting a class name with a lower-case character. The default mechanism used by JSF's annotation processor mandates that the classname must follow the standard, which means that the class name must be "ControllerBean", not "controllerBean". JSF will then instantiate the bean and catalog it under the object name "controllerBean" (starting with lower-case, as is the standard for class instances).

Incidentally, in the MVC paradigm, backing beans are NOT controllers. They are Models, although they may be lightly decorated with controller assists such as listeners. The actual Controller part of JSF is primarily located in the FacesServlet and the various tag implementations, and relatively little user-written Controller code is required.


Customer surveys are for companies who didn't pay proper attention to begin with.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: javax.el.PropertyNotFoundException
 
Similar Threads
Method not found
Fields doesn't set the properties
JEE example with EJB, JSF is not working
how use a <li>with <h:commandLink> ?
Again javax.el.PropertyNotFoundException