You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Tellier Benoit (JIRA)" <ji...@apache.org> on 2019/01/21 03:10:00 UTC
[jira] [Commented] (MAILBOX-371) Implement routing for notification
listeners (key registrations)
[ https://issues.apache.org/jira/browse/MAILBOX-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16747629#comment-16747629 ]
Tellier Benoit commented on MAILBOX-371:
----------------------------------------
https://github.com/linagora/james-project/pull/2113 added tests for dispatching before registration. In that case, events should not be received.
> Implement routing for notification listeners (key registrations)
> ----------------------------------------------------------------
>
> Key: MAILBOX-371
> URL: https://issues.apache.org/jira/browse/MAILBOX-371
> Project: James Mailbox
> Issue Type: New Feature
> Reporter: Trần Tiến Đức
> Priority: Major
> Fix For: 3.3.0
>
>
> Reusing the work of "creating new RabbitMQEventBus" we will implement support for per mailbox registration of MailboxListeners (asynchronous execution).
> - Each James server creates a notification queue
> - Upon MailboxListener registration, James adds a binding for the given MailboxId from the exchange to its queue
> - James create consumers delivering events to locally registers MailboxListeners, according to the event MailboxId
> Tests:
> - Ensure that notifications works on a single RabbitMQDelegatingMailboxListener
> - Ensure that notifications works on two RabbitMQDelegatingMailboxListeners (listeners registered on 2 are aware of events generated on 1)
> Note: Several registration can be done on the same node, a record of lacal registration (in memory) needs to be kept.
>
> Update: you need to extract registration tests in EventBusContract to a new Contract then implements it in your new RabbitMQEventBusTest.
> also need to have tests about multiple event bus
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org