No, it’s not the same case with the @EventHandler and @EventSourcingHandler annotations.
The @EventSourcingHandler is by definition only used to source a model based on the events in your event store.
Currently, this is only allowed for the Command Model, aka the Aggregate, where the EventSourcingRepository fixes this functionality for you.
An @EventHandler is just a function which listens to a certain event with no sourcing capabilities behind it.
Additionally I don’t think we’ll deprecate the CommandGateway, since as Allard says it’s a convenience wrapper around a CommandBus; it’s thus not a duplicate implementation, as it uses the CommandBus, but adds a simplified interface for you.
Hope this helps.