You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Patrick Linskey (JIRA)" <ji...@apache.org> on 2007/02/01 07:42:05 UTC

[jira] Commented: (OPENJPA-10) persistence unit name should be default diagnostic context for standard OpenJPA log impl

    [ https://issues.apache.org/jira/browse/OPENJPA-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469345 ] 

Patrick Linskey commented on OPENJPA-10:
----------------------------------------

Resolved with 475084

> persistence unit name should be default diagnostic context for standard OpenJPA log impl
> ----------------------------------------------------------------------------------------
>
>                 Key: OPENJPA-10
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-10
>             Project: OpenJPA
>          Issue Type: Improvement
>            Reporter: Patrick Linskey
>            Priority: Minor
>
> OpenJPA's default logging implementation has a concept of a diagnostic context, roughly stolen from log4j. The basic idea is that in a configuration file, the user can specify a diagnostic context string that will be printed out with each log message. The result is that if a user has multiple EntityManagerFactories running in the same JVM, she can distinguish between the different logging outputs, even if they all just go to stderr.
> The JPA spec requires that persistence units are named uniquely. This presents us with an opportunity: we could check for the existence of multiple EMFs and, if found and the user did not specify a diagnostic context, automatically set the logging diagnostic context based on the name of the persistence unit.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.