Table/TableModel - Allow for use of Java Objects to follow Java Swing MVC pattern

[Orbisman]

Issue:
Current design acts on the individual properties/fields in the POJO (plain old java object), not the whole POJO, restricting the developer to use Strings or manage individual fields separate from the POJO.

Suggested Changes:
Enhance the TableModel and Table classes where necessary to more closely follow the Java Swing MVC (Model View Controller) pattern to give better
flexibility when using POJOs. A new Junit / Test app will be provided to demonstrate and validate changes.

Example(s):
List getRow(); would be V getRow(); - Where V is the POJO object, not a list of the individual columns.

addRow(Collection values); new method would be added addRow(V value); - Where V is the new POJO to be added.

Notes:

• Changes will retain the existing support for String based models as much as possible for backward compatibility.
• A Pull Request will be submitted for consideration