[maven-release-plugin] prepare release axon-2.0-m3
[maven-release-plugin] prepare for next development iteration
Typo in javadoc
Improved performance of visit-all-events query

By changing the way the batching is done by the query, performance is improved
dramatically, especially for the batches beyond the first million (selecting
1000 records after the first 1.000.000 took nearly 4 minutes, now 200ms)

Issue #AXON-57 Fixed
Removed deprecated classes

Preparing for the first release candidate. We don't want deprecated classes in
there.
Made AsyncAnnotatedSagaManager more robust against exceptions

Exceptions thrown by Saga handlers are now ignored, instead of propagated.
Propagation would result in the failure of the manager as a whole (reporting
exceptions in the log). Now, it logs the failure and continues processing the
other Sagas.
Fixed null-AssociationValue issue in AsyncAnnotationSagaManager

The SagaManager should not create a Saga instance if the association value
resolves to null. The AsyncAnnotationSagaManager did not check this, causing
NPE's further on. Now, the values are properly checked.
Fixed 'the fix' in the previous commit
Removed insight plugin from core codebase

This module is going to be picked up and maintained by VMWare.
Added some UoW cleaning in tests

Found another location where a UoW doesn't seem to be properly cleaned in
tests. This caused failures depending on the order in which tests were
executed.

Issue #AXON-60 Comment
Added Exception Handler to disruptor to prevent threads from crashing

When an exception occurs in the Disruptor, by default, that thread is
terminated. In the case of the AsyncAnnotatedSagaManager, this means that
processing of Events will ultimately stop.

Issue #AXON-58 Fixed
Removed unnecessary check from UnitOfWork

This check would cause events not to be published when an aggregate has a
hashCode implementation that changes during its lifecycle. Since aggregates
are stored in a HashMap, this will cause strange behavior.
[maven-release-plugin] prepare release axon-2.0-rc1
[maven-release-plugin] prepare for next development iteration
Added wrong identifier detection in test fixtures

When using the wrong identifier to load an aggregate in the Test Fixtures, Axon
will now throw an exception. This can occur when the command contains an
identifier that does not match the identifier used in the "given" events.

This also uncovered a problem in the LockingRepository, where the identifier
used to load an aggregate was used to obtain a lock, while that actual
identifier of the aggregate was used to release the lock. When identifiers
don't match, this would lead to exceptions and leakage of locks.

Issue #AXON-61 Fixed
Fixed typo
Support change of access style to message property in SagaMethodMessageHandler
Cleanup code

Remove introduced dependency of org.axonframework.common.annotation on org.axonframework.saga.annotation package
Add java docs
Add ability to use custom PropertyAccessors
Use PropertyAccessor to get/set properties values
Documentation update