Siphalor/tweed5-commons-logging
1
0
Fork 0
Code Activity

Normalize spelling

Browse Source
This commit is contained in:
Gary Gregory
2024-08-14 07:45:12 -04:00
parent b9667701e6
commit a823926443
2 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
src/site/xdoc/guide.xml
View File

@@ -126,7 +126,7 @@ and will report any configuration problems that prevent that system being used.
</p>
<p>
When no particular logging library is specified, then JCL will silently ignore any logging library
that it finds but cannot initialise and continue to look for other alternatives. This is a deliberate
that it finds but cannot initialize and continue to look for other alternatives. This is a deliberate
design decision; no application should fail to run because a "guessed" logging library cannot be
used. To ensure an exception is reported when a particular logging library cannot be used, use one
of the available JCL configuration mechanisms to force that library to be selected (ie disable
@@ -215,11 +215,11 @@ Configuration of the behavior of the JCL ultimately depends upon the
logging toolkit being used. Please consult the documentation for the chosen logging system.
</p>
<p>
JCL is NOT responsible for initialisation, configuration, or shutdown of the underlying logging library.
In many cases logging libraries will automatically initialise/configure themselves when first used, and
JCL is NOT responsible for initialization, configuration, or shutdown of the underlying logging library.
In many cases logging libraries will automatically initialize/configure themselves when first used, and
need no explicit shutdown process. In these situations an application can simply use JCL and not depend
directly on the API of the underlying logging system in any way. However if the logging library being used
requires special initialisation, configuration, or shutdown, then some logging-library-specific code will
requires special initialization, configuration, or shutdown, then some logging-library-specific code will
be required in the application. JCL simply forwards logging method calls to the correct underlying
implementation. When writing library code this issue is of course not relevant as the calling application
is responsible for handling such issues.