How to refresh JTable with always-changing tableModel?

Question

2015.5.5 22:11 updated. I found that, when I create a sorter and call setRowSorter() method in the MyTable's construction, afterwards, it will keep the original line number(in which the data still refresh correctly but not easy to discover)even though the dataModel inside is already changed many times which can be proven as printf(getModel().getRowCount()). What's more, MyTable.getAutoCreateRowSorter() always return true. I must explicitly call setAutoCreateRowSorter(true) to fix the issue it if I called setRowSorter(). I am happy but this is still wierd.

---

[2015.5.5 6:19 updated] I have found a way to access: make a "setRow" with the combination of insertRow() and removeRow() and everytime I update, I setrRow all the rows in the table. It reflect immediately in the UI. BUT there will be a series of error begin with "AWT-EventQueue-0" java.lang.IndexOutOfBoundsException: Invalid index" and I　guess it's about some kiind of swing thread problem because I can see "RepaintManager" or "paint" in the error. It occurs especially when I move the scrollbar when it's running.(but it still occur if I don't move it)

I have a JTable in a JScrollPane in a JFrame. I initial a MyTableModel with a data and use it to Create a JTable.Like this

MyTableModel extends DefaultTableModel{
    Data data;
    //object

    MyTableModel (Data a){
    data = a;
    // do something to initial the table model,like build object[][] and add rows.   
    }
}
class main{
MyTableModel tm = new MyTableModel(data);
Jtable table = new JTable(tm);
JScrollpane jsp = new JScrollpane(table);
JFrame window = new JFrame();
window.getxxxpane().add(jsp);



}

So, as my data is always changing/updating and the changed row is plural and impossible to caculate.

while(true){
    data.change();

    refreshing the table to display the data immediately;

}

my idea is to simply build a new MyTableModel object and set it as the table's model like:

 table.setModel(new MyTableModel(data));   //data had been changed.

which doesn't work. and I tried this:

  tm = MyTableModel(data);
  tm.fireTableDataChanged();

which doesn't work either. and the combination as well:

  MyTableModol nm = new MyTableModel(data); //data had been changed
  table.setModel(nm);
  nm.fireTableDataChanged();

Could someone please give me some clue to change the TableModel object in an unchangable Jtable and update everytime.I dont want to change the tableModel Object because the calculation is huge, instead ,i Want to always create a new object with the construction method's parameter(changed data).

the most worst method is to remove the JScrollpane and rebuild one table/tablemodel/jscrollpane and re-add it, in which I have to call window.setVisible(true). window.repait() doesn't work,either,unless I move it. I create a space-wasting but runnable program for demostration ,which most of them are nonsense.

import java.awt.BorderLayout;
import java.awt.event.ActionEvent;
import java.awt.event.ActionListener;
import java.util.Formatter;

import javax.swing.JButton;
import javax.swing.JFrame;
import javax.swing.JScrollPane;
import javax.swing.JTabbedPane;
import javax.swing.JTable;
import javax.swing.table.DefaultTableModel;

class TM extends DefaultTableModel {
    int[] inside;
    static String[] columnNames = { "Hellium", "Radon",

    };

    TM(int[] data) {
        super(columnNames, 0);
        this.inside = data;
        update();
    }

    void update() {
        Object[][] data = new Object[2][columnNames.length];

        for (int i = 0; i < 2; ++i) {

            data[i][0] = inside[0];

            data[i][1] = inside[1];
           // setValueAt(aValue, row, column);
            addRow(data[i]);

        }
        fireTableDataChanged();
    }

}

class idkName {
    TM tm;
    JButton jb, jb2;
    int data[] = { 1, 2 };
    int data2[] = { 9, 10 };
    JTable table;
    JScrollPane jsp;
    JFrame twindow;

    idkName() {
        JFrame window = new JFrame();
        window.setSize(400, 400);
        window.setLayout(new BorderLayout());
        jb = new JButton("show");
        jb2 = new JButton("change model");
        window.add(jb, BorderLayout.EAST);
        window.add(jb2, BorderLayout.WEST);
        twindow = new JFrame();

        jb.addActionListener(new ActionListener() {

            @Override
            public void actionPerformed(ActionEvent arg0) {
                tm = new TM(data);
                table = new JTable(tm);
                jsp = new JScrollPane(table);
                twindow.getContentPane().add(jsp);
                twindow.setSize(500, 500);
                twindow.setVisible(true);

            }
        });
        window.setVisible(true);

        jb2.addActionListener(new ActionListener() {

            @Override
            public void actionPerformed(ActionEvent e) {
                // TODO Auto-generated method stub
                // tm = new TM(data2);

                tm = new TM(data2);

                System.out.println(""+tm.getValueAt(0,0));
                tm.fireTableDataChanged(); 
                twindow.setVisible(true); 

            }
        });

    }
}
public class main2 {
    TM tm;
    public static void main(String[] args) {
        idkName i = new idkName();
    }

}

Answer 1

If you're going to extend DefaultTableModel, then when the data is changed, you need to update it in DefaultTableModel's internal representation using the setValueAt or setDataVector methods. If you have extensive changes (which it sounds like you do), use the setDataVector method to change all the cells and the table structure at once. Your example code looks like it's missing some updates because it's not pushing the new values in to the DefaultTableModel's data vectors.

But since you have a lot of updates, you're probably better off avoiding DefaultTableModel and just extending AbstractTableModel, using your own custom data storage, and calling the appropriate fireXxx() methods whenever your data changes. This will probably be more efficient in terms of both data conversion and number of events raised.

And then make sure all the event and value change work is done on the AWT event thread, using SwingWorkers or other threading support.