This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
Hi Alex You are right.JSP is a compiled into a servlet. Regarding technologies,the downside of using servlets is there will be too many out.print statements in ur java code. besides your html code will be interspersed with the java code.
using servlet-jsp combination would be a good approach. servlet for the navigation part and jsp for the view part.
U could start reading about struts,which is a framework rather than a technology.The ranch site for struts is a good place to start off with.i am not very familiar with Java Swings,i belive is also more or less based on MVC architecture.
hth thanks cheers vinnym
proud Fan of European Champion CHELSEA FC
"If you don't see the bug where you're looking, perhaps you're looking in the wrong place" -James Gosling
I would be tempt to do applets... but I know some people consider it to be history..
I did JSF for a while, even tho im not an expert at all.. I do understand how stuff works a little bit (simply made a mistake in my first post using "servlet" when really I meant "applet").
About JSP being a jump in the past, let me explain myself. It's just my personal opinion: pure JSP (meaning not with jsf for instance) is simply scripting and is quite far from OO programming. However I never did pure JSP and thats why I'm asking your opinions, because I don't know enough on the subject.
I'm looking for the best choice of technology to spend some time on..
Applet looked like the easy path, but again I read was outdated..
pure JSP (meaning not with jsf for instance) is simply scripting
You've been out of the loop for a while, haven't you?
With JSP 2.0 the move is strongly away from any scripting on the pages, and towards completely scriptless pages using technologies like the JSTL (JSP Standard Tag Library) and EL (Expression Language), and making use of custom actions developed using the new and simpler tag handling mechanisms.
Usually a servlet is used as a front controller to perform any processing, and then forwarding to a JSP page to render the view. [ January 31, 2006: Message edited by: Bear Bibeault ]
JSF is more than a simple collection tags. From the J2EE Tutorial:
The main components of JavaServer Faces technology are as follows: # An API for representing UI components and managing their state; handling events, server-side validation, and data conversion; defining page navigation; supporting internationalization and accessibility; and providing extensibility for all these features # Two JavaServer Pages (JSP) custom tag libraries for expressing UI components within a JSP page and for wiring components to server-side objects
Tough in space?, <a href="http://tjws.sf.net" target="_blank" rel="nofollow">Get J2EE servlet container under 150Kbytes here</a><br />Love your iPod and want it anywhere?<a href="http://mediachest.sf.net" target="_blank" rel="nofollow">Check it here.</a><br /><a href="http://7bee.j2ee.us/book/Generics%20in%20JDK%201.5.html" target="_blank" rel="nofollow">Curious about generic in Java?</a><br /><a href="http://7bee.j2ee.us/bee/index-bee.html" target="_blank" rel="nofollow">Hate ant? Use bee.</a><br /><a href="http://7bee.j2ee.us/addressbook/" target="_blank" rel="nofollow">Need contacts anywhere?</a><br /><a href="http://searchdir.sourceforge.net/" target="_blank" rel="nofollow">How to promote your business with a search engine</a>