Skip to content

Commit

Permalink
Apply suggestions from code review
Browse files Browse the repository at this point in the history 
Co-authored-by: Ladislav Thon <ladicek@gmail.com>
  • Loading branch information
@MichalMaler @Ladicek
MichalMaler and Ladicek authored Jul 26, 2023
1 parent 6607836 commit f4578c9
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/src/main/asciidoc/logging.adoc
View file
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ You can use any of the <<logging-apis,following APIs>>:
[[jboss-logging]]
== Use JBoss Logging for application logging

Check warning on line 26 in docs/src/main/asciidoc/logging.adoc

View workflow job for this annotation

GitHub Actions / Linting with Vale 

[vale] reported by reviewdog 🐶
[Quarkus.Headings] Use sentence-style capitalization in 'Use JBoss Logging for application logging'.

Raw Output:
{"message": "[Quarkus.Headings] Use sentence-style capitalization in 'Use JBoss Logging for application logging'.", "location": {"path": "docs/src/main/asciidoc/logging.adoc", "range": {"start": {"line": 26, "column": 4}}}, "severity": "INFO"}

Check warning on line 26 in docs/src/main/asciidoc/logging.adoc

View workflow job for this annotation

GitHub Actions / Linting with Vale 

[vale] reported by reviewdog 🐶
[Quarkus.CaseSensitiveTerms] Use 'JBoss EAP' rather than 'JBoss'.

Raw Output:
{"message": "[Quarkus.CaseSensitiveTerms] Use 'JBoss EAP' rather than 'JBoss'.", "location": {"path": "docs/src/main/asciidoc/logging.adoc", "range": {"start": {"line": 26, "column": 8}}}, "severity": "INFO"}

Using the JBoss Logging API, your application requires no additional dependencies, as Quarkus automatically provides it.
When using the JBoss Logging API, your application requires no additional dependencies, as Quarkus automatically provides it.

Check warning on line 28 in docs/src/main/asciidoc/logging.adoc

View workflow job for this annotation

GitHub Actions / Linting with Vale 

[vale] reported by reviewdog 🐶
[Quarkus.CaseSensitiveTerms] Use 'JBoss EAP' rather than 'JBoss'.

Raw Output:
{"message": "[Quarkus.CaseSensitiveTerms] Use 'JBoss EAP' rather than 'JBoss'.", "location": {"path": "docs/src/main/asciidoc/logging.adoc", "range": {"start": {"line": 28, "column": 16}}}, "severity": "INFO"}

.An example of using the JBoss Logging API to log a message:

Check warning on line 30 in docs/src/main/asciidoc/logging.adoc

View workflow job for this annotation

GitHub Actions / Linting with Vale 

[vale] reported by reviewdog 🐶
[Quarkus.CaseSensitiveTerms] Use 'JBoss EAP' rather than 'JBoss'.

Raw Output:
{"message": "[Quarkus.CaseSensitiveTerms] Use 'JBoss EAP' rather than 'JBoss'.", "location": {"path": "docs/src/main/asciidoc/logging.adoc", "range": {"start": {"line": 30, "column": 26}}}, "severity": "INFO"}
[source,java]
Expand Down Expand Up @@ -802,7 +802,7 @@ In Quarkus, the MDC provider has a specific implementation for handling the reac
As a result, you can still access the MDC data in various scenarios:

* After asynchronous calls, like for example, when a REST client returns a Uni.
* When dealing with code submitted to the `ManagedExecutor` using `@Inject org.eclipse.microprofile.context.ManagedExecutor executor`.
* In code submitted to `org.eclipse.microprofile.context.ManagedExecutor`.
* In code executed with `vertx.executeBlocking()`.

NOTE: NOTE: MDC data is stored in a duplicated context, isolated for processing.
Expand Down

0 comments on commit f4578c9

Please sign in to comment.