Hi Dirk,
Firstly, it's custom to use the `@EventSourcingHandler` annotation for event handling functions in the Aggregate. The `@EventHandler` annotation is generally used for other event listeners.
Second: What do you mean exactly with events which were created outside the aggregate?
Do you mean events which were never applied within an aggregate, or events which were applied by another aggregate?
Either way, it should not be necessary to handle events within that aggregate which aren't meant for that aggregate.
If you want to handle events outside the aggregate to update the query side of your application however, you could in, for example a Spring app, have a bean with `@EventHandler` annotated functions.
If you're using the auto-config set up of Axon 3, it should automatically pick up that bean as a event handling bean, making it so that the events which are applied in an aggregate can also be event handled by that bean.
Hope this helps!
Cheers,
Steven