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.

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

Grammar fix for its #11

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
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
6 changes: 3 additions & 3 deletions src/jbake/content/Logging.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -5,15 +5,15 @@ Andrey Hihlovskiy
:jbake-type: page
:jbake-status: published

Gretty protocols it's own messages and messages from servlet container
Gretty protocols its own messages and messages from servlet container
with the help of http://logback.qos.ch/[logback-classic] library.

Gretty isolates it's own logging from the web application logging on the level of ClassLoader. That means:
Gretty isolates its own logging from the web application logging on the level of ClassLoader. That means:
the logback library (and logback configuration) used by Gretty is not visible within web application.
You are free to use any logging system - logback, log4j, commons-logging etc. - within your
web applications.

Gretty supports configuring it's own slf4j/logback logging by two methods:
Gretty supports configuring its own slf4j/logback logging by two methods:

. If you place "logback.groovy" or "logback.xml" to arbitrary folder and then reference it by +logbackConfigFile+ property, gretty applies the specified configuration to servlet-container process.
. If "logback.groovy" or "logback.xml" is not specified, gretty configures logging with default settings:
Expand Down