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 should be adopted in the UI as well, where the DLC queue
should be filtered and pointed based on the above signature.
@Shani/Ishara : will it be possible to reflect the changes in the UI as
well ?
On Fri, Feb 28, 2014 at 2:39 PM, Pamod Sylvester <[email protected]> wrote:
> Attached diff contains the Dead Letter Channel (DLC) server
> side implementation. Shani will be able to provide input on the UI
> component.
>
> The following is the nature of the DLC feature implementation,
>
> ~ External parties will not be allowed to publish/subscribe to the DLC
> queue.
> ~ Messages in the DLC could be restored back to its origin queue or could
> be deleted (When deleting it was ensured that data from the NodeQueue CF,
> GlobalQueueCF and MessageContentCF was deleted)
>
> In addition to the above, an enhancement was Incorporated which will allow
> a user to specify a different destination queue other than its origin queue
> for the message to be restored. The admin service signature for
> the functionality is as follows,
>
> restoreMessagesFromDeadLetterQueueToDifferentDestination(String[]
> messageIDs, String destination)
>
> @Shani : will it be possible for you to add the capability in the UI to
> allow users to specify a destination queue of their choice and invoke the
> above service ?
>
> Please do let know if there're any amendments to be done in the existing
> flows.
>
> Thanks,
> Pamod
>
>
>
>
> On Sat, Feb 15, 2014 at 11:14 AM, Pamod Sylvester <[email protected]> wrote:
>
>> Hi All,
>>
>> The current status of the DLC implementation is described from the
>> following,
>>
>> ~ During the time where the messages are intended to be dropped after the
>> re-trying count has exceeded, it will first be stored in the Dead Letter
>> Channel queue which is an entry of the NodeQueues CF and the messages will
>> be purged.
>> ~ Implemented the functionality to delete a specific message from the DLC
>> through providing it an id of the message, and also restore a message back
>> ~ The re storing process will basically cut-past the message content
>> stored in the DLC entry in the NodeQueues CF back to the Global Queue.
>>
>> TO-DOs
>>
>> ~ Currently the dead-letter queue is created and listed as a general
>> queue, which will also be listed along with the other queues. Need to
>> discuss and figure out to list it as a separate entity. Need to modify the
>> permissions of that queue which will prevent the external users from
>> subscribing/publishing to this queue
>> ~Need to integrate with the UI and test the use cases in real time
>>
>> I've also attached the diff of the current implementation. Please do let
>> know of the amendments/modification which should be made.
>>
>> Thanks,
>> Pamod
>>
>> --
>> *Pamod Sylvester *
>> * Software Engineer *
>> Integration Technologies Team, WSO2 Inc.; http://wso2.com
>> email: [email protected] cell: +94 77 7779495
>>
>
>
>
> --
> *Pamod Sylvester *
> * Software Engineer *
> Integration Technologies Team, WSO2 Inc.; http://wso2.com
> email: [email protected] cell: +94 77 7779495
>
--
*Pamod Sylvester *
* Software Engineer *
Integration Technologies Team, WSO2 Inc.; http://wso2.com
email: [email protected] cell: +94 77 7779495
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev
