AXON-199 Update Disruptor dependency

Updated Disruptor dependency from com.googlecode.disruptor:disruptor:2.10.3 to
   com.lmax:disruptor:3.2.0.
Removed use of ClaimStrategy, SingleThreadedClaimStrategy, and MultiThreadedClaimStrategy
   and replaced them with single-threaded and multi-threaded ProducerType.
Removed claimStrategy from DisruptorConfiguration and replaced with bufferSize and
   producerType.
Removed parseClaimStrategy method from DisruptorCommandBusBeanDefinition and replaced
   with parseProducerType method.
Replaced ClaimStrategyFactoryBean with ProducerTypeFactoryBean.
AXON-199 Update Disruptor dependency

Added claim-strategy back to axon-core-2.1.xsd and documented as deprecated.
Added parseClaimStrategy method back to DisruptorCommandBusBeanDefinition and marked as deprecated.
Fixed payload verification issue in "expectStoredEvents"

The expected value (payload) is compared with the EventMessage of the message
actually stored, causing it to always fail.

Issue #AXON-201 Fixed
Added ability to attach resources to a Unit of Work

This feature will be used in upcoming versions to manage resources used by
building block implementations, such as JPA Event Store or AMQPTerminal to
ensure the same resource can be used during the processing of a Unit of Work.
This prevents the waste of creating new resources several times.

Issue #AXON-200 Fixed
Allow event-entry-store attribute in axon namespace support for
JpaEventStore. See detail in
http://issues.axonframework.org/youtrack/issue/AXON-202#tab=Comments
Add EventEntryStore attribute test for JpaEventStore axon namespace.
Added EventProcessingMonitor mechanism

This mechanism allows for components to take action when Event processing has
finished (either successfully or by failure).

Issue #AXON-193 Fixed
Fixed issue where some aggregate would not be correctly created

This would occur when two sagas of different types, managed by the same
saga manager and triggered by the same association value are created at the
same time.

Issue #AXON-204 Fixed
Fixed issue where command callback is not notified of a missing handler

Sending an unroutable message on the SimpleCommandBus would throw an exception,
but would not notify the callback, as defined by the interface. In certain
configurations, this could lead to silent errors.

Issue #AXON-203 Fixed
Increased timeout on a test to allow slower machines to pass the test
Reverted to default to the ClasspathParameterResolverFactory.

All components allow a custom ParameterResolverFactory to be configured. B
default, the ClasspathParameterResolverFactory is used, which is configured
to use the class loader of the class to resolve parameters for.

Spring beans can no longer be injected into the Event Handlers of aggregates.
Although it seems a limitation, it can be seen as a bad practice to require
any type of resources in event sourcing handlers.

Issue #AXON-123 Fixed
Merge branch 'master' of git://github.com/Hippoom/AxonFramework
OSGi: unit tests
OSGi unit tests
Merge branch 'master' of git://github.com/jcraigbrown/AxonFramework

Issue #AXON-199 Fixed
Removed reference to Java 7 method
Merge branch 'master' of git://github.com/lburgazzoli/AxonFramework
Moved OSGi tests to integration tests module

Issue #AXON-179 Comment
Updated dependencies and improved OSGi integration test
Added Spring configuration support for AMQP publisher ack

Issue #AXON-113 Comment