Camel 4.7 - Reflection in jms and sql component about camel-quarkus

[jamesnetherton]

Ah, maybe we can consider to add ActiveMQConnectionFactory reflection configuration in quarkus-artemis extension?

Can we not just use Jandex and discover all impls of ConnectionFactory & DataSource?

[zhfeng]

@davsclaus How about if ActiveMQConnectionFactory is wrapped by such JMSPoolConnectionFactory provided by quarkus-pooled-jms ?

[oscerd]

@davsclaus How about if ActiveMQConnectionFactory is wrapped by such JMSPoolConnectionFactory provided by quarkus-pooled-jms ?

We should not use runtime specific dependency where possible.

[zhfeng]

OK, so for camel-jms we could only add jakarta.jms.ConnectionFactory to the reflection configuration in native mode. And for camel-sql adding javax.sql.DataSource?

Then if using with quarkus-pooled-jms, there might be an issue to get brokerUrl?

[zhfeng]

Ah, maybe we can consider to add ActiveMQConnectionFactory reflection configuration in quarkus-artemis extension?

[zhfeng]

@jamesnetherton well, it looks like quarkus-artemis-jms has not included jandex yet.

[jamesnetherton]

I don't think this can work OOTB. The problem is that the ConnectionFactory and DataSource are synthetic ClientProxy beans. When you do reflection on them, the methods that get returned are those of the generated proxy and not the actual target type.

We could maybe investigate doing ClientProxy.unwrap before beans get returned from RuntimeBeanRepository.