Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Link to GitHub repo and remove mutiny #213

Merged
merged 2 commits into from
Nov 21, 2023
Merged

Link to GitHub repo and remove mutiny #213

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c04ba86
add solution link for github repo
christofluethi Nov 21, 2023
3b6782f
remove mutiny extension as it has a transitive dependency to classic …
christofluethi Nov 21, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions content/en/docs/01.0/12_quarkus.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ integration, RESTeasy-JAX-RS, dev mode and many more features.

Quarkus provides a list of extensions and frameworks which can be included into
your Quarkus project. Extensions (Hibernate ORM, Liquibase, Flyway, SmallRye
Reactive Messageing, and many others) are minified and customized to work with
Reactive Messaging, and many others) are minified and customized to work with
the minimal resource consuming framework.

Due to the optimization of extensions and the framework itself, Quarkus can be
Expand Down Expand Up @@ -74,7 +74,7 @@ be used again.

In summary:

* Too much classes beeing loaded
* Too much classes being loaded
* Too much metadata processing for annotations, cdi, reflection, proxies, ...

This is where Quarkus does things differently. It moves everything possible to the build-time phase instead of run-time
Expand Down
2 changes: 1 addition & 1 deletion content/en/docs/01.0/18_solutions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ description: >
Solution code for the Quarkus Techlabs
---

We have provided solution code for the labs in the folder `solution` of this `quarkus-techlab` project.
We have provided solution code for the labs in the folder `solution` of this `quarkus-techlab` project. You can find the source code of the `quarkus-techlab` on [GitHub]({{% param "github_repo" %}})

{{% alert color="warning" %}}
Be aware that in some solution projects like `quarkus-rest-data-producer` you'll find the solution code for multiple labs.
Expand Down
4 changes: 2 additions & 2 deletions content/en/docs/02.0/25_reactive-programming.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -382,13 +382,13 @@ curl -X POST localhost:8080/data -d "{\"data\":0.1, \"time\":\"2022-01-01T00:00:

We have learned how to implement a reactive REST API to serve data in a complete reactive non-blocking way. Now it's time to take a look at the opposite, how do we reactively consume the API.

Create another Quarkus project with the following extensions: `quarkus-resteasy-reactive-jackson`, `quarkus-rest-client-reactive-jackson`, `quarkus-resteasy-mutiny`:
Create another Quarkus project with the following extensions: `quarkus-resteasy-reactive-jackson`, `quarkus-rest-client-reactive-jackson`:

```bash
mvn io.quarkus:quarkus-maven-plugin:{{% param "quarkusVersion" %}}:create \
-DprojectGroupId=ch.puzzle \
-DprojectArtifactId=quarkus-reactive-rest-consumer \
-Dextensions="quarkus-resteasy-reactive-jackson,quarkus-rest-client-jackson,quarkus-resteasy-mutiny" \
-Dextensions="quarkus-resteasy-reactive-jackson,quarkus-rest-client-reactive-jackson" \
-DprojectVersion=1.0.0 \
-DclassName="ch.puzzle.quarkustechlab.reactiverest.consumer.boundary.DataResource"
```
Expand Down