I'm not sure a JTable is the way to go. Just because you need to model multiple instances of an editor does not mean tha
you should use a JTable.
Alternatively, write an ObjectEditor class (what Objects are they by the way, it makes the conversation easier... ). An ObjectEditor instance will allow the user to set some attributes on an object.
Then all you have to do is create as many ObjectEditors as the user chooses objects. When the user needs to pick up an additional object, you just create a new ObjectEditor instance. This is just as easy as adding an extra row to a JTable.
Does that help ?
D.