If I understood you correctly, you want to use different implementations of ServiceActivator in various projects or have the ability to override the behavior of the default MyServiceActivator provided by your library.
Messing up with the same bean names or using @ConditionalOnMissingBean for this case may not be the most straightforward solution. And it also doesn't look good from the architectural point of view.
One possible solution would be introducing a common interface for these two classes, but this would, in return, require the unifying of parameters for the handleApplicationEvent method:
public interface ServiceActivator {
void handleApplicationEvent(String header, Object object);
}
@Component
public class MyServiceActivator implements ServiceActivator {
@Override
@ServiceActivator(inputChannel = "SomeChannel")
public void handleApplicationEvent(@Header("SomeHeader") String header, @Payload Object object) {
// ...
}
}
@Component
public class ChildServiceActivator implements ServiceActivator {
@Override
@ServiceActivator(inputChannel = "SomeChannel")
public void handleApplicationEvent(@Header("SomeHeader") String header, @Payload Object object) {
// Do something else
}
}
With such an approach, you would be able to benefit from using @Qualifier during the auto wiring:
@Autowired
@Qualifier("childServiceActivator")
private ServiceActivator childServiceActivator;
Besides that, you would be able to define the primary bean in your configuration:
@Configuration
public class ServiceActivatorConfig {
@Bean
@Primary
public ServiceActivator serviceActivator() {
return new ChildServiceActivator();
}
}
Another possible solution is to move the bean initialization to a separate configuration file in your library project instead of putting @Component on MyServiceActivator, which you would be able to import or exclude based on your needs.
Also, you maybe have considered it, but it might be worth mentioning the third option for this case – using @ConditionalOnProperty and enabling your beans based on the property value. From my point of view, it might be the optimal solution for your case, since it won't require any changes to the method signature.
@ConditionalOnProperty(value = "service-activator.provider", havingValue = "my")
@Component(value = "myServiceActivator")
public class MyServiceActivator {
@Override
@ServiceActivator(inputChannel = "SomeChannel")
public void handleApplicationEvent(@Payload Object object) {
// ...
}
}
@ConditionalOnProperty(value = "service-activator.provider", havingValue = "child")
@Component(value = "myServiceActivator")
public class ChildServiceActivator {
@Override
@ServiceActivator(inputChannel = "SomeChannel")
public void handleApplicationEvent(@Header("SomeHeader") String header, @Payload Object object) {
// Do something else
}
}
