Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -8,7 +8,7 @@
8	8
9	9	= New and Noteworthy (since XWiki 7.4) =
10	10
11		-[[Full list of issues fixed and Dashboard for <version>>>http://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=<fill id here>]].
	11	+[[Full list of issues fixed and Dashboard for 8.0-milestone-1>>http://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=<fill id here>]].
12	12
13	13	== <feature N> ==
14	14
...	...	@@ -108,7 +108,7 @@
108	108	* Replaced a few String based APIs by Locale based equivalent
109	109	* Generated URLs for document-based skin extensions (SSX and JSX) now contain the version of the document, so when a change is made to the extension the browser don't use an outdated version from its cache.
110	110	* Support for chaining uberspectors, first introduced in XWiki as an enhancement of Velocity 1.5, has been part of the official library since Velocity 1.6. As such, we're deprecating our custom classes that provide this functionality. If you have custom uberspectors that implement ##org.xwiki.velocity.introspection.ChainableUberspector## or extend ##org.xwiki.velocity.introspection.AbstractChainableUberspector##, update them to ##org.apache.velocity.util.introspection.ChainableUberspector## and ##org.apache.velocity.util.introspection.AbstractChainableUberspector##. If you have a custom list of uberspectors specified under ##runtime.introspector.uberspect.chainClasses##, just use the ##runtime.introspector.uberspect## property for defining the list.
111		-* the [[XWiki Select Widget>>platform:DevGuide.XWikiSelect]] now offers a javascript API in the form of a jQuery plugin, to get the current value or clear the selection (it was also introduced in [[XWiki 7.4.1>>ReleaseNotes.ReleaseNotesXWiki741]]).
	111	+* the [[XWiki Select Widget>>platform:DevGuide.XWikiSelect]] now offers a javascript API in the form of a jQuery plugin, to get the current value or clear the selection.
112	112	* the [[WYSIWYG editor>>extensions:Extension.WYSIWYG Editor Module]] script service has a new method to render a document as a full HTML page. You can use it like this:(((
113	113	{{code language="none"}}<textarea class="wysiwyg">$escapetool.xml($services.wysiwyg.render('Some.Content.Template'))</textarea>{{/code}}
114	114	The main difference between this API and the existing ##$doc.getRenderedContent()## is that it replaces [[the skin extension hooks>>extensions:Extension.Skin Extension Plugin]] with the corresponding resource includes (e.g. style sheets includes), allowing us to define a WYSIWYG editor content template in a wiki page.
...	...	@@ -151,14 +151,11 @@
151	151
152	152	* The WebDAV feature is now configured using Servlet 3.0 annotations. Make sure you deploy XWiki in a Servlet Container that is configured to discover Servlet 3.0 annotations (at least for the XWiki ##xwiki-platform-webdav-server-*.jar## JAR). If you're upgrading also make sure you edit your ##web.xml## to remove all the Servlet and Filter definitions for WebDAV (search for ##dav## in ##web.xml##).
153	153	* With the improvement done in the wiki links, ##image~:## and ##attach~:## syntax, existing untyped links pointing to inexistent documents (e.g. ##~[~[Doc]]##) will no longer be resolved to point to a new terminal document in the same space (i.e. ##<currentSpace>.Doc##, when ##<currentSpace>.Doc## does not exist), but will be resolved to point to a new non-terminal document in the top level (i.e. ##Doc.WebHome##). The reason is because we don`t currently have a way to specify a relative link to a nested document (i.e. space) and we only use absolute links. This only affects wanted links, since for existing documents the backwards compatibility mechanism preserves the previous behavior.
	154	+* Mail API Unique Message Identifier (since 7.4.1): In order to solve [[XWIKI-12165>>http://jira.xwiki.org/browse/XWIKI-12165]], the unique identifier of each mime message sent has been change to a SHA1 based on the ##Message-ID## header and the list of recipients of the mails, ensuring uniqueness during a newsletter or mailing sending. To introduce this change, the ##MailContentStore## and the ##MailListener API## has been broken, and now use a new ExtendedMimeMessage instead of the simple ##MimeMessage## for all arguments. The values ##messageId## returned or used as argument in the API is no more equivalent to the ##Message-ID## header, but is now the unique identifier returned by ##ExtendedMimeMessage#getUniqueMessageId()##. Finally, the ##MessageMimeMessageFactory## now returns cloned ##MimeMessage## without changing the ##Message-ID##.
154	154
155		-== Mail API Unique Message Identifier (since 7.4.1) ==
156		-
157		-In order to solve [[XWIKI-12165>>http://jira.xwiki.org/browse/XWIKI-12165]], the unique identifier of each mime message sent has been change to a SHA1 based on the ##Message-ID## header and the list of recipients of the mails, ensuring uniqueness during a newsletter or mailing sending. To introduce this change, the ##MailContentStore## and the ##MailListener API## has been broken, and now use a new ExtendedMimeMessage instead of the simple ##MimeMessage## for all arguments. The values ##messageId## returned or used as argument in the API is no more equivalent to the ##Message-ID## header, but is now the unique identifier returned by ##ExtendedMimeMessage#getUniqueMessageId()##. Finally, the ##MessageMimeMessageFactory## now returns cloned ##MimeMessage## without changing the ##Message-ID##.
158		-
159	159	== API Breakages ==
160	160
161		-The following APIs were modified since <project> <version - 1>:
	158	+The following APIs were modified since XWiki 7.4:
162	162
163	163	{{code language="none"}}
164	164	<clirr output here>