Originally posted by sunitha raghu:
In your book you are mentioning use JSF , if the site is highly user interactive and for a basic dynamic web app there is no need to use JSF?
Can you please elaborate that?
Hans Bergsten, hans@gefionsoftware.com<br />Author of O'Reilly's<br />- JavaServer Pages,<br />- JavaServer Faces<br /><a href="http://www.hansbergsten.com/" target="_blank" rel="nofollow">http://www.hansbergsten.com/</a>
Kishore
SCJP, blog
Hans Bergsten, hans@gefionsoftware.com<br />Author of O'Reilly's<br />- JavaServer Pages,<br />- JavaServer Faces<br /><a href="http://www.hansbergsten.com/" target="_blank" rel="nofollow">http://www.hansbergsten.com/</a>
As a concrete example, say you need an editable table, where the user can change the values of a number of cells and submit them all at once. The values need to be validated, the table must be sortable and scrollable. Doing this with JSF is fairly simple (I show an example in the book), but doing it with plain JSP and/or servlets is pretty complex an messy. For this kind of interface, JSF is a better choice than plain JSP.
have a nice one
Originally posted by bas duijzings:
please correct me if i am wrong: After a user event on the component, only the component will be updated. Does it make a connection to the server ?
Say two dropdowns (classic web issue, if you do not want to work with flavours of javascript) One dropdown depends on the selection in the other dropdown. If you select something in the first dropdown, only the second dropdown will refresh itself (going back to the server, i assume ?)
Or am i too far off ?
Hans Bergsten, hans@gefionsoftware.com<br />Author of O'Reilly's<br />- JavaServer Pages,<br />- JavaServer Faces<br /><a href="http://www.hansbergsten.com/" target="_blank" rel="nofollow">http://www.hansbergsten.com/</a>
have a nice one
Originally posted by bas duijzings:
I just hoped you could do without the client side code, so i guess you cant.
Just a shame, since there are projects where you are not allowed to use client side code for things other then simple presentation (like image swapping) Businesslike issues in client side code, like managing a flow, or a submit, is often not allowed.
Kishore
SCJP, blog
have a nice one
Originally posted by sunitha raghu:
To use or not to use Javascript depends on which scenario we need to use. For example a validation should be done on server side because user can always turn off. But to increase the usability of the site like auto tabbing
we can always use JS.
Kishore
SCJP, blog
Originally posted by Kishore Dandu:
May be with JSF, there will be no need to use JavaScripy anymore. Just a guess from my side.
Hans Bergsten, hans@gefionsoftware.com<br />Author of O'Reilly's<br />- JavaServer Pages,<br />- JavaServer Faces<br /><a href="http://www.hansbergsten.com/" target="_blank" rel="nofollow">http://www.hansbergsten.com/</a>
Originally posted by Hans Bergsten:
I'll try to answer both questions here.
JSF is great for complex user interfaces, i.e., for web applications that look and feel as much as a GUI app as possible. For such an application, JSF boost productivity and reduces complexity.
<< snip >>
.
JSF / Jini / Javaspaces / JDO - all rock in my opinion.
Originally posted by Mike Brewer:
I'm thinking about developing a site that is similar to Slashdot or Kuro5hin in Java. I'm beginning to start evaluating frameworks to use in its creation. Is this the sort of project that you would recommend for JSF? Or would Struts be better for that sort of thing?
Also, you said that the JSF API is server side. However, it is an event driven framework. It'd seem to me that most events are user triggered. How does the page communicate the user events back to JSF on the server? Is it through simple links that are pre-written by JSF (as a result of JSF API programming), form submission, or some other method that I can't think of?
Hans Bergsten, hans@gefionsoftware.com<br />Author of O'Reilly's<br />- JavaServer Pages,<br />- JavaServer Faces<br /><a href="http://www.hansbergsten.com/" target="_blank" rel="nofollow">http://www.hansbergsten.com/</a>
Roland Barcia: IBM Distinguished Engineer, CTO Mobile for Lab Services
Originally posted by Roland Barcia:
The power of JSF is RAD development. Vendors such as WebSphere Studio provide an environment to quickly assemble pages.
Hans Bergsten, hans@gefionsoftware.com<br />Author of O'Reilly's<br />- JavaServer Pages,<br />- JavaServer Faces<br /><a href="http://www.hansbergsten.com/" target="_blank" rel="nofollow">http://www.hansbergsten.com/</a>
Hans Bergsten, hans@gefionsoftware.com<br />Author of O'Reilly's<br />- JavaServer Pages,<br />- JavaServer Faces<br /><a href="http://www.hansbergsten.com/" target="_blank" rel="nofollow">http://www.hansbergsten.com/</a>
Byron Estes<br />Sun Certified Enterprise Architect<br />Senior Consulant<br />Blackwell Consulting Services<br />Chicago, IL<br /><a href="http://www.bcsinc.com" target="_blank" rel="nofollow">www.bcsinc.com</a>
Hans Bergsten, hans@gefionsoftware.com<br />Author of O'Reilly's<br />- JavaServer Pages,<br />- JavaServer Faces<br /><a href="http://www.hansbergsten.com/" target="_blank" rel="nofollow">http://www.hansbergsten.com/</a>
JSF is great for complex user interfaces, i.e., for web applications that look and feel as much as a GUI app as possible. For such an application, JSF boost productivity and reduces complexity.
As a concrete example, say you need an editable table, where the user can change the values of a number of cells and submit them all at once. The values need to be validated, the table must be sortable and scrollable. Doing this with JSF is fairly simple (I show an example in the book), but doing it with plain JSP and/or servlets is pretty complex an messy. For this kind of interface, JSF is a better choice than plain JSP.
Originally posted by Ken Januski:
Hans,
I'm currently developing some jsp pages which do their best to mimic an editable table where users get a number of results from database and then update them. This is similar to what you mention below.
But I'm wondering if you can give any idea as to just how steep the learning curve is on learning enough of JSF to get a working application. I know this is pretty subjective and that there are members of varying abilities and experience. I'm someone who's done a few projects with jsp and servlets but have never looked at Struts or any other framework. Though I'm in a department of 10-15 I'll be the only one doing any work on this most likely. In your estimation do you think JSF if something that someone working on their own and balancing other non-Java projects could pick up in a month or so?
Thanks for your thoughts,
Ken
Hans Bergsten, hans@gefionsoftware.com<br />Author of O'Reilly's<br />- JavaServer Pages,<br />- JavaServer Faces<br /><a href="http://www.hansbergsten.com/" target="_blank" rel="nofollow">http://www.hansbergsten.com/</a>
"No one appreciates the very special genius of your conversation as the dog does."
Originally posted by John Dunn:
Might be dumb question, but how easy is it to use JSF, if I just have pages of data from a db with links to other pages. Not too much user interface for now, but that may change. Can I do use jsf here, so that if more user activities develops I don't have to throw away jsp and replace??
Hans Bergsten, hans@gefionsoftware.com<br />Author of O'Reilly's<br />- JavaServer Pages,<br />- JavaServer Faces<br /><a href="http://www.hansbergsten.com/" target="_blank" rel="nofollow">http://www.hansbergsten.com/</a>
Your mind is under my control .... your will is now mine .... read this tiny ad
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com
|