You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Lorenz Quack (JIRA)" <ji...@apache.org> on 2017/02/01 15:10:51 UTC
[jira] [Created] (QPID-7653) [Java Broker] Separate JDBC and Derby
Plugins from Broker Core
Lorenz Quack created QPID-7653:
----------------------------------
Summary: [Java Broker] Separate JDBC and Derby Plugins from Broker Core
Key: QPID-7653
URL: https://issues.apache.org/jira/browse/QPID-7653
Project: Qpid
Issue Type: Improvement
Components: Java Broker
Reporter: Lorenz Quack
Currently there are some parts of the JDBC and Derby plugins that leak into broker-core. The reason for this is that the two plugins share some code. It would probably be more reasonable to move the common code to the JDBC plugin and make the Derby Plugin depend on the JDBC plugin.
I identified the following JDBC top-level classes in core (might not be exhaustive):
* {{org.apache.qpid.server.store.AbstractJDBCConfigurationStore}}
* {{org.apache.qpid.server.store.AbstractJDBCMessageStore}}
* {{org.apache.qpid.server.store.preferences.AbstractJDBCPreferenceStore}}
* {{org.apache.qpid.server.store.jdbc.JDBCDetails}}
* {{org.apache.qpid.server.store.jdbc.ConnectionProvider}}
* {{org.apache.qpid.server.plugin.JDBCConnectionProviderFactory}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org