qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Wall (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (QPID-7653) [Java Broker] Separate JDBC and Derby Plugins from Broker Core
Date Fri, 22 Sep 2017 09:39:00 GMT

     [ https://issues.apache.org/jira/browse/QPID-7653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Keith Wall resolved QPID-7653.
------------------------------
    Resolution: Fixed

> [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
>             Fix For: qpid-java-broker-7.0.0
>
>
> 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.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message