<
From version < 17.1 >
edited by Thomas Mortagne
on 2015/06/18
To version < 17.2 >
edited by Vincent Massol
on 2015/09/24
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ThomasMortagne
1 +XWiki.VincentMassol
Content
... ... @@ -151,6 +151,10 @@
151 151  * Mail Status Store API has been refactored to provides ordered result based on any status fields. A new method also ease loading a single status for a given messageId.
152 152  * When evaluating Velocity in Mail Templates, the Execution Context used is a clone of the one that was available when the ##send*(...)## method was called. Thus all Velocity bindings that were present are available from your Mail Template.
153 153  
154 +{{error}}
155 +Several API breakages have been introduced, make sure to check the [[Mail backward-compatibility section below>>||anchor="HMailAPIchanges"]].
156 +{{/error}}
157 +
154 154  == Job Progress Improvements ==
155 155  
156 156  It's now possible to associate message to each step of the progress. Also a new API have been added to make easier to notify about progress in scripts.
... ... @@ -276,12 +276,6 @@
276 276  
277 277  When upgrading make sure you compare your ##xwiki.cfg##, ##xwiki.properties## and ##web.xml## files with the newest version since some configuration parameters may have been modified or added. Note that you should add ##xwiki.store.migration=1## so that XWiki will attempt to automatically migrate your current database to the new schema. Make sure you backup your Database before doing anything.
278 278  
279 -{{comment}}
280 -== Issues specific to XWiki 7.1 ==
281 -
282 -<issues specific to the project>
283 -{{/comment}}
284 -
285 285  == Mail API changes ==
286 286  
287 287  The young mail API has been refactored to provide better and more detailed error reporting.
... ... @@ -290,6 +290,8 @@
290 290  
291 291  There is now more than one message state representing an error, therefore, the MailStatusResult interface has been extended with a ###getAllError()## method to retrieve all message status in error. Moreover, the ###getTotalMailCount()# may represent a partial total in case of failure of the prepare phase. In that case, it represents the number of mails sent to the send phase. As a consequence, ###isProcessed()# and ###waitTillProcess()# now considerer the batch to be processed when all successfully prepared mail has been sent, or failed to be prepared or sent.##
292 292  
291 +Please review the [[new way to check for errors>>extensions:Extension.Mail Sender API||anchor="HCheckforErrors"]]].
292 +
293 293  The mail API is now tracking individual message based on the standard Message-ID headers, which made it fully compliant with RFC-822 WRT the mail identification. Caller that want to specify custom Message-ID may do so by extending MimeMessage to preserve the Message-ID of the message. Caller is also responsible to ensure that different messages are identified by unique message identifier.
294 294  
295 295  {{warning}}

Get Connected