SpringAtom-#6 Data layer [Hibernate]

removed fluent-interface...was weird using this
for now I am in the progress of switching all setters to return the instance of the object(this)
SpringAtom-#6 Data layer [Hibernate]

removed redundant files
leftovers from fluent-interface library...was really tough to use that
so i decided to currently drop it and maybe figure out something by my own or whatsoever...maybe something to produce custom java classes.
SpringAtom-#6 Data layer [Hibernate]

a lot of changes has been made
- provided several interfaces which are further to be used in repositories and services and are meant to serve as foundamental base for further development and extending existing functionality
- contacts have been divided and wrapped in several interfaces
-- we have four interfaces that defines functionality of SContactAware implementations
--- SContactable means that instance of it may be contacted using one of the SContact instances. SContactable defines an email value as its base
--- SMultiContactable provides facility that says I can be contacted using not only SContact(mail) but a lot of more points
-- contacts have been divided to be more safe againts meta data which match their purpose (for example SPersonEmailContact is a contact which holds  a meta data that correspond to appropriate value)
-- SBasicContact is the base for targeted contacts (SContactable), first usage of it is SPersonContact which use SPerson instances as the target of the contact
- notifications are also affected
-- removed several links which were telling that notification has been send to the SClient instances
-- now notifications are diverted to serve following issues:
--- we want to sent notification to someone (we use one of the subclasses of SBasicTargetedNotification)
--- we want to sent notification to someone which concerns something (we use one of the subclass of SBasicConcerningNotification, which in fact is also targeted)
- improved naming
- added OOTB validator (coming either from JPA or Hibernate)
SpringAtom-#6 Data layer [Hibernate]

fix error in SAppointment
- coulnd save the SAppointment instance due to SAppointment tasks not being persisted prior to it..solved with cascading the persists event
- fix validating annotation