[ https://issues.apache.org/jira/browse/DERBY-1275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478616 ]
Mamta A. Satoor commented on DERBY-1275: ---------------------------------------- Laura, the current thought is to keep this as an undocumented addition to Derby. There is information on this addition at http://wiki.apache.org/db-derby/UndocumentedDerbyBehavior if a user wants to go ahead and use it until some another way of on the fly client tracing is enabled, ie w/o changing the application. If the community thinks it is ok to go ahead and make the properties introduced in my solution as an official solution then we can go ahead and add it to Derby's official docs. > Provide a way to enable client tracing without changing the application > ----------------------------------------------------------------------- > > Key: DERBY-1275 > URL: https://issues.apache.org/jira/browse/DERBY-1275 > Project: Derby > Issue Type: Improvement > Components: Network Client > Affects Versions: 10.1.3.1, 10.2.1.6 > Reporter: Kathey Marsden > Assigned To: Mamta A. Satoor > Priority: Minor > Fix For: 10.3.0.0 > > Attachments: DERBY1275EnableClientTracingDiffV1.txt, > DERBY1275EnableClientTracingDiffV2.txt, > DERBY1275EnableClientTracingDiffV3.txt, > DERBY1275EnableClientTracingDiffV4.txt, > DERBY1275EnableClientTracingDiffV5.txt, > DERBY1275EnableClientTracingStatV1.txt, > DERBY1275EnableClientTracingStatV2.txt, > DERBY1275EnableClientTracingStatV3.txt, > DERBY1275EnableClientTracingStatV4.txt, DERBY1275EnableClientTracingStatV5.txt > > > 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. - You can reply to this email to add a comment to the issue online.