[ 
https://issues.apache.org/jira/browse/QPID-5650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14188489#comment-14188489
 ] 

ASF subversion and git services commented on QPID-5650:
-------------------------------------------------------

Commit 1635183 from [email protected] in branch 'qpid/trunk'
[ https://svn.apache.org/r1635183 ]

QPID-5650: Move attribute names into upgrader constants

> [Java Broker] DurableConfigurationStoreUpgrader relies on the action of the 
> AMQQueueFactory to reunite queue with its dead letter exchange
> ------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-5650
>                 URL: https://issues.apache.org/jira/browse/QPID-5650
>             Project: Qpid
>          Issue Type: Improvement
>    Affects Versions: 0.30
>            Reporter: Keith Wall
>            Assignee: Keith Wall
>             Fix For: 0.31
>
>         Attachments: 
> set-alt-exchange-only-when-attribute-is-set-on-queue.diff, test-store.tar.gz
>
>
> Currently, when upgrading a configuration store v4 store, if the store 
> contains a queue that has a DLQ and associated DLE (*), it is the action of 
> the AMQQueueFactory that is used to reunite the queue with its alternate 
> exchange.   This is rather a poor division of responsibilities and makes that 
> the code in the factory to be rather more complicated than it ought.
> The DurableConfigurationStoreUpgraders should be changed so that if they 
> encounter an appropriately named exchange (i.e. one with standard _DLE 
> suffix), they take the responsibility of producing ConfiguredObjectRecord for 
> the queue with the alternateExchange attribute properly populated.
> (*) The test BDBStoreUpgrade#xtestRecoveryOfQueueWithDLQ uses such a store



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to