[
https://issues.apache.org/jira/browse/CAMEL-14912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17083933#comment-17083933
]
Omar Al-Safi commented on CAMEL-14912:
--------------------------------------
Ahh I see what you mean, it looks like at some instances it forces the URI
validation although you have a client injected which is not needed. What you
mean to send a PR for the fix?
By the way, in case you are still testing, we added a new component that uses
the new v12 azure sdk, you can take a look at here:
https://github.com/apache/camel/blob/master/components/camel-azure-storage-blob/src/main/docs/azure-storage-blob-component.adoc.
Please take a look at it as need feedback on it
> Azure components should allow custom service URIs
> -------------------------------------------------
>
> Key: CAMEL-14912
> URL: https://issues.apache.org/jira/browse/CAMEL-14912
> Project: Camel
> Issue Type: Improvement
> Reporter: James Netherton
> Priority: Minor
>
> If you provide custom blob or queue clients to the Azure components, it seems
> you're forced to configure a service URI for either {{blob.core.windows.net}}
> or {{queue.core.windows.net}} This is validated in
> {{QueueServiceUtil.prepareStorageQueueUri}} &
> {{BlobServiceUtil.prepareStorageBlobUri}}.
> This prohibits testing with the Azure storage emulator where you'd configure
> a custom client with a URI that likely points at localhost.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
