This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
thanks, Bear, for your improvement now i have: , which translates to: <link href="/css/blog.css" rel="stylesheet" type="text/css" />
BTW, i'd like to grab the oportunity to adress a question that i have in my mind for a while: i've read some (beginers) tutorials on servlets and jsp, and all of them refer that servlets are suitable for code and jsp for html (said in a short and imprecise way) anyway, all database code i found use servlets - so i end up with the usual mess of code and print statements! i wonder if there is a way to split things: jsp would be in charge of presentation and servlet would deal with database stuff
What should i read about to get it going that way? (maybe "sending" the recordset to the jsp...)
TiA [ November 17, 2006: Message edited by: miguel lisboa ]
You will be sending the data to the JSP, but not as a result set. That's a database concept and should remain sequenstered in model/business code. The model layer should abstract the data into POJOs or DTOs for use by the UI layer.