Due to a bug in the JPA validator columns with camel case names are
flagged as missing (probably due to the case-insensitive nature of SQL).
This has been circumvented by assigning every column with a camel case
name a new name with underscores.
The inheritance strategy of the Contacts class has been changed to
single table for performance reasons.
These were partially caused by an old Hibernate validator which has now
been replaced by the EclipseLink validator for the current JPA standard.
Another error was caused by the use of non-standard JPQL in the user
search query which has now been replaced by a standardized one.
*Added a contact abstract class that serves as a superclass for user and
group
* Added a group class
* Updated persistenceManager to fit the new contact system.
* Updated all classes that used methods, that were updated.
The ObjectMessageReader does function normally for single messages but
will deliver corrupted objects when a message consisting of multiple
objects is received.
additionally cleaned up whole project, fixed some Javadoc errors and
added a few database and connection options.
Sorry for the huge commit, there was almost no time inbetween where a
commit would have been possible, as to solve every problem, a new
problem arose.
However, as of now, f/message_handling should be ready to be merged into
develop, besides that it could not be tested yet.
At this moment the client is not able to receive to objects sent
consecutively. This will be worked on in a future commit and should be
fixed before merging this branch into develop.
Kai S. K. Engelbart
delvh