This week's book giveaway is in the Java in General forum.
We're giving away four copies of Think Java: How to Think Like a Computer Scientist and have Allen B. Downey & Chris Mayfield on-line!
See this thread for details.
Win a copy of Think Java: How to Think Like a Computer Scientist this week in the Java in General forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

first JSF page...

 
ankur rathi
Ranch Hand
Posts: 3830
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
With the following files:



Now, here, we can't directly access JSP page(http://localhost:8081/JSFLogin/pages/test.jsp), if we do that then an exception is thrown. Because FacesServlet should be initialized (called) before we access any tag of JSF. So for accessing this JSP page we will have to go through the FacesServlet...

So as per mapping in web.xml, we will access it with faces extension (http://localhost:8081/JSFLogin/pages/test.faces), it will call FacesServlet and that will display our test.jsp.

Now, my confusion is, why we need faces-config.xml in this example??? (we are not providing any navigation rule, managed bean etc).

Please guide...

And also, all my assumptions are right or not??

Thanks a lot.
 
ankur rathi
Ranch Hand
Posts: 3830
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I think, I understood it.

Actually, whether we are using faces-config.xml in this example or not, FacesServlet class try to find this file, loads the content of this file into some object, initialize any bean if present etc. So if we don't provide faces-config.xml the FacesServlet doesn't let us to go ahead...

 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic