You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org> on 2009/02/03 17:43:59 UTC
[jira] Created: (QPID-1631) Create TransactionLog and RoutingTable
interfaces from MessageStore
Create TransactionLog and RoutingTable interfaces from MessageStore
-------------------------------------------------------------------
Key: QPID-1631
URL: https://issues.apache.org/jira/browse/QPID-1631
Project: Qpid
Issue Type: Sub-task
Reporter: Martin Ritchie
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Assigned: (QPID-1631) Create TransactionLog and RoutingTable
interfaces from MessageStore
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie reassigned QPID-1631:
------------------------------------
Assignee: Aidan Skinner (was: Martin Ritchie)
Hi Aidan, I've also completed this, there is also a test along with this interface refactor to test that we correctly create the new _routingTable in the Virtualhost if the _transactionLog is also a RoutingTable.
> Create TransactionLog and RoutingTable interfaces from MessageStore
> -------------------------------------------------------------------
>
> Key: QPID-1631
> URL: https://issues.apache.org/jira/browse/QPID-1631
> Project: Qpid
> Issue Type: Sub-task
> Components: Java Broker
> Affects Versions: M4
> Reporter: Martin Ritchie
> Assignee: Aidan Skinner
> Fix For: M5
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> Replace existing MessageStore interface with TransactionLog and RoutingTable.
> There should be minimal change to the existing code as a result of this.
> Our existing *MessageStores can continue to operate as before but this gives us freedom to create new TransactionLogs and RoutingTable implementations.
> Some changes will be required in the broker startup as it currently requires the specified configuration class implements MessageStore.
> Backward compatibility will be key here. Existing configuration files should still be able to work as the underlying code has not changed only the interface names.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Updated: (QPID-1631) Create TransactionLog and RoutingTable
interfaces from MessageStore
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie updated QPID-1631:
---------------------------------
Status: Ready To Review (was: In Progress)
> Create TransactionLog and RoutingTable interfaces from MessageStore
> -------------------------------------------------------------------
>
> Key: QPID-1631
> URL: https://issues.apache.org/jira/browse/QPID-1631
> Project: Qpid
> Issue Type: Sub-task
> Components: Java Broker
> Affects Versions: M4
> Reporter: Martin Ritchie
> Assignee: Martin Ritchie
> Fix For: M5
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> Replace existing MessageStore interface with TransactionLog and RoutingTable.
> There should be minimal change to the existing code as a result of this.
> Our existing *MessageStores can continue to operate as before but this gives us freedom to create new TransactionLogs and RoutingTable implementations.
> Some changes will be required in the broker startup as it currently requires the specified configuration class implements MessageStore.
> Backward compatibility will be key here. Existing configuration files should still be able to work as the underlying code has not changed only the interface names.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Assigned: (QPID-1631) Create TransactionLog and RoutingTable
interfaces from MessageStore
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie reassigned QPID-1631:
------------------------------------
Assignee: Martin Ritchie
> Create TransactionLog and RoutingTable interfaces from MessageStore
> -------------------------------------------------------------------
>
> Key: QPID-1631
> URL: https://issues.apache.org/jira/browse/QPID-1631
> Project: Qpid
> Issue Type: Sub-task
> Components: Java Broker
> Affects Versions: M4
> Reporter: Martin Ritchie
> Assignee: Martin Ritchie
> Fix For: M5
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> Replace existing MessageStore interface with TransactionLog and RoutingTable.
> There should be minimal change to the existing code as a result of this.
> Our existing *MessageStores can continue to operate as before but this gives us freedom to create new TransactionLogs and RoutingTable implementations.
> Some changes will be required in the broker startup as it currently requires the specified configuration class implements MessageStore.
> Backward compatibility will be key here. Existing configuration files should still be able to work as the underlying code has not changed only the interface names.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Updated: (QPID-1631) Create TransactionLog and RoutingTable
interfaces from MessageStore
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie updated QPID-1631:
---------------------------------
Component/s: Java Broker
Fix Version/s: M5
Description:
Replace existing MessageStore interface with TransactionLog and RoutingTable.
There should be minimal change to the existing code as a result of this.
Our existing *MessageStores can continue to operate as before but this gives us freedom to create new TransactionLogs and RoutingTable implementations.
Some changes will be required in the broker startup as it currently requires the specified configuration class implements MessageStore.
Backward compatibility will be key here. Existing configuration files should still be able to work as the underlying code has not changed only the interface names.
Affects Version/s: M4
Remaining Estimate: 4h
Original Estimate: 4h
> Create TransactionLog and RoutingTable interfaces from MessageStore
> -------------------------------------------------------------------
>
> Key: QPID-1631
> URL: https://issues.apache.org/jira/browse/QPID-1631
> Project: Qpid
> Issue Type: Sub-task
> Components: Java Broker
> Affects Versions: M4
> Reporter: Martin Ritchie
> Fix For: M5
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> Replace existing MessageStore interface with TransactionLog and RoutingTable.
> There should be minimal change to the existing code as a result of this.
> Our existing *MessageStores can continue to operate as before but this gives us freedom to create new TransactionLogs and RoutingTable implementations.
> Some changes will be required in the broker startup as it currently requires the specified configuration class implements MessageStore.
> Backward compatibility will be key here. Existing configuration files should still be able to work as the underlying code has not changed only the interface names.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Commented: (QPID-1631) Create TransactionLog and
RoutingTable interfaces from MessageStore
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673289#action_12673289 ]
Martin Ritchie commented on QPID-1631:
--------------------------------------
At this stage I think simply performing the interface changes and leaving the configuration as is for now is the way to go.
We can pick up the confuration change issue when the current changes to the configuration have stabilised.
> Create TransactionLog and RoutingTable interfaces from MessageStore
> -------------------------------------------------------------------
>
> Key: QPID-1631
> URL: https://issues.apache.org/jira/browse/QPID-1631
> Project: Qpid
> Issue Type: Sub-task
> Components: Java Broker
> Affects Versions: M4
> Reporter: Martin Ritchie
> Assignee: Martin Ritchie
> Fix For: M5
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> Replace existing MessageStore interface with TransactionLog and RoutingTable.
> There should be minimal change to the existing code as a result of this.
> Our existing *MessageStores can continue to operate as before but this gives us freedom to create new TransactionLogs and RoutingTable implementations.
> Some changes will be required in the broker startup as it currently requires the specified configuration class implements MessageStore.
> Backward compatibility will be key here. Existing configuration files should still be able to work as the underlying code has not changed only the interface names.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Resolved: (QPID-1631) Create TransactionLog and RoutingTable
interfaces from MessageStore
Posted by "Aidan Skinner (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aidan Skinner resolved QPID-1631.
---------------------------------
Resolution: Fixed
Assignee: Martin Ritchie (was: Aidan Skinner)
> Create TransactionLog and RoutingTable interfaces from MessageStore
> -------------------------------------------------------------------
>
> Key: QPID-1631
> URL: https://issues.apache.org/jira/browse/QPID-1631
> Project: Qpid
> Issue Type: Sub-task
> Components: Java Broker
> Affects Versions: M4
> Reporter: Martin Ritchie
> Assignee: Martin Ritchie
> Fix For: M5
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> Replace existing MessageStore interface with TransactionLog and RoutingTable.
> There should be minimal change to the existing code as a result of this.
> Our existing *MessageStores can continue to operate as before but this gives us freedom to create new TransactionLogs and RoutingTable implementations.
> Some changes will be required in the broker startup as it currently requires the specified configuration class implements MessageStore.
> Backward compatibility will be key here. Existing configuration files should still be able to work as the underlying code has not changed only the interface names.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org