Support for ObjectProvider<T> from Spring

[chirdeeptomar]

Description

I have the following Spring bean that use ObjectProvider in one of the gradle modules, I have Quarkus as the web layer. Quarkus is unable to resolve ObjectProvider dependency. I have set up beans.xml, everything works until I add the AppConfig as below.

@Configuration
public class AppConfig {

    @Bean
    public Customer customer(ObjectProvider<CustomerBuilder> builder) {
        return new Customer();
    }
}

CustomerBuilder.java

@Component
public class CustomerBuilder {
}

Quarkus Graphql module

@GraphQLApi
public class ExampleResource {
    @Inject
    TestService service;

    @Query("allFilms")
    @Description("Get all Films from a galaxy far far away")
    public boolean getAllFilms() {
        return service.test();
    }
}

Error

`Caused by: javax.enterprise.inject.UnsatisfiedResolutionException: Unsatisfied dependency for type org.springframework.beans.factory.ObjectProvider<com.exa mple.demo.CustomerBuilder> and qualifiers [@Default]

• java member: com.example.demo.config.AppConfig#customer()
• declared on PRODUCER METHOD bean [types=[com.example.demo.Customer, java.lang.Object], qualifiers=[@Named(value = "customer"), @Default, @Any], t arget=com.example.demo.Customer customer(org.springframework.beans.factory.ObjectProvider builder), declaringBean=com.exa mple.demo.config.AppConfig] at io.quarkus.arc.processor.Beans.resolveInjectionPoint(Beans.java:487) at io.quarkus.arc.processor.BeanInfo.init(BeanInfo.java:362) at io.quarkus.arc.processor.BeanDeployment.init(BeanDeployment.java:226) ... 14 more `

[quarkusbot]

/cc @geoand

[vietk]

Quarkus Spring DI support merely transforms Spring annotations into CDI annotations, here it's more about providing an alternative implementation of Spring DI itself, which can be tedious if you one want to fill all the gaps.

Maybe you have to consider switching to CDI for some part of your code, i.e: mixing CDI and SpringDI code ?

[rmarting]

Same issue if the original Spring application code uses ObjectFactory:

@Configuration
public class KafkaConfig {
    @Bean
    public Producer<String, Message> createProducer() { /* Config stuff */}
}

And in my @Service class:

@Service
public class MessageService {

    private ObjectFactory<Producer<String, Message>> producer;

    public MessageService(ObjectFactory<Producer<String, Message>> producer) {
        this.producer = producer;
    }
}

Error stack trace:

Caused by: javax.enterprise.inject.UnsatisfiedResolutionException: Unsatisfied dependency for type org.springframework.beans.factory.ObjectFactory<org.apache.kafka.clients.producer.Producer<java.lang.String, com.rmarting.kafka.schema.avro.Message>> and qualifiers [@Default]
    - java member: com.rmarting.kafka.service.MessageService#<init>()
    - declared on CLASS bean [types=[com.rmarting.kafka.service.MessageService, java.lang.Object], qualifiers=[@Named(value = "messageService"), @Default, @Any], target=com.rmarting.kafka.service.MessageService]
    at io.quarkus.arc.processor.Beans.resolveInjectionPoint(Beans.java:504)

In both cases, should we refactor these definitions using CDI instead of Spring DI? Is there any plan to cover these Spring feature?

[geoand]

Hi,

We could most likely offer support for this. If enough people ask, we'll put the effort into it :)