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 "Kathey Marsden (JIRA)" <ji...@apache.org> on 2009/05/07 21:24:45 UTC
[jira] Assigned: (DERBY-927) Cleanup code in the monitor to clarify
the relationship between StorageFactory and PersistentService
[ https://issues.apache.org/jira/browse/DERBY-927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden reassigned DERBY-927:
------------------------------------
Assignee: (was: Daniel John Debrunner)
Unnassigning due to inactivity. Please reassign yourself if you would like to work on this issue.
> Cleanup code in the monitor to clarify the relationship between StorageFactory and PersistentService
> ----------------------------------------------------------------------------------------------------
>
> Key: DERBY-927
> URL: https://issues.apache.org/jira/browse/DERBY-927
> Project: Derby
> Issue Type: Improvement
> Components: Services
> Reporter: Daniel John Debrunner
> Priority: Minor
>
> The addition of the StorageFactory code into the BaseMonitor code muddied the water with respect to what is a service and what is a storage factory.
> Cleanup the code and add comments and/or a package.html to describe what is going on.
> Look at loading the storage factories through the modules.properties rather than the hard-coded list and thus gain the benefit of the standard module environment
> checking (jvm level and dependent classes) and ensure classes are loaded from modules.properties consistently.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.