|
Log4j 1.3alpha-7 | ||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
The LogManager
uses one (and only one)
RepositorySelector
implementation to select the
LoggerRepository
for a particular application context.
It is the responsability of the RepositorySelector
implementation to track the application context. Log4j makes no assumptions
about the application context or on its management.
See also LogManager
.
Method Summary | |
LoggerRepository |
detachRepository(String name)
Remove the repository with the given name from the list maintained by the respository selector. |
LoggerRepository |
getLoggerRepository()
Returns a LoggerRepository depending on the context. |
LoggerRepository |
getLoggerRepository(String name)
Get a LoggerRepository by name. |
Method Detail |
public LoggerRepository getLoggerRepository(String name)
LoggerRepository
by name. If the named repository does not
exists or is unknown to this selector, then null
is returned.
public LoggerRepository getLoggerRepository()
LoggerRepository
depending on the context. Implementors
must make sure that under all circumstances a valid (non-null)
LoggerRepository is returned.
public LoggerRepository detachRepository(String name)
When applications are stopped or recycled, this method should be called to ensure that the associated repository is recycled as well. After the repository is detached from this selector, the returned value, i.e. the detached repository, can be used to shutdown the repository.
If more than one application share the same logging context, then the applications need to coordinate their actions.
|
Log4j 1.3alpha-7 | ||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |