You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kristian Waagan (JIRA)" <ji...@apache.org> on 2011/06/10 11:10:58 UTC
[jira] [Commented] (DERBY-5253) Engine code references
org.apache.derby.shared.common.sanity.SanityManager
[ https://issues.apache.org/jira/browse/DERBY-5253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13047090#comment-13047090 ]
Kristian Waagan commented on DERBY-5253:
----------------------------------------
Note the exception in iapi.services.info.JVMInfo. Here SanityManager is imported from shared.common to make it possible to keep iapi.services.sanity sealed. JVMInfo is included in both derby.jar and derbyclient.jar.
> Engine code references org.apache.derby.shared.common.sanity.SanityManager
> --------------------------------------------------------------------------
>
> Key: DERBY-5253
> URL: https://issues.apache.org/jira/browse/DERBY-5253
> Project: Derby
> Issue Type: Bug
> Components: Miscellaneous
> Affects Versions: 10.9.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Priority: Minor
> Fix For: 10.9.0.0
>
> Attachments: derby-5253-1a-engine_imports.diff
>
>
> Derby engine code is importing org.apache.derby.shared.common.sanity.SanityManager, causing sealing violations. See DERBY-4669 why this fix is inadequate.
> Even though this won't fix the/all problems, using shared.common.sanity.SanityManager on the client and iapi.services.sanity.SanityManager in the engine code is a simple rule to follow. Violations are also easily addressed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira