Details
-
Bug
-
Resolution: Done
-
Blocker
-
Camel-K-GA, camel-quarkus-2.2-GA
-
None
-
False
-
False
-
%
-
Todo
-
Undefined
Description
Camel Quarkus generates an exception when using the salesforce camel component.
This is raised as a result of testing for ENTESB-16422. Using camel-k initially generated the error but that layer can be removed and the error repeated in a locally executed camel-quarkus java project, eg. here.
A look at the debug traces indicates that the camel salesforce component is wired up using the camel BaseMainSupport class.
This though calls the doBuild() method of the SalesforceComponent and sets up its delegate SalesforceLogin instance ... but with no properties.
Then it uses PropertyBindSupport to set the properties obtained from the .properties files on the component itself BUT not the SalesforceLogin instance.
Consequently, once the session is initialised, it is the properties of SalesforceLogin that are used rather than the component's hence the empty properties and the error being thrown.
This may appear a camel component problem and it may still be the case that a fix is required at that level. However, it is apparent that this is not an issue with Springboot implementations using this component. Does that mean that camel-quarkus needs to wire up properties from application.properties / secrets differently for these doBuild() components?
Attachments
Issue Links
- blocks
-
ENTESB-16422 Camel-k-example-saas: loginUrl must be specified with 1.4.0
- Done
- causes
-
ENTESB-16422 Camel-k-example-saas: loginUrl must be specified with 1.4.0
- Done
- is duplicated by
-
CEQ-1925 SalesforceComponent generates "loginUrl must be specified" error
- Closed
-
ENTESB-16770 Salesforce fails to start because loginUrl configuration is ignored
- Closed