ComputerVision | You can find code to projects | Model View Controller library

Pls make sure that you have created a current type of cognitive service, I recommend you to create All Cognitive Services just as below:

You can follow this doc to create it(Multi-service resource).

I did some test on my side by this service and everything works for me as expected :

My local test image:

Result:

The Computer Vision Read API is Azure's latest OCR technology that handles large images and multi-page documents as inputs and extracts printed text in Dutch, English, French, German, Italian, Portuguese, and Spanish. It also includes support for handwritten OCR in English, digits, and currency symbols from images and multi-page PDF documents. It's optimized to extract text from text-heavy images and multi-page PDF documents with mixed languages. It supports detecting both printed and handwritten text in the same image or document (for English only).

Here is the doc for release update in computer vision.

You can use both hosts below to send request:

Use a project reference.

https://docs.microsoft.com/en-us/visualstudio/ide/managing-references-in-a-project?view=vs-2019

To test; create a new solution with two projects within it. Within one project, add a nuget package. Say, Newtonsoft.Json Add a project reference from your second project to the first

Dependencies should now look like so;

Now within TestConsoleApp, you can add using statements to access the nuget package used in TestConsoleApp2.

eg;

When we use the method read_in_stream, we need to provide a stream. But the code BytesIO.getvalue will return the content of the stream as string or bytes. So please update code as below

Set the Content-Type header of the POST request to "application/octet-stream" and add the image to the HTTP body:

There is indeed no request and reply channel options in Java DSL because you simply wrap that handle() into channel() configuration or just chain endpoints in the flow natural way and they are going to exchange messages using implicit direct channels in between. You can look into Java DSL IntegrationFlow as a in the XML configuration.

Your advice configuration is a bit wrong: you need declare your custom advice as a first in a chain, so when exception is thrown from there a retry one is going to handle it.

You should also consider to implement an AbstractRequestHandlerAdvice to align it with the RequestHandlerRetryAdvice logic.

You implement there a doInvoke(), call ExecutionCallback.execute() and analyze the result to return as is or throw a desired exception. A result of that call for HttpRequestExecutingMessageHandler is going to be an AbstractIntegrationMessageBuilder and probably a ResponseEntity as a payload to check for your further logic.

OK. I see where is the problem:

v12 sdk uses BlobServiceClient instead of BlockBlobService, if you want to use BlockBlobService should use v2 sdk. For v12 sdk usage, please refer to this official doc.

So please change it to from azure.storage.blob import BlobServiceClient, PublicAccess.