[GitHub] [camel-k] edeandrea edited a comment on issue #1870: camel.component.* properties not being respected under Quarkus runtime

[GitBox <gi...@apache.org>]

edeandrea edited a comment on issue #1870:
URL: https://github.com/apache/camel-k/issues/1870#issuecomment-758105245


   @lburgazzoli another question here though - is there a particular reason that the `hotrod-client.properties` file is not picked up by camel-k?
   
   In my sample (https://gist.github.com/edeandrea/770c84be9da204ff0b13f2340975904e) I would assume that the properties I have defined in the [`hotrod-client.properties`](https://gist.github.com/edeandrea/770c84be9da204ff0b13f2340975904e#file-camelk-client-yml-L34-L45) and are [mounted into the `Integration`](https://gist.github.com/edeandrea/770c84be9da204ff0b13f2340975904e#file-camelk-client-yml-L56-L57) would be picked up by the `camel:infinispan` component, but they are not.
   
   I know this because my `hotrod-client.properties` file defines `infinispan.client.hotrod.marshaller=org.infinispan.commons.marshall.UTF8StringMarshaller`. When I run my integration and look into the Infinispan cache, the keys/values that are there aren't simple strings - they're serialized using class serialization.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org