Do not produce Infinispan RemoteCacheManager if no Infinispan configuration is present

[ppalaga]

We depend on quarkus-infinispan-client in camel-quarkus-infinispan. Camel offers some alternative ways to configure Infinispan client, e.g. users can pass the list of hosts through the Camel route definition - see apache/camel-quarkus#2344 (comment) . If the user does not provide any quarkus.infinispan.* config in application.properties, starting the application fails, because quarkus-infinispan-client still produces an improperly configured RemoteCacheManager. Thus we'd appreciate if the producer methods in InfinispanClientProducer could please return null if no quarkus.infinispan.* config was provided by the end user.

cc @jamesnetherton

[quarkus-bot]

/cc @gwenneg, @karesti, @wburns

[karesti]

we are working now on the extension, I will create a JIRA to address this issue

[karesti]

https://issues.redhat.com/browse/ISPN-13137

[karesti]

@ppalaga would this make the trick? I also upgraded to 12.1.5.Final but it has not landed in central yet
karesti@3a65b18

[jamesnetherton]

Peter is on PTO, but it looks ok to me.

I can try to test it with camel-quarkus when 12.1.5.Final shows up in central.

[jamesnetherton]

I tested and it didn't quite work. The problem is in InfinispanClientProducer.initialize(). It seems properties is not null and contains some values that I assume the extension set at build time?

• infinispan.client.hotrod.protofile.org/infinispan/protostream/message-wrapping.proto
• infinispan.client.hotrod.marshaller
• infinispan.client.hotrod.protofile.org/infinispan/query/remote/client/query.proto

Maybe because the camel component has this dependency.

[karesti]

@jamesnetherton sorry I missed this comment before.