OK, so if the model is to encapsulate access to the database, why have a JModel class? It seems to me that both JTable and JModel need to be one class, not separate.The model is the part of the component that encapsulates the application’s data. It will often provide routines to manage and manipulate this data in a meaningful way in addition to routines that retrieve the data from the model. In our case, the model will contain methods to add, remove and update information about the books in the database. It will also contain methods to retrieve the list of books from the database. In general, the underlying data access technique should be encapsulated in the model. In this way, if an application is to be moved from a system that utilizes a flat file to store its information to a system that uses a database, the model is the only element that needs to be changed, not the view or the controller.
Also, if JTable models a database table, but doesn't include JOIN and FOREIGN KEY functionality, why bother?
Anyone care to straighten me out?