[
https://issues.apache.org/jira/browse/DERBY-4715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12887286#action_12887286
]
Kristian Waagan commented on DERBY-4715:
----------------------------------------
Regarding the public methods in utility classes, I think it is fine to create
(and use them) if they add value, but the utility method should not include the
call to doPrivileged. Instead, the calling code (which is hopefully not easily
accessible and controllable for external users) should call the utility method
inside a doPrivileged-block.
The above approach isn't as compact, but Kathey is right that adding public
(static) utility methods with doPrivileged-blocks is dangerous.
> Write jvm information and path of derby.jar to derby.log
> --------------------------------------------------------
>
> Key: DERBY-4715
> URL: https://issues.apache.org/jira/browse/DERBY-4715
> Project: Derby
> Issue Type: Bug
> Components: Miscellaneous
> Affects Versions: 10.6.1.0
> Reporter: Lily Wei
> Assignee: Lily Wei
> Priority: Minor
> Fix For: 10.7.0.0
>
> Attachments: DERBY-4715-1.diff, DERBY-4715-2.diff, DERBY-4715-3.diff,
> derby.log
>
>
> The bug is part of DERBY-1272. In production environment, derby.jar can be
> located different than the derbyclient.jar It can be easier if we have jvm
> version information and path of derby.jar are in the derby.log
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
