[
https://issues.apache.org/jira/browse/CAMEL-17706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17497215#comment-17497215
]
Andrea Cosentino commented on CAMEL-17706:
------------------------------------------
It's not really standard to have a clientBuilder as endpoint option. You have
already the ability to inject a client in the camel registry and passing it in
the route. We could probably relax the requirements for connection string, but
having a clientBuilder as endpoint option is not a best practice. If you want
to use AzureAD authentication, you could do that by injecting an instance of
the client in the registry. There is still the problem of connection string
requirement and this is something we should look at.
If you have time to improve the component, we love contributions.
> Add ServiceBusClientBuilder to Azure ServiceBus component
> ---------------------------------------------------------
>
> Key: CAMEL-17706
> URL: https://issues.apache.org/jira/browse/CAMEL-17706
> Project: Camel
> Issue Type: New Feature
> Components: camel-azure
> Affects Versions: Future
> Reporter: MattV
> Priority: Minor
> Labels: azure, servicebus
> Fix For: 3.x
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Add the option to pass a ServiceBusClientBuilder to the azure-servicebus
> component as a uri parameter. The use case would be to use a custom builder
> to configure AzureAD authentication rather than using a connection string,
> and allow for configuration for more than one service bus namespace.
> Currently that configuration is cumbersome, needed to instantiate an async
> client for each queue to be sent to/received from. Passing a client builder
> to the endpoint uri would greatly simplify that configuration.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
