Sorry to bother you. Yes, but merely extending the range in the MailPrioritySupport interface will not guarantee that the PriorityMailQueueContract and PriorityManageableMailQueueContract contracts are adhered to for negative priority values. For instance, the MailPrioritySupport implementation, JMSCacheableMailQueue, relies on jakarta.jms.
вт, 13 авг. 2024 г. в 13:56, Benoit TELLIER <btell...@linagora.com>: > Hello, > > As said on github, +1 > > I believe the range 0-9 is defined within the Mail interface which is a > James class. > > My understanding is that we are fully able to increase this range without > third party library impacting us. > > BTW by moving to a larger range we are causing no breaking change as by > design all previous ranges are to be supported. > > -- > > Best regards, > > Benoit TELLIER > > General manager of Linagora VIETNAM. > Product owner for Team-Mail product. > Chairman of the Apache James project. > > Mail: btell...@linagora.com > Tel: (0033) 6 77 26 04 58 (WhatsApp, Signal) > > > On Aug 11, 2024 3:50 PM, from Maksim Meliashchuk Hello everyone! > As a follow-up to > issues.apache.org/jira/projects/JAMES/issues/JAMES-3824?filter=allissues > I would like to consider extending the priority range from -9 to 9 to > implement mail queues in accordance with > datatracker.ietf.org/doc/rfc6710/ > Currently, the Jakarta Messaging API defines ten priority levels, where 0 > is the lowest priority and 9 is the highest. Any ideas on how to use > negative priorities? What might a JMS modification or alternative look > like? >
