Weird CORS bug when pressing "fights" about quarkus-super-heroes HOT 10 CLOSED

When you launched fights, did you use -Dquarkus.profile=no-microcks (see https://github.com/quarkusio/quarkus-super-heroes/tree/main/rest-fights#integration-with-microcks)?

By default if you just to ./mvnw quarkus:dev on rest-fights, it will not talk to heroes/villains and will serve "canned" responses.

from quarkus-super-heroes.

When you launched fights, did you use -Dquarkus.profile=no-microcks (see https://github.com/quarkusio/quarkus-super-heroes/tree/main/rest-fights#integration-with-microcks)?

By default if you just to ./mvnw quarkus:dev on rest-fights, it will not talk to heroes/villains and will serve "canned" responses.

Very fast response Eric, wow!

I tried that, works the same, but the UI just points to the microcks endpoint. Maybe I need to change the UI endpoint and do a research in the READMEs before doing some testing.

It's not the topic of this issue, but... any video or tutorial for the Super Heroes repo?

Thanks!

from quarkus-super-heroes.

I just started all the apps manually

• In grpc-locations: ./mvnw clean quarkus:dev
• In rest-villains: ./mvnw clean quarkus:dev
• In rest-heroes: ./mvnw clean quarkus:dev
• In rest-fights: ./mvnw clean quarkus:dev -Dquarkus.profile=no-microcks
• In ui-super-heroes: ./mvnw clean quarkus:dev -Dquarkus.profile=no-microcks

And when I bring up the UI (http://localhost:8080) everything seems to work fine. No CORS issues.

Can you tell me a little bit more about how you are running the UI? Are you doing a docker run? Or are you starting via ./mvnw quarkus:dev?

It's not the topic of this issue, but... any video or tutorial for the Super Heroes repo?

There are a few resources...

• https://youtube.com/live/W_QREL1nEGI
• https://youtu.be/H9yK0xnExeA
• https://youtu.be/7M0Tvlx-GTA
• https://quarkus.io/blog/quarkus-superheroes-to-the-rescue/

There is also the repo's main README file, as well as the README files of all the individual applications.

from quarkus-super-heroes.

Actually you know what - when I start up the UI with just ./mvnw clean quarkus:dev and when I do a FIGHT, I do see the CORS issue...

I've created microcks/microcks-quarkus#22 for some guidance.

from quarkus-super-heroes.

I just started all the apps manually

• In grpc-locations: ./mvnw clean quarkus:dev
• In rest-villains: ./mvnw clean quarkus:dev
• In rest-heroes: ./mvnw clean quarkus:dev
• In rest-fights: ./mvnw clean quarkus:dev -Dquarkus.profile=no-microcks
• In ui-super-heroes: ./mvnw clean quarkus:dev -Dquarkus.profile=no-microcks

And when I bring up the UI (http://localhost:8080) everything seems to work fine. No CORS issues.

Can you tell me a little bit more about how you are running the UI? Are you doing a docker run? Or are you starting via ./mvnw quarkus:dev?

It's not the topic of this issue, but... any video or tutorial for the Super Heroes repo?

There are a few resources...

• https://youtube.com/live/W_QREL1nEGI
• https://youtu.be/H9yK0xnExeA
• https://youtu.be/7M0Tvlx-GTA
• https://quarkus.io/blog/quarkus-superheroes-to-the-rescue/

There is also the repo's main README file, as well as the README files of all the individual applications.

Just missed the -Dquarkus.profile=no-microcks parameter on ui-super-heroes and rest-fights. Now works perfectly. No cors problem and #686 problem disappear. Does the order of execution matter?

Maybe too much desire on running quarkus perfectly without reading READMEs 🤣

(I need to check grpc-locations, I know)

from quarkus-super-heroes.

Does the order of execution matter?

No it doesn't.

from quarkus-super-heroes.

Actually you know what - when I start up the UI with just ./mvnw clean quarkus:dev and when I do a FIGHT, I do see the CORS issue...

I've created microcks/microcks-quarkus#22 for some guidance.

from quarkus-super-heroes.

Actually you know what - when I start up the UI with just ./mvnw clean quarkus:dev and when I do a FIGHT, I do see the CORS issue...

I've created microcks/microcks-quarkus#22 for some guidance.

Great! I'm going to continue without microcks for the moment.

If you wanna close or continue this issue, your choice. Thanks!

from quarkus-super-heroes.

I'll keep it open for now until I get feedback on the issue I created in microcks.

from quarkus-super-heroes.

@psirdev FYI the issue has been fixed by microcks/microcks-quarkus#22

from quarkus-super-heroes.