TableModel that
uses a Vector of Vectors to store the
cell value objects.
Warning:
Serialized objects of this class will not be compatible with
future Swing releases. The current serialization support is
appropriate for short term storage or RMI between applications running
the same version of Swing. As of 1.4, support for long term storage
of all JavaBeansTM
has been added to the java.beans package.
Please see java.beans.XMLEncoder
.
DefaultTableModel
which is a table of zero columns and zero rows.DefaultTableModel with
rowCount and columnCount of
null object values.DefaultTableModel with as many columns
as there are elements in columnNames
and rowCount of null
object values. Each column's name will be taken from
the columnNames vector.DefaultTableModel with as many
columns as there are elements in columnNames
and rowCount of null
object values. Each column's name will be taken from
the columnNames array.DefaultTableModel and initializes the table
by passing data and columnNames
to the setDataVector method.DefaultTableModel and initializes the table
by passing data and columnNames
to the setDataVector
method. The first index in the Object[][] array is
the row index and the second is the column index.columnName, which may be null. This method
will send a
tableChanged notification message to all the listeners.
This method is a cover for addColumn(Object, Vector) which
uses null as the data vector.columnName. columnData is the
optional array of data for the column. If it is null
the column is filled with null values. Otherwise,
the new data will be added to model starting with the first
element going to row 0, etc. This method will send a
tableChanged notification message to all the listeners.columnName, which may be null.
columnData is the
optional vector of data for the column. If it is null
the column is filled with null values. Otherwise,
the new data will be added to model starting with the first
element going to row 0, etc. This method will send a
tableChanged notification message to all the listeners.null values unless rowData is specified.
Notification of the row being added will be generated.null values unless rowData is specified.
Notification of the row being added will be generated.
The equals method implements an equivalence relation
on non-null object references:
x, x.equals(x) should return
true.
x and y, x.equals(y)
should return true if and only if
y.equals(x) returns true.
x, y, and z, if
x.equals(y) returns true and
y.equals(z) returns true, then
x.equals(z) should return true.
x and y, multiple invocations of
x.equals(y) consistently return true
or consistently return false, provided no
information used in equals comparisons on the
objects is modified.
x,
x.equals(null) should return false.
The equals method for class Object implements
the most discriminating possible equivalence relation on objects;
that is, for any non-null reference values x and
y, this method returns true if and only
if x and y refer to the same object
(x == y has the value true).
Note that it is generally necessary to override the hashCode method whenever this method is overridden, so as to maintain the general contract for the hashCode method, which states that equal objects must have equal hash codes.
TableModel interface and is not used by the
JTable.[row, column] has been updated.TableModelListeners that registered
themselves as listeners for this table model.JTable should redraw the
table from scratch. The structure of the table (as in the order of the
columns) is assumed to be the same.[firstRow, lastRow], inclusive, have been deleted.[firstRow, lastRow], inclusive, have been inserted.[firstRow, lastRow], inclusive, have been updated.JTable receives this event and its
autoCreateColumnsFromModel
flag is set it discards any table columns that it had and reallocates
default columns in the order they appear in the model. This is the
same as calling setModel(TableModel) on the
JTable.Object.class regardless of columnIndex.Vector of Vectors
that contains the table's
data values. The vectors contained in the outer vector are
each a single row of values. In other words, to get to the cell
at row 1, column 5:
((Vector)getDataVector().elementAt(1)).elementAt(5);
FooListeners
upon this AbstractTableModel.
FooListeners are registered using the
addFooListener method.
You can specify the listenerType argument
with a class literal,
such as
FooListener.class.
For example, you can query a
model m
for its table model listeners with the following code:
TableModelListener[] tmls = (TableModelListener[])(m.getListeners(TableModelListener.class));If no such listeners exist, this method returns an empty array.
row
and column.java.util.Hashtable.
The general contract of hashCode is:
hashCode method on each of
the two objects must produce the same integer result.
As much as is reasonably practical, the hashCode method defined by class Object does return distinct integers for distinct objects. (This is typically implemented by converting the internal address of the object into an integer, but this implementation technique is not required by the JavaTM programming language.)
row in the model. The new row
will contain null values unless rowData
is specified. Notification of the row being added will be generated.row in the model. The new row
will contain null values unless rowData
is specified. Notification of the row being added will be generated.start to
end to the to position in the model.
After the move, the row that was at index start
will be at index to.
This method will send a tableChanged notification
message to all the listeners.
Examples of moves:1. moveRow(1,3,5); a|B|C|D|e|f|g|h|i|j|k - before a|e|f|g|h|B|C|D|i|j|k - after
2. moveRow(6,7,1); a|b|c|d|e|f|G|H|i|j|k - before a|G|H|b|c|d|e|f|i|j|k - after
fireTableChanged.setSize method in
Vector which truncates vectors
which are too long, and appends nulls if they
are too short.
This method also sends out a tableChanged
notification message to all the listeners.wait methods.
The awakened thread will not be able to proceed until the current thread relinquishes the lock on this object. The awakened thread will compete in the usual manner with any other threads that might be actively competing to synchronize on this object; for example, the awakened thread enjoys no reliable privilege or disadvantage in being the next thread to lock this object.
This method should only be called by a thread that is the owner of this object's monitor. A thread becomes the owner of the object's monitor in one of three ways:
synchronized statement
that synchronizes on the object.
Class, by executing a
synchronized static method of that class.
Only one thread at a time can own an object's monitor.
wait methods.
The awakened threads will not be able to proceed until the current thread relinquishes the lock on this object. The awakened threads will compete in the usual manner with any other threads that might be actively competing to synchronize on this object; for example, the awakened threads enjoy no reliable privilege or disadvantage in being the next thread to lock this object.
This method should only be called by a thread that is the owner
of this object's monitor. See the notify method for a
description of the ways in which a thread can become the owner of
a monitor.
row from the model. Notification
of the row being removed will be sent to all the listeners.fireTableChanged.null cell values.
If the new size is less than the current size, all columns at index
columnCount and greater are discarded.newIdentifiers is greater than the current number
of columns, new columns are added to the end of each row in the model.
If the number of newIdentifiers is less than the current
number of columns, all the extra columns at the end of a row are
discarded. newIdentifiers is greater than the current number
of columns, new columns are added to the end of each row in the model.
If the number of newIdentifiers is less than the current
number of columns, all the extra columns at the end of a row are
discarded. dataVector instance
variable with the values in the array dataVector.
The first index in the Object[][]
array is the row index and the second is the column index.
columnIdentifiers are the names of the new columns.dataVector instance variable
with the new Vector of rows, dataVector.
Each row is represented in dataVector as a
Vector of Object values.
columnIdentifiers are the names of the new
columns. The first name in columnIdentifiers is
mapped to column 0 in dataVector. Each row in
dataVector is adjusted to match the number of
columns in columnIdentifiers
either by truncating the Vector if it is too long,
or adding null values if it is too short.
Note that passing in a null value for
dataVector results in unspecified behavior,
an possibly an exception.
setRowCount instead.rowCount and greater are discarded. column and
row. aValue is the new value. This method
will generate a tableChanged notification.toString method returns a string that
"textually represents" this object. The result should
be a concise but informative representation that is easy for a
person to read.
It is recommended that all subclasses override this method.
The toString method for class Object
returns a string consisting of the name of the class of which the
object is an instance, the at-sign character `@', and
the unsigned hexadecimal representation of the hash code of the
object. In other words, this method returns a string equal to the
value of:
getClass().getName() + '@' + Integer.toHexString(hashCode())
The current thread must own this object's monitor. The thread
releases ownership of this monitor and waits until another thread
notifies threads waiting on this object's monitor to wake up
either through a call to the notify method or the
notifyAll method. The thread then waits until it can
re-obtain ownership of the monitor and resumes execution.
As in the one argument version, interrupts and spurious wakeups are possible, and this method should always be used in a loop:
synchronized (obj) {
while (<condition does not hold>)
obj.wait();
... // Perform action appropriate to condition
}
This method should only be called by a thread that is the owner
of this object's monitor. See the notify method for a
description of the ways in which a thread can become the owner of
a monitor.The current thread must own this object's monitor.
This method causes the current thread (call it T) to place itself in the wait set for this object and then to relinquish any and all synchronization claims on this object. Thread T becomes disabled for thread scheduling purposes and lies dormant until one of four things happens:
A thread can also wake up without being notified, interrupted, or timing out, a so-called spurious wakeup. While this will rarely occur in practice, applications must guard against it by testing for the condition that should have caused the thread to be awakened, and continuing to wait if the condition is not satisfied. In other words, waits should always occur in loops, like this one:
synchronized (obj) {
while (<condition does not hold>)
obj.wait(timeout);
... // Perform action appropriate to condition
}
(For more information on this topic, see Section 3.2.3 in Doug Lea's
"Concurrent Programming in Java (Second Edition)" (Addison-Wesley,
2000), or Item 50 in Joshua Bloch's "Effective Java Programming
Language Guide" (Addison-Wesley, 2001).
If the current thread is interrupted by another thread while it is waiting, then an InterruptedException is thrown. This exception is not thrown until the lock status of this object has been restored as described above.
Note that the wait method, as it places the current thread into the wait set for this object, unlocks only this object; any other objects on which the current thread may be synchronized remain locked while the thread waits.
This method should only be called by a thread that is the owner
of this object's monitor. See the notify method for a
description of the ways in which a thread can become the owner of
a monitor.
This method is similar to the wait method of one
argument, but it allows finer control over the amount of time to
wait for a notification before giving up. The amount of real time,
measured in nanoseconds, is given by:
1000000*timeout+nanos
In all other respects, this method does the same thing as the method of one argument. In particular, wait(0, 0) means the same thing as wait(0).
The current thread must own this object's monitor. The thread releases ownership of this monitor and waits until either of the following two conditions has occurred:
notify method
or the notifyAll method.
timeout
milliseconds plus nanos nanoseconds arguments, has
elapsed.
The thread then waits until it can re-obtain ownership of the monitor and resumes execution.
As in the one argument version, interrupts and spurious wakeups are possible, and this method should always be used in a loop:
synchronized (obj) {
while (<condition does not hold>)
obj.wait(timeout, nanos);
... // Perform action appropriate to condition
}
This method should only be called by a thread that is the owner
of this object's monitor. See the notify method for a
description of the ways in which a thread can become the owner of
a monitor.