db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1275) Provide a way to enable client tracing without changing the application
Date Fri, 23 Jun 2006 14:36:30 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1275?page=comments#action_12417497 ] 

Knut Anders Hatlen commented on DERBY-1275:

Hi Kathey, I think your approach sounds reasonable. It is definitely good to have some simple
way (documented or undocumented) to enable client-side tracing. By not documenting it, we
don't commit to support it in case we find a better way in the future. However, I think it's
a good idea that we maintain a list of such undocumented features somewhere. Otherwise, I
fear that they will be forgotten and just make the code less maintainable. What about creating
a wiki page with undocumented properties/features (clearly labelled as unsupported, of course)?

> 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:,
>     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:
For more information on JIRA, see:

View raw message