Hello,

I'm in the process of making my own ListModel by extending
AbstractListModel. That's not difficult. But i'm having problems with
my infrastructure, my new created Model tend to be more like a
Controller. For example:

====
public class UserManagerListModel extends AbstractListModel {
 private ArrayList listUsers;
 private UserManager um;
 private SessionFactory sessionFactory;

 public UserManagerListModel(SessionFactory sessionFactory) {
   this.sessionFactory=sessionFactory;
   um=new UserManager(sessionFactory);
   listUsers=(ArrayList)um.getUsers();
 }
 public Object getElementAt(int index) {
   return listUsers.get(index);
 }
 public int getSize() {
   return listUsers.size();
 }
 private void updateUsers(){
   listUsers=(ArrayList)um.getUsers();
   this.fireContentsChanged(this, 0, getSize());
 }
 public void storeUser(User u){
   um.storeUser(u);
   updateUsers();
 }
 public void removeUser(User u){
   um.removeUser(u);
   updateUsers();
 }
}
====

The variable "UserManager" is my DAO object which stores and retrieves
and find data in the database.

Additional i have a JFrame which contains the JList with the
"UserManagerListModel" as model.

====
JList listusers = new JList();
listusers.setModel(new UserManagerListModel(sessionFactory));
====

The Frame also consists of several Add, Remove and Change buttons to
change the name of the user. For example a user press the Add button.
The following happens:

===
User u=id.getUser();
u.setGebruikersnaam(naam);
((UserManagerListModel)listusers.getModel()).storeUser(u);
===

As you can see i must get the Model from the JList, do a cast and then
i call the storeUser() methode of the UserManagerListModel to save the
user to the database.

I do not really like the construct:
"((UserManagerListModel)listusers.getModel()).storeUser(u);"
it's seems a bit like dirty programming to me.

Does there exists a better solution (/pattern) with not much overhead,
which makes things a little cleaner?

Thanks,

joop