Joe Cheng wrote: >>>Each Action class should correspond to one request type, so if you >>> > support retrieving data with one request and update with another, > you should have two Access classes. If you have one request type > that combines multiple database operations, say update information > and then retrieves the updated info, you should have one Access > class for both operations. Again Action classes correspond one-to-one > with request types. << > > Are you using the labels "Action" and "Access" interchangably? Forgive my > ignorance, I'm not familiar with this vocabulary.
Oops, "Access classes" is a typo. It should be "Action classes". For more about what I mean by Action class (and Data Access Object, DAO) I hope it's clear in the context of the complete thread. Basically, Action classes handle requests and DAO classes encapsulate database access. Hans -- Hans Bergsten [EMAIL PROTECTED] Gefion Software http://www.gefionsoftware.com JavaServer Pages http://TheJSPBook.com =========================================================================== To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST". Some relevant FAQs on JSP/Servlets can be found at: http://archives.java.sun.com/jsp-interest.html http://java.sun.com/products/jsp/faq.html http://www.esperanto.org.nz/jsp/jspfaq.jsp http://www.jguru.com/faq/index.jsp http://www.jspinsider.com
