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/05/20 03:47:00 UTC
[jira] [Resolved] (MAILBOX-355) MailboxListener should not rely on
MailboxPath
[ https://issues.apache.org/jira/browse/MAILBOX-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tellier Benoit resolved MAILBOX-355.
------------------------------------
Resolution: Fixed
Commits solving this: 387861af61 577d661f35 6fe8891220 e7e5ba68ad 5b05b9445f 3412083e85 3412083e85 16e4d9f93d
> MailboxListener should not rely on MailboxPath
> ----------------------------------------------
>
> Key: MAILBOX-355
> URL: https://issues.apache.org/jira/browse/MAILBOX-355
> Project: James Mailbox
> Issue Type: Improvement
> Components: api
> Affects Versions: 3.2.0
> Reporter: Tellier Benoit
> Priority: Major
> Fix For: 3.3.0
>
>
> Now that in https://issues.apache.org/jira/browse/MAILBOX-352 events carry MailboxId we can remote usage for mailboxPath from the MailboxListeners.
> 47 calls, many of which in code that is going to be removed.
> If possible, keep doing the job with 'just' the mailboxId. Otherwize use the mailboxManager to retrieve the MailboxPath associated with a given mailboxId.
--
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