[
https://issues.apache.org/jira/browse/QPID-7653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15936695#comment-15936695
]
ASF subversion and git services commented on QPID-7653:
-------------------------------------------------------
Commit 1788141 from [~lorenz.quack] in branch 'java/trunk'
[ https://svn.apache.org/r1788141 ]
QPID-7653: [Java Broker, JDBC, Derby] Move JDBC classes out of core. Make Derby
plugin depend on JDBC plugin
> [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: [email protected]
For additional commands, e-mail: [email protected]
