Chandella Montero wrote:Why? I still don't understand.
What happens if you pass an int?
Tim Holloway wrote:navigation is to URLs, not to resources. Therefore your rule must specify a URL, giving us:
3. If the destination URL cannot be resolved, no navigation can occur.
Actually, I thought this was supposed to result in a "404" error, but at any rate, it can't succeed.
Tim Holloway wrote:1. Failure of one or more fields in the form to validate (hint: include an "h:messages" element on the view containing the form).
2. Failure to find the action method. This can happen if the action method does not exist, the name is misspelled/miscapitalized, or if it doesn't have the proper signature: "public String xxxxx()". No error will display in this case. Failure is silent.
Multiple Annotations on this line:
The content of element type must match "(head, body)"
Attribute "xmlns:h" must be declared for element type html
Attribute "xmlns:f" must be declared for element type html
Tim Holloway wrote:
Tim Holloway wrote:The message you got from Tomcat 5.5 was probably because 5.5 JSF webapps also requires the EL jar that's part of Tomcat 6.
I'm not sure about the html error. The first message I think would require being able to see some more of the HTML than just the outermost element. The 2 namespace errors shouldn't be happening if the jsf-api jar is located in the apps classpath, since that's where those definitions are stored.
BTW, it's usually better to start a new thread. Otherwise we sometimes end up with conversations on 2 different subjects and that can not only be confusing, it can make it a little harder for people who use the forum search.
Tim Holloway wrote:Hello Menen, welcome to the JavaRanch.
When you create a JSF webapp, you must include the JSF api jar as part of the webapp, and like all library JARs for a J2EE WAR, that means you put a copy of the jsf-api.jar in the webapp's WEB-INF/lib directory.
Tomcat is not JEE 5 compliant, so the actual JSF implementation classes aren't a standard part of Tomcat the way they are in full-fledged JEE servers. So you have to also include the jsf-impl.jar in WEB-INF/lib.
Multiple Annotations on this line:
The content of element type must match "(head, body)"
Attribute "xmlns:h" must be declared for element type html
Attribute "xmlns:f" must be declared for element type html
Ankit Garg wrote:
i.e. the Run2 r2 = (Run2)r; isn't two instances of the same thread, but two threads with the same instance of runnable? So calling start on each is legal?
The line you mentioned just creates a sort of alias to r. Neither does it create two instances of a thread, nor it creates two threads with the same runnable. It is just a plain assignment.
Neha Daga wrote:because the runnable object instance passed to both threads is same. If you had created a new runnable object and passed it to second thread then it would have been 1 2 1 2.
Bauke Scholtz wrote:Make sure that the request URL matches the url-pattern of the FacesServlet entry in web.xml. This way the request will be passed through the FacesServlet, which on its turn creates the FacesContext. Otherwise the JSF components in the JSP page will complain that the FacesContext cannot be found and hence this exception.
If the url-pattern is for example *.jsf, you should be invoking the page as /page.jsf, not as /page.jsp.