AuditerConsumer moved to Auditer

- getMessages, getFullMessages, getMessagesForParser and getMessagesForParserLikePairWithId renamed to pollConsumer methods
- methods added to blImpl, entry and rpc
- added for update to select queries for last processed id (lock)
- authorization into entry layer for PerunAdmin
- added createAuditerConsumer method
CORE,REGISTRAR: changed SimpleJdbcTemplate to JdbcTemplate

- SimpleJdbcTemplate is marked as deprecated so JdbcTemplate should
  be used instead. Class API is the same, but support ResultSetExctractor.
- Removed some unused imports.
- Instance check is kept in Utils.getNewId() since somebody still may pass
  this class as data source.
CORE: Fixed jdbc data source type for Searcher

- Use NamedParameterJdbcTemplate instead of JdbcTemplate since it can't
  handle named parameters used in Searcher.
- Commented out stdout in Searcher tests.

  Note: Previous SimpleJdbcTemplate (deprecated) combines JdbcTemple and
  NamedParameterJdbcTemplate, so it was possible to pass both types of params
  to the same jdbc template. Now we must choose and pass proper params.
Minor fixes - removed separator & imports, javadoc changes

- PrivilageException added to javadoc for methods in AuditMessagesManager
- separator removed - not needed
- unneeded imports removed
- bad refactoring fixed in comments and javadoc - pollConsumerMessages switched back to getMessages where it was needed
virtual attributes for getAttributes methods

getAttributes methods in impl layer now return also virtual attributes, javadoc for methods changed, usage of methods fixed
Merge pull request #390 from zlamalp/jdbc

CORE,REGISTRAR: changed SimpleJdbcTemplate to JdbcTemplate
Merge pull request #383 from Simcsa/auditer

AuditerConsumer moved to Auditer
Merge pull request #394 from Simcsa/attributes

virtual attributes for getAttributes methods
Add synchronizeGroup to nested transaction
New behavior for creating and calling auditerConsumer for LDAP

CORE,RPC,RPC-LIB:
- change behavior of method pollConsumerMessagesForParserLikePairWithId,
  return List<auditMessage> instead of List<Pair<String,Integer>>
- change name of methods pollConsumerMessages* to be more simple
- fix bug in Auditer.java (using bad variable lastProcessedId)
- add mehotd pollConsumerMessagesForParser to RPC-LIB
- remove AUDITER_LOG_MAPPER_FOR_PARSER_WITH_ID from Auditer (not needed now)

LDAPc:
- remove datasource from ldap (using rpc now)
- remove perun-ldapc-applicationcontext-jdbc.xml (not needed now)
- remove bad autowiring variable ldapcManager in LdapcStarter
- add @org.springframework.stereotype.Service to
  EventProcessorImpl
- use method pollConsumerMessagesForParser in LDAP EventProcessorImpl,
  reading messages by RPC through RPC-LIB

Tested on localhost
Merge pull request #395 from stavamichal/newCallingAuditerForLDAPFromRPC

New behavior for creating and calling auditerConsumer for LDAP
Merge pull request #384 from stavamichal/synchronizerInTransaction

Add synchronizeGroup to nested transaction
Fix delay of forcePropagation methods

forcePropagation methods uses audit message to notify engine about force
propagation request. Ussually, audit messages are stored to current
thread and waiting for commit of DB transaction; in this case there are
no queries in DB transaction, therefore the audit meessages are stuck
and waiting for commit of next DB transaction. (Not sure, where exactly
the messages are stuck).

This commit fix this behaviour by setting forcePropagation methods to
store audit messages to DB aside from DB transaction.

Details:
- create new method logWithoutTransaction
- storeMsgToDb method do not run in transaction
- call method logWithoutTransaction in forcePropagation methods

Original author: Michal Stava <stava.michal@gmail.com>
Modifications of decsriptions: Slavek Licehammer <slavek@ics.muni.cz>
Fixed type definition in JavaDoc.
RPC-LIB: check for response code before processing response

- We must check HTTP response code before processing response itself,
  since Apache can respond e.g. 503, and then HTML content is
  passed into JsonDeserializer and causes NullPointerException.

  If response code isn't HTTP_OK, then throw RpcException.
Merge pull request #397 from zlamalp/rpc-lib

RPC-LIB: check for response code before processing response