FoodCart | This project was generated with Angular CLI version | Generator Utils library

Answer

The reason for that is likely how the SpringBeanParameterResolverFactory and it's SpringBeanParameterResolver are used to retrieve Spring beans to inject in message handling functions.

At the moment a message handling function like your @CommandHandler public void handle(DeselectProductCommand ...) is called. The SpringBeanParameterResolver#resolveParameterValue method will be called, which in turn calls the AutowireCapableBeanFactory#getBean(String). As you might have noticed there, it doesn't use any notion of an InjectionPoint.

Implementing this wouldn't be hard I believe. The AutowireCapableBeanFactory#resolveDependency(DependencyDescriptor, String) method would be sufficient at a quick glance (DependencyDescriptor is an implementation of InjectionPoint). Might be worth providing an issue on Axon's GitHub for this, or even better, a PR.

Suggestions

However, I do have another suggestion to achieve the same non-functional requirement of logging without injecting it in every message handling function. To achieve this form of logging in an Axon application, you can go two ways:

1. Use MessageHandlerInterceptors and MessageDispatchInterceptors which log upon ingestion and handling of any message. Quick solution would be to use Axon's LoggingInterceptor for this, which implements both interfaces. From there, you would register it to every message dispatching and handling component (thus the CommandBus, EventBus, all EventProcessors and the QueryBus).
2. Provide a HandlerEnhancerDefintion which wraps every message handling function with your logging logic. Providing a Bean for this should be sufficient for Axon to pick it up and automatically wrap all @MessageHandler annotated methods.

Doing either of these means you are not obstructing the logic of handling commands, events and queries, with the rather dull logic of logging.

That's my two cents, hope it helps Andre!