[
https://issues.apache.org/jira/browse/DERBY-1275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamta A. Satoor updated DERBY-1275:
-----------------------------------
Attachment: DERBY1275EnableClientTracingStatV4.txt
DERBY1275EnableClientTracingDiffV4.txt
Dan, I have
1)taken care of "." from the trace directory for portability reasons,
2)removed the use of static field from the junit test and
3)created a new method to fetch the system property rather than duplicating the
code in 2 places in ClientBaseDataSource.
All these changes are in DERBY1275EnableClientTracingDiffV4.txt. svn stat -q
output hasn't really changed since the last attachement but I have copied it
again ( DERBY1275EnableClientTracingStatV4.txt) to have svn stat -q output for
every patch revision.
As for your last comment about decorators, I am not 100% clear yet on what you
are proposing. I will spend some more time in trying to figure it out.
I will fire the junit test suite to make sure the patch attached doesn't cause
any regression.
> 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.2.3.0
>
> Attachments: DERBY1275EnableClientTracingDiffV1.txt,
> DERBY1275EnableClientTracingDiffV2.txt,
> DERBY1275EnableClientTracingDiffV3.txt,
> DERBY1275EnableClientTracingDiffV4.txt,
> DERBY1275EnableClientTracingStatV1.txt,
> DERBY1275EnableClientTracingStatV2.txt,
> DERBY1275EnableClientTracingStatV3.txt, DERBY1275EnableClientTracingStatV4.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.
