JSP is nothing more than servlet code woven with html and some tags to
make generating html pages more easy. Almost everything you can do in
sevlet code you can do also in JSP page. So it is a design decision
what logic should be kept in JSP and what logic should tackled in a
classic servlet code.
I think that what you have written is very sound and follow MVC
approach. JSP should be responsible only for user interface ("view"
part) and be separated from any persistent logic, and servlet code
should keep "model" and "control" part and be separated from any
interface code. Servlet code should also be the only to communicate
with the persistence layer.But why use pure JSP and servlet ? There are a lot of good frameworks at hand. There are successful stories with JSF 2.0 and Spring MVC running gently with Google App Engine. http://groups.google.com/group/google-appengine-java/web/will-it-play-in-app-engine?pli=1 Also GWT is running very nicely - I'm personally very fond of it. But GWT is completely different, Ajax-style, approach. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~----------~----~----~----~------~----~------~--~---
