Hi,
+1, yes we could use the same way the queue's are handled. Have the list of
queues in DLC with the destination queue name, and number of messages, and
through the browse button you can browse the message.
On Sun, Mar 23, 2014 at 11:36 PM, Pamod Sylvester pa...@wso2.com wrote:
+1 for the
We (Pamod,Hasitha,Shammi and myself ) had a meeting on the current state of
the DLC implementation. Following is the concerns raised and the agreed
solutions.
*1. What if user deletes original queue when there are messages addressed
to that queue remains in DLC ?*
When user decides to delete
+1 for the approach to add further filtering per queue. Currently from the
server the destination queue information is sent to the UI. We might need
to add some filtering per queue basis and re categorize them.
@Ishara/Shani : WDYT about the approach ?
On Mon, Mar 24, 2014 at 11:55 AM, Asanka
Also to add, the filtering criteria for the DLC queue should change.
Currently the queues are checked as to whether, it 'contains' the string
DeadLetterChannel. Whereas it makes it possible for a queue which has a
names such as ex :- abcDeadLetterChannel to be diverted to the DLC queue.
This
Hi Asanka/Shani,
On Mon, Mar 24, 2014 at 12:11 PM, Shani Ranasinghe sh...@wso2.com wrote:
Hi,
+1, yes we could use the same way the queue's are handled. Have the list
of queues in DLC with the destination queue name, and number of messages,
and through the browse button you can browse the
On Mon, Mar 24, 2014 at 3:31 PM, Ishara Premadasa ish...@wso2.com wrote:
We (Pamod,Hasitha,Shammi and myself ) had a meeting on the current state
of the DLC implementation. Following is the concerns raised and the agreed
solutions.
*1. What if user deletes original queue when there are
The latest code of the DLC implementation is committed with r198710.
Currently we're progressing in implementing the feature to be tenant aware,
for the tenant aware model a DLC queue will be created per tenant, the
queue signature will be *{tenantdomain}/DeadLetterChannel*.
The above model
