API Controller Not Being Triggered in Oqtane Module

[kasif]

Issue: API Controller Not Being Triggered in Oqtane Module
Context:
I am developing a custom Oqtane module where a Razor component calls a client-side service, which should send a request to an API controller. The expected flow is:

1️⃣ Razor Component (Edit.razor) → Calls a method that invokes the client service.
2️⃣ Client Service (InvoiceService) → Sends an HTTP POST request to the API controller.
3️⃣ API Controller (InvoiceController) → Processes the request and performs necessary operations.

However, during debugging, I noticed that the flow never reaches the API controller. Instead, the execution bypasses the controller entirely and directly interacts with the repository layer.

Request for Guidance:
1- What could cause the API controller to be skipped entirely, with execution going straight to the repository?
2- Are there specific configurations required in Oqtane to ensure the client-side service correctly calls the API?
3- How can I confirm whether the HTTP request is being made, and if not, what might be blocking it?

i am using Oqtane Version: 5.1.2
Working on multimodule, all compiled finally into three dll (client,server,shared).

[mdmontesinos]

Is it possible that you are running Oqtane in Render Mode Static or with server side interactivity?

In that case, if you have an service implementation in both client and server, it will use the server one. That might be why it is bypassing the controller.

[sbwalker]

As @mdmontesinos mentioned above, please see the "Services" section in this blog: https://www.oqtane.org/blog/!/83/oqtane-developers-meeting-mar-2024 . Oqtane uses dependency injection to determine the most high performance method for components to interact with backend services. If you are running Static Blazor or Blazor Server then there is no need to incur the extra overhead of spinning up an HttpClient to make an HTTP call over the wire with serialization/deserialization of the data.