When handling command we a getting alot of the following log messages
WARN org.axonframework.unitofwork.DefaultUnitOfWork An aggregate is
being registered with this UnitOfWork more than once. Although this is
not likely to cause problems, it is improper use of resources.
After looking at the code is appears that the we are loading aggregate
more than once in the processing of a command. Is order to reduce hit
to the database I was considereing using the caching respositories.
Unfortunately there is no SpringPrototypeCachingRepository so I will
probably roll my own.
My question is should axon provide a caching capability within the
UnitOfWork. This would be similar to the hibernate Session level
caching. I see the Caching repository implementations as a second
level caching mechanism.