db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <derby-...@db.apache.org>
Subject [jira] Created: (DERBY-1275) Provide a way to enable client tracing without changing the application
Date Tue, 02 May 2006 04:27:46 GMT
Provide a way to enable client tracing without changing the application
-----------------------------------------------------------------------

         Key: DERBY-1275
         URL: http://issues.apache.org/jira/browse/DERBY-1275
     Project: Derby
        Type: Improvement

  Components: Network Client  
    Versions: 10.1.2.3, 10.2.0.0    
    Reporter: Kathey Marsden
    Priority: Minor


Currently  the client tracing can be enabled by  setting attributes on the client url, setXXX
methods on the DataSource or calling DriverManager.setLogWriter(), but it often cannot be
enabled in a deployed client application  because all of these API's require modification
of the application or its configuration files.

It would be good to have a global way to turn on client tracing.  A system property pointing
to a property file is  one possibility but probably not ideal because of the impact in class
loader contexts.    I am not sure what the other possiblities are,







-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message