Javadoc and code style improvements
Fixed issue with Saga activity while that Saga was being created

This fixes an issue where Saga that dispatch events from their @StartSaga
handler which may result in activity in that same Saga instance.

Issue #AXON-194 Fixed
Added index to ensure replays on larger collections

Ensuring additional index on the event collection to allow replays on mongo event stores.

Issue #AXON-195 Fixed
DisruptorCommandBus will only log errors when dispatching without callback

Instead of defaulting to the LoggingCallback, the DisruptorCommandBus will log
only errors, on the info level.
Added transactionManager to AbstractSnapshotter

This allows non-spring applications to configure a transaction manager that
wraps the snapshot creation process in a transaction.

Issue #AXON-197 Fixed
Added support for reading partial event streams

The EventStore can optionally implement PartialStreamSupport, which allows
clients to read a predefined portion of events, regardless of the availability
of snapshot events.

Issue #AXON-156 Fixed
CachingEventSourcingRepository no longer needs to reload on version conflict

The CachingEventSourcingRepository would force a full reload of an aggregate
when the actual version did not match the expected version. Now, it will use
the cached aggregate, and load the "unseen" events from the event store, if the
event store implements the PartialEventStreamSupport interface. Otherwise,
behavior is unchanged.

Issue #AXON-150 Fixed
Created ListenerAdapter implementation that allows modification of Meta Data

This adapter implementation allows adding meta data to an Event during the
beforeCommit phase of the Unit of Work. It works around the immutability of
events, which is restored immediately after the modifications.

Issue #AXON-161 Fixed
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.
Changed default event handler annotation for aggregates to @EventSourcingHandler

For backwards compatibility, the @EventHandler annotation is still supported.
This support will be removed in Axon 3.

Issue #AXON-175 Fixed
Issue #AXON-175 Documented
Changed Cache API to javax.cache.Cache

The jsr107 API has been moved to javax.cache. Currently, Axon supports the 0.5
version of the specification, which has been implemented by the (at this
moment) latest EhCache-JCache implementation (being 1.5.0-0.5).

Future releases of Axon will upgrade the API when an implementation for that
API version is available.

A warning/explanation has been put in the reference guide.

Issue #AXON-81 Fixed
Issue #AXON-81 Documented
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 Java code to use ‘<‘ instead of ‘>’
Use createCopy(), otherwise an exception will be thrown.

The Dom4J element returned by element(“address”) still has its original
parent set. Adding this element to another node results in an
IllegalAddException. See Dom4Js Branch#add(Element element) JavaDocs.
The createCopy() method just copies the element without its parent and
therefore can be used to move elements betweens different trees.
Merge pull request #104 from sebhoss/upcaster-doc

Small fixes for the upcaster documentation
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