[
https://issues.apache.org/jira/browse/CAMEL-21735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17926356#comment-17926356
]
Pasquale Congiusti commented on CAMEL-21735:
--------------------------------------------
I think the best thing would be to open an issue directly on Camel Quarkus
Github page and contribute to the feature if there is no other reason not to do
this. I recall we were very dependent on the Quarkus MondoDB dependency a few
years back, not sure if the things are different now.
> MongoDB component connecting to localhost event if connection data is set
> -------------------------------------------------------------------------
>
> Key: CAMEL-21735
> URL: https://issues.apache.org/jira/browse/CAMEL-21735
> Project: Camel
> Issue Type: Bug
> Components: camel-mongodb
> Affects Versions: 4.8.0
> Reporter: Luis Sergio Faria Carneiro
> Priority: Major
>
> I'm trying to use the MongoDB component within a Camel K integration. And the
> code is as following:
> {code:java}
> - to:
> uri: mongodb:dummy
> parameters:
> operation: findAll
> collection: environment
> database: environments
> username: someuser
> password: somepass
> hosts: somehost:27017{code}
> Although the connection parameters are set, I see component trying to connect
> to 127.0.0.1:27017.
> Debugging the source code and checking the log, I see the component is using
> an autowired client which is configured to localhost instead of creating a
> new client from my parameters.
> I haven't configured any beans.
> But anyways, shoudn't the endpoint parameters take precedence over any
> pre-configured bean which I'm not even aware of?
>
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
