[
https://issues.apache.org/jira/browse/QPID-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Greig updated QPID-156:
------------------------------
Description:
Currently, we have no persistent store implementation that can be hosted on
Apache due to licence issues. (We use Berkeley DB currently). Would be better
to offer an alternative imeplmentation which allows the use of Apache licensed
code for persistence to disk.
Previously been discussion on dev list regarding best solution for this,
including appropriate API - using O/R mappers, JDBC, in-line SQL etc etc.
More implementation details to be added by assignee please prior to progressing
this change.
was:
Currently, we only provide an implementation of persistence in-memory using
Qpid code. For persistence to disk we use the Berkeley DB. Would be better to
offer an alternative imeplmentation which allows the use of Apache licensed
code for persistence to disk.
Previously been discussion on dev list regarding best solution for this,
including appropriate API - using O/R mappers, JDBC, in-line SQL etc etc.
More implementation details to be added by assignee please prior to progressing
this change.
Summary: Implement persistent store with Apache compliant licence
(was: Implement persistence to disk for Qpid)
Updated the subject to make it clear that the lack of persistent store was a
licence issue.
> Implement persistent store with Apache compliant licence
> --------------------------------------------------------
>
> Key: QPID-156
> URL: https://issues.apache.org/jira/browse/QPID-156
> Project: Qpid
> Issue Type: New Feature
> Components: Java Broker
> Affects Versions: M1, M2
> Reporter: Marnie McCormack
> Priority: Minor
> Fix For: M3
>
>
> Currently, we have no persistent store implementation that can be hosted on
> Apache due to licence issues. (We use Berkeley DB currently). Would be better
> to offer an alternative imeplmentation which allows the use of Apache
> licensed code for persistence to disk.
> Previously been discussion on dev list regarding best solution for this,
> including appropriate API - using O/R mappers, JDBC, in-line SQL etc etc.
> More implementation details to be added by assignee please prior to
> progressing this change.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
