bvahdat commented on issue #4278:
URL: https://github.com/apache/camel-quarkus/issues/4278#issuecomment-1318528826
> yeah, it is happening in the camel. Please see
https://camel.apache.org/components/3.18.x/jms-component.html#_component_option_allowAutoWiredConnectionFactory
Thanks, i
bvahdat commented on issue #4278:
URL: https://github.com/apache/camel-quarkus/issues/4278#issuecomment-1318480470
Thanks @zhfeng that did the trick!
>The `autowired` property is not set on the `connectionFactory` property of
`JmsConnectionFactory`, so wondering why it works in the fi
bvahdat commented on issue #4278:
URL: https://github.com/apache/camel-quarkus/issues/4278#issuecomment-1318407514
Trying out this approach introduces a regression not clear to me, as
auto-wiring of
https://github.com/messaginghub/pooled-jms/blob/main/pooled-jms/src/main/java/org/mes
bvahdat commented on issue #4278:
URL: https://github.com/apache/camel-quarkus/issues/4278#issuecomment-131718
Thanks @jamesnetherton that's actually what I have already tried out which
solves the Camel version conflicts we have run into after the upgrade, but the
problem is that there
bvahdat commented on issue #4278:
URL: https://github.com/apache/camel-quarkus/issues/4278#issuecomment-1316959133
If I would make use of Quarkus `2.13.3.Final` together with
`camel-quarkus:2.13.1` as per VOTE statement I have seen above, then I would
get conflicting camel versions, causing
