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 "Antoine Duprat (JIRA)" <se...@james.apache.org> on 2018/10/31 16:58:00 UTC
[jira] [Closed] (JAMES-2551) Bind RabbitMQ MailQueueFactory
implementation
[ https://issues.apache.org/jira/browse/JAMES-2551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antoine Duprat closed JAMES-2551.
---------------------------------
> Bind RabbitMQ MailQueueFactory implementation
> ---------------------------------------------
>
> Key: JAMES-2551
> URL: https://issues.apache.org/jira/browse/JAMES-2551
> Project: James Server
> Issue Type: Improvement
> Components: Queue
> Reporter: Trần Tiến Đức
> Priority: Major
> Fix For: 3.2.0
>
>
> The Cassandra product should use the RabbitMQ implementation of MailQueueFactory (also the ldap-Cassandra product).
> The implementation binding is actually done in james-server-guice-common (ActiveMQQueueModule class), we should extract this binding to its own project.
> We should pass all integration test on top of RabbitMQ. we may use rabbitmqadmin in docker for that:
>
> https://hub.docker.com/r/activatedgeek/rabbitmqadmin/
> and a command like this one: (we will have to provide RABBIT_HOST & RABBIT_PORT)
> $ docker run --rm activatedgeek/rabbitmqadmin:latest purge queue name=name_of_the_queue_to_be_purged
> Docker concerns: how to avoid spawning a Rabbit per test? (how to blow up data? Use namespaces?) Auto discover to disable?
>
--
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