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

4.x: Minor change in the docs #9404

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

4.x: Minor change in the docs #9404

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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 docs/src/main/asciidoc/mp/config/advanced-configuration.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -87,7 +87,7 @@ include::{sourcedir}/mp/config/AdvancedConfigurationSnippets.java[tag=snippet_2,
Custom Config Sources are loaded using the Java Service Loader pattern, by implementing
either `org.eclipse.microprofile.config.spi.ConfigSource`,
or `org.eclipse.microprofile.config.spi.ConfigSourceProvider` SPI and registering
it as a service (Using `pass:[META-INF/services/${class-name}]` file when using classpath, or
it as a service (Using pass:normal[`META-INF/services/${class-name}`] file when using classpath, or
using the `provides` statement in `module-info.java` when using module path).

The interface `org.eclipse.microprofile.config.spi.ConfigSource` requires implementation of the following methods:
Expand Down Expand Up @@ -172,7 +172,7 @@ sources:

== Extending Meta-Config to Create a Custom Config Source Type

Helidon meta-config by default supports the following types: environment-variables, system-properties, properties, yaml, hocon and json. Users can also extend meta-config to create a custom config source type by loading it using the Java Service Loader pattern. This is achieved by implementing `io.helidon.config.mp.spi.MpMetaConfigProvider` SPI and registering it as a service (Using `pass:[META-INF/services/${class-name}]` file when using classpath, or using the `provides` statement in `module-info.java` when using module path).
Helidon meta-config by default supports the following types: environment-variables, system-properties, properties, yaml, hocon and json. Users can also extend meta-config to create a custom config source type by loading it using the Java Service Loader pattern. This is achieved by implementing `io.helidon.config.mp.spi.MpMetaConfigProvider` SPI and registering it as a service (Using pass:normal[`META-INF/services/${class-name}`] file when using classpath, or using the `provides` statement in `module-info.java` when using module path).

The interface `io.helidon.config.mp.spi.MpMetaConfigProvider` requires implementation of the following methods:

Expand Down
2 changes: 1 addition & 1 deletion docs/src/main/asciidoc/se/config/advanced-configuration.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -486,7 +486,7 @@ for more detail.

=== Tokens
A token reference is a key token starting with `$`, optionally enclosed between
`{` and `}`, i.e. `$ref`, `pass:[${ref}]`. Even a key composed of more than one token
`{` and `}`, i.e. `$ref`, pass:normal[`${ref}`]. Even a key composed of more than one token
can be referenced in another key, i.e. `${env.ref}`.

As an example use case, you can use token references to declare the default values (see
Expand Down
2 changes: 1 addition & 1 deletion docs/src/main/asciidoc/se/guides/webclient.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -196,7 +196,7 @@ Hello David!
----

It is also possible to change the greeting word by using a PUT request to `/greet/greeting` path. The request also
needs to include a body with JSON type and using a structure like `pass:[{"greeting" : "value"}]`.
needs to include a body with JSON type and using a structure like pass:normal[`{"greeting" : "value"}`].

[source,java]
.Modify the application greeting:
Expand Down