Hi,
within axon 2.x I was creating command handlers as spring’s @Component. Now in axon 3.x this doesn’t work anymore.
What is the minimal configuration needed to register command handler with it’s repository?
I was trying this:
@Aggregate
public class AccessorAggregateRoot implements Serializable {
private static final long serialVersionUID = -6507215786865192829L;
@AggregateIdentifier
private AccessorId accessorId;
...
}
@Configuration
public class AccessorCommandConfiguration {
@Bean
Repository<AccessorAggregateRoot> accessorAggregateRootRepository(AxonConfiguration axonConfiguration) {
return axonConfiguration.repository(AccessorAggregateRoot.class);
}
}
@Component
public class AccessorCommandHandler implements IAggregateLoader<AccessorAggregateRoot, AccessorId> {
private Repository<AccessorAggregateRoot> accessorRepository;
private PasswordEncoder passwordEncoder;
@Autowired
public AccessorCommandHandler(
Repository<AccessorAggregateRoot> accessorAggregateRootRepository, PasswordEncoder passwordEncoder) {
this.accessorRepository = accessorAggregateRootRepository;
this.passwordEncoder = passwordEncoder;
}
}
but I’m getting the exception:
BeanCurrentlyInCreationException: Error creating bean with name ‘accessorAggregateRootRepository’: Requested bean is currently in creation: Is there an unresolvable circular reference?
If I remove the repository config from AccessorCommandConfiguration then it seems that repository is not configured, or maybe it’s configured after commandhandler
using Spring, if you want to customize the repository, simply define a repository bean, but don’t use the AxonConfiguration to get one. The issue here is that you’re asking the AxonConfiguration to provide a repository instance, but the configuration isn’t ready to provide one yet. Using Spring, it works the other way round (defining a repository will configure it with the configuration).
Anyway, the @Aggregate annotation allows you to configure the name of the repository bean to use to load that aggregate. If you don’t define one, then Axon will automatically create one (provided you use spring-boot-auto-configuration and have the axon-spring-boot-autoconfigure module included).
For what purpose are you trying to wire the Aggregate Repository?
Typical use case to wire an Aggregate Repository would be to be able to load or create Aggregate instances directly on it because you’ve got @CommandHandler annotated functions on a service.
If that’s the case however, I’d suggest setting the @CommandHandler annotations in your Aggregate class directly, is that introduce a simpler solution for you.
If you’re wiring the Repository to query the Aggregate it’s state and you’re doing Event Sourcing, then I’d also suggest against wiring it yourself.
In this case you’re mixing up the command and query side of your application, and as such I’d suggest introducing a dedicated query model which is based off of the events published from your Aggregates.
The above are mainly suggestions though, maybe you’ve got another entirely valid reason to wire the Repository somewhere.
So to ask a simpler question, from which part in your application does the @Autowired priver Repository<Account> accountRepository; line stem?
@CommandHandler
public void handle(SomeCommand cmd) {
…
}
}
I
`
Sometime I want to handle one command based on 2 aggregates,these 2 aggregate maybe aggregate and its member. And sometime,when I handle order command,I need to get some value of related product.
I know I can spit some command into 2, to avoid access 2 aggregates in one function. But if it is available, I think it will be convenient to do as above.
在 2018年5月30日星期三 UTC+8下午7:27:28，Steven van Beelen写道：
You’re response somehow slipped between the gaps of other work…
Any how, back to your issue.
I’ve been able to reproduce your scenario; thus, not being able to wire an aggregate Repository as a bean in my own Components/Services.
The Spring (Boot) configuration code in Axon showed me that we’re currently not exposing the Repository as a bean in the ApplicationContext.
To resolve this, I’ve created the following issue.
That issue describes the idea we have to resolve this, so that framework-users like yourself can wire the automatically created aggregate Repository.
For now however, you’ll need a work around of course.
I suggest to instantiate the aggregate Repository yourself in your application and annotating it with @Bean.
Doing so will surely allow you to wire the Repositories you need in your other components.
If you’ve got time to wait though, you could track issue #620 for the progress.
I assume we’ll introduce it in release 3.3, which we’re planning to release this week.
