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 "René Cordier (Jira)" <se...@james.apache.org> on 2022/11/30 09:35:00 UTC

[jira] [Updated] (JAMES-3864) Unify vhost management with queues and RabbitMQ

     [ https://issues.apache.org/jira/browse/JAMES-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

René Cordier updated JAMES-3864:
--------------------------------
    Description: 
Actually in James we have our queues that get assigned to the correct vhost on rabbitmq but in two different ways:
- via the uri parameter in rabbitmq.properties, like: 
{noformat}
amqp://{user}:{password}@{rabbit_host}:{rabbit_port}/{vhost}
{noformat}
- via the parameter `vhost` in rabbitmq.properties (like for the mail queues)

It's not really logical and confusing for users in general. We should:

- agree on one unified way to get the vhost for all queues (uri parsing or vhost parameter)
- refactor the code following the consensus on the solution

  was:
Actually in James we have our queues that get assigned to the correct vhost on rabbitmq but in two different ways:
- via the uri parameter in rabbitmq.properties, like: 
{noformat}
"amqp://{user}:{password}@{rabbit_host}:{rabbit_port}/{vhost}"
{noformat}
- via the parameter `vhost` in rabbitmq.properties (like for the mail queues)

It's not really logical and confusing for users in general. We should:

- agree on one unified way to get the vhost for all queues (uri parsing or vhost parameter)
- refactor the code following the consensus on the solution


> Unify vhost management with queues and RabbitMQ
> -----------------------------------------------
>
>                 Key: JAMES-3864
>                 URL: https://issues.apache.org/jira/browse/JAMES-3864
>             Project: James Server
>          Issue Type: Improvement
>            Reporter: René Cordier
>            Priority: Minor
>
> Actually in James we have our queues that get assigned to the correct vhost on rabbitmq but in two different ways:
> - via the uri parameter in rabbitmq.properties, like: 
> {noformat}
> amqp://{user}:{password}@{rabbit_host}:{rabbit_port}/{vhost}
> {noformat}
> - via the parameter `vhost` in rabbitmq.properties (like for the mail queues)
> It's not really logical and confusing for users in general. We should:
> - agree on one unified way to get the vhost for all queues (uri parsing or vhost parameter)
> - refactor the code following the consensus on the solution



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org