Last modified by Thomas Mortagne on 2017/03/24

<
From version < 18.11 >
edited by Vincent Massol
on 2015/05/19
To version < 20.1 >
edited by Ramona Conoro
on 2015/05/20
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.VincentMassol
1 +XWiki.RamonaConoro
Content
... ... @@ -38,10 +38,10 @@
38 38  
39 39  == Mail API Improvements ==
40 40  
41 -* Send prepared mime message to multiple users as independent message. A new mime message cloning factory (hint "message") is available to be used with iterator factories. It duplicates a given source message as is, to allow sending it to multiple users as independent messages. See [[Example 5>>extensions:Extension.Mail Sender API||anchor="#HExample5:SendapreparedMimeMessagetoalistofUsersandGroups"]] of the documentation for a sample.
41 +* Send prepared mime message to multiple users as independent message. A new mime message cloning factory (hint "message") is available to be used with iterator factories. It duplicates a given source message as is, to allow sending it to multiple users as independent messages. See [[Example 5>>extensions:Extension.Mail Sender API||anchor="HExample5:SendapreparedMimeMessagetoalistofUsersandGroups"]] of the documentation for a sample.
42 42  * Mail API has been slightly modified to fix a bug when waiting for all mails to have been processed (the ##waitForProcessing()## wasn't really waiting!). As a consequence calls to ##MailResult.waitTillProcessed(long timeout)## and ##MailResult.isProcessed()## have been replaced by calls to ##MailStatusResult.waitTillProcessed(long timeout)## and ##MailStatusResult.isProcessed()##. Note that for backward compatibility reason the scripting API still supports the old API (but it's deprecated and you should move your code to use the new API).
43 43  * 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.
44 -* The Mail module's prepare step now does a better handling of the ExecutionContext by cloning it. This way you can safely use it while rendering your mail's template, when you are using the velocity bindings. More details on [[XWIKI-12090>>http://jira.xwiki.org/browse/XWIKI-12090]]
44 +* 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.
45 45  
46 46  == Job Progress Improvements ==
47 47  
... ... @@ -65,7 +65,7 @@
65 65  
66 66  = Tested Browsers & Databases =
67 67  
68 -{{include reference="TestReports.ManualTestReportTemplateSummary"/}}
68 +{{include reference="TestReports.ManualTestReportXWiki71M2Summary"/}}
69 69  
70 70  = Known issues =
71 71  

Get Connected