[
https://issues.apache.org/jira/browse/DERBY-5029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lily Wei updated DERBY-5029:
----------------------------
Attachment: DERBY-5029-1.diff
Thanks Rick for the suggestion.
I am uploading DERBY-5029-1.diff patch
With this patch, getParentLogger() will work after the engine has been shut
down once.
Also, I modify some comments and AutoloadTest based on Dag's comment.
https://issues.apache.org/jira/browse/DERBY-2905?focusedCommentId=12992533&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12992533
jdbc4._Suite passed with this patch. Please review the patch. Thanks.
> getParentLogger() won't work after the engine has been shut down once
> ---------------------------------------------------------------------
>
> Key: DERBY-5029
> URL: https://issues.apache.org/jira/browse/DERBY-5029
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.7.1.1
> Environment: Windows 7 64 bits
> Reporter: Lily Wei
> Fix For: 10.8.0.0
>
> Attachments: DERBY-5029-1.diff
>
>
> Plans for JDBC 4.1 implementation are dependent on Autoloader40 being loaded
> after shutdown so that the getParentLogger() function will work. The attached
> program ww.java provided by rick in discussions on DERBY-2905 show that
> AutoloadedDriver would get loaded instead. This will prevent
> getParentLogger() from working once implemented.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
