[
https://issues.apache.org/jira/browse/UIMA-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor resolved UIMA-2375.
----------------------------------
Resolution: Fixed
Fix Version/s: 2.4.1SDK
Assignee: Marshall Schor
applied patch
> Log methods for log wrappers
> ----------------------------
>
> Key: UIMA-2375
> URL: https://issues.apache.org/jira/browse/UIMA-2375
> Project: UIMA
> Issue Type: Improvement
> Components: Core Java Framework
> Reporter: Richard Eckart de Castilho
> Assignee: Marshall Schor
> Labels: patch
> Fix For: 2.4.1SDK
>
> Attachments: UIMA-2375-REC-2012-02-20.patch
>
>
> The logging framework of UIMA provides wrappers for several logging backends,
> e.g. for Log4J and JSR47. These frameworks provide special logging methods
> for logger wrappers that make sure the final logging message contains the
> correct logging location information (e.g. filename, class, line, etc.). The
> UIMA Logger interface does not provide such a generic logging method and is,
> thus, not suitable to be wrapped itself.
> Wrapping a Logger instance can be interesting for building complex logging
> message with helper methods, or, to provide an alternative logging API.
> Recently, uimaFIT 1.3.0 has introduced a more convenient logging API wrapping
> the UIMA Logger. Unfortunately, currently the class name written to the log
> is always the name of the logger wrapper, not of the original caller.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
