• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Login application not running error is resourse not found

 
navalk joshi
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
hello everyone........... i am new to java server faces and trying to run the application in jsf 2.0 but its not working.here is my web.xml and faces-config.xml..........kindly tell me where its going wrong......

[
My faces-config.xml is as follows:


 
Tim Holloway
Saloon Keeper
Posts: 18300
56
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
First and foremost, user-designed login/security systems are a very bad idea. I've worked with J2EE since before servlets were invented, seen a lot of different webapps, some of which were very sensitive in nature, and seen a lot of user-defined security systems.

Almost all of them could be hacked into in under 10 minutes by non-sophisticated users. None of them were completely secure.

The J2EE specification includes a container-managed security framework. It works by wrapping itself around the webapp and bouncing many of the invalid requests before they can come anywhere near application code, and if you can't get to the code, you cannot exploit it. This system was designed by full-time professional security experts, not someone who was simply expected to "Git 'R Dun!" while concentrating on the more important business functions. It has withstood the test of time; I've never heard of it being successfully exploited. And best of all, it's pre-written and pre-debugged.

Aside from that, there are 2 problems with your samples.

First, you are using web resource paths as your navigation targets. Navigation targets are not resources (.xhtml), they are URLs (.faces). Specifically, they are relative URLs with no parameters or other decorations and must be JSF URLs, not URLs for generic servlets or JSPs.

Secondly, since they are URLs, you cannot retrieve them from under WEB-INF, because WEB-INF is invisible as a URL target path component in J2EE.
 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic