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.
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.