[ 
https://issues.apache.org/jira/browse/CAMEL-21735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17926052#comment-17926052
 ] 

Luis Sergio Faria Carneiro commented on CAMEL-21735:
----------------------------------------------------

Yes, that's specific to camel-quarkus. Running the code with jbang, for 
example, works.

One other point that I noticed is that even if I set autowiredEnabled to false 
in the parameters, I still see the default client being injected into the 
component:
{code:java}
2025-02-11 16:15:51,895 INFO  [org.apa.cam.sup.LifecycleStrategySupport] (main) 
Autowired property: mongoConnection on component: mongodb as exactly one 
instance of type: com.mongodb.client.MongoClient 
(com.mongodb.client.MongoClient_h1_G0-d2ADp3y2Tmh2-WKjUlre0_Synthetic_ClientProxy)
 found in the registry{code}
 

 

> 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)

Reply via email to