Last week, we had the author of TDD for a Shopping Website LiveProject. Friday at 11am Ranch time, Steven Solomon will be hosting a live TDD session just for us. See for the agenda and registration link
Rauhl Roy wrote:i am using Eclipse: Version: 3.4.1
By the way, it's odd that Eclipse didn't show any warning regard to the commandButton. Or did you miss it? Or didn't you add the JSF facet to the web project?
I have checked this application by all means, in fact I followed your tutorial only, the example you gave on your blog was running like anything. But it never worked even I added one more page to your application and tried to display values from the main page.
And one more thing is, are we supposed to write all HTML tags in every JSF page?
And Eclipse does not show any thing on console is there any place where we can see log file of JSP.
Now, do the same in JSF. It also has a component for it. If you configured Eclipse the way as in my tutorial, you should see a warning around the h:commandButton element that it is missing some required parent component.
And one more thing is, are we supposed to write all HTML tags in every JSF page?
No, but knowledge of HTML is fairly important. Simply because JSF generates HTML.
I did same as you did in your blog these are the error/ warning which are shown on the console of eclipse IDE,
please let m know how to solve the problem.
This is not an error. This is a warning. Stuff should just work.
This warning comes because eclipse modifies the Tomcat´s server.xml to add the module contexts (web projects) and Eclipse is using a new attribute 'source' to indicate the web project location in Eclipse. When Tomcat starts up, it will validate the XML and it will show warnings when it encounters unknown tags or attributes.
Those warnings doesn´t harm. You can just ignore it. If you really want to get rid of it, doubleclick the Tomcat server entry in Eclipse to get its configuration and under 'Server Options' enable the 'Publish module contexts to separate XML files' option.