>> Does going to the root, i.e. http://hostname:port/, yield a non 404
>> page?
>
> This yields the "Java Web Services Developer Pack 1.5" page.
> >> >> [snip configuration info]
> >> >> > when I try to open http://hostname:port/app/faces/jsp/index.jsp
[quoted text clipped - 13 lines]
>
> - Oliver
Hi,
So I tried this suggestion, and what happened with each progression is
that my browser would just hang for a very long time.
Anyways, I made a couple of changes before trying to call index.jsp
again:
I copied a faces-config.xml file (one I know works) over the existing
one and made the necessary modifications.
Also, I found out I had some phantom tomcat processes going on, which I
had killed.
I'm not sure if one, the other or both changes solved the problem.
The most frustrating part of this ordeal was the vague error message of
"Requested resource not available", along with the fact that I could
not find any remotely similar situation by googling or searching Sun's
forums (but that's not anyone else's fault but my own :P ).
If anyone out there has any "default" debugging tips for when
confronted with this error message (I mean, when you see "requested
resource not available", you know to try to look in a certain set of
areas to alleviate the problem), I would greatly appreciate it.
Finally, thanks Oliver for all your help. I am really grateful.
C.
Oliver Wong - 07 Sep 2006 17:01 GMT
> The most frustrating part of this ordeal was the vague error message of
> "Requested resource not available", along with the fact that I could
[quoted text clipped - 5 lines]
> resource not available", you know to try to look in a certain set of
> areas to alleviate the problem), I would greatly appreciate it.
I don't think it would have solved your specific problem, but it might
be worthwhile to take a look at, and eventually memorize, some of the HTTP
status codes, as they're standardized:
http://en.wikipedia.org/wiki/List_of_HTTP_status_codes
http://en.wikipedia.org/wiki/404_error
You'll see 404 and 500 so commonly, that it's hard not to memorize them.
404 means that a resource was not found (which is why I tried having you
verify the path), while 500 means "internal server error" which is the most
vague one of them all.
- Oliver