Open ThoSap opened 1 month ago
Don't you also need something like...
quarkus.rest.path=/bar/foo
quarkus.quinoa.ignored-path-prefixes=/q,/bar/foo/baz
Sorry I already had quarkus.rest.path
set to the following (I also updated the issue description above) and as the doc says for quarkus.quinoa.ignored-path-prefixes
, this property automatically ignores values configured by quarkus.resteasy-reactive.path
, quarkus.rest.path
, quarkus.resteasy.path
and quarkus.http.non-application-root-path
.
quarkus.rest.path=/api/v1
Maybe one addition which probably is the root cause of this issue, the REST endpoints, for example
/administration/api/v1/core/keycloak
/administration/api/v1/translations/en
are coming from a shared multi-module lib and are discovered automatically by the simplified bean discovery (dependency injection). https://quarkus.io/guides/cdi-reference
So I guess maybe these REST paths must be added to quarkus.quinoa.ignored-path-prefixes
(even though they should already be covered by quarkus.rest.path
?), but maybe that is something that Quinoa should handle out of the box?
Some Quarkus Gradle multi-module examples from the Quarkus integration tests: https://github.com/quarkusio/quarkus/tree/3.15.1/integration-tests/gradle/src/main/resources/basic-multi-module-project https://github.com/quarkusio/quarkus/tree/3.15.1/integration-tests/gradle/src/main/resources/basic-multi-module-project-test-setup https://github.com/quarkusio/quarkus/tree/3.15.1/integration-tests/gradle/src/main/resources/multi-module-named-injection
yeah you might have to tweak that ignored
values as thta is what the Angular Integration Tests here do...
Got it, I will try that. But is it normal that if this is not configured correctly, Quinoa infinitely blocks any REST API request?
Yes i am pretty sure if you look through the tickets here if both are mapped to the same address you need to distinguish them. That is how the integration tests are. In all my code I always set Quinoa at one path and REST API at another path. But I will let @ia3andy chime in he knows more about this stuff than me....
@ThoSap where did you end up on this?
I also experience that the dev server mode seems not to work. All request from the server application on port :4200 to the backend hang. When disabling the dev server, it seems to work find but then I don't have the "push" live reload anymore and gotta press F5 every time 🤷♂️
@HerrDerb can you put together a small reproducer?
Describe the bug
When the Quarkus
quarkus.http.non-application-root-path
is set relative toquarkus.http.root-path
, requests to the REST API endpoints lead to stuck backend requests when Quinoaquarkus.quinoa.ui-root-path
is unset or not set to anything different than/
(relative to thequarkus.http.root-path
, but then the dev server does not work at all). For example:So my endpoints are the following:
If I set the
quarkus.quinoa.ui-root-path
to something different, let's say /dummy, then the backend REST API requests work and the backend is not stuck, but I then cannot use the Quinoa dev server as the path is wrong for Angular. Alsoquarkus.quinoa.just-build
set totrue
fixes the error, but then I can no longer use the dev server advantages of Quinoa.This also happens with Quarkus version
3.14.4
.When I then stop the backend using
q
in the console, I get the following errors:Quinoa version
2.4.9
Quarkus version
3.15.1
Build / Runtime
Angular
Package Manager
PNPM
Steps to reproduce the behavior
Expected behavior
No response