Transaciton becomes dirty

Question

I have a table thats bound to a View Object that I use for searching. When I double click a row in the table it sets the current Row of another view object that is displayed on the page.
The JTable is not editable and is declared like:
searchResultsTable = new JTable(){
public boolean isCellEditable(int r, int c) {
     return false;
so it always returns false when an edit is attempted.
Sometimes when I select rows in the table it makes the transaction dirty. I have a listener that disables/enables components (save button etc) when this happens. If the table is not editable and I am not editing any components how is the transaction becoming dirty by switching records? This behavior does not happen on every row selected, but happens regularly on certain rows.
Could the current values of a selected row trigger the transaciton to be dirty?
thanks
Jeff

Answer 1

Double click on a JTable by default calls setCellValue on it's model to dirty the model. If you want an alternate behavior, I'd suggest overriding editingStopped method on the table and perform appropriate value comparision before calling setValueAt.
    public void editingStopped(ChangeEvent e) {
        // Take in the new value
        TableCellEditor editor = getCellEditor();
        if (editor != null) {
            Object value = editor.getCellEditorValue();
            if (!value.toString().equals(getValueAt(value, editingRow, editingColumn).toString())
               setValueAt(value, editingRow, editingColumn);
            removeEditor();