Post by:Alex Kravets
Of course whenever possible it is better to have one servlet to do all you stuff. Besides, form checking and database updates are pretty forward routines. Have you considered using JavaBeans and JSP?
Post by:Cynthia Yao
Well, I need very strict seperation between presentation and logic, all content will go through another process for update. That is why I choose servlet. If could, I would rather use jsp which I am more familiar with. All databse access will use bean, I wrote two small servlet to handle form validation and email. If the client decide to add more similiar stuff, I would just change the property file. Well, maybe client would not make that much changes, maybe I should wrote singel servlet to handle one process. Thanks
He loves you so much! And I'm baking the cake! I'm going to put this tiny ad in the cake:
RavenDB is an Open Source NoSQL Database that’s fully transactional (ACID) across your database