Skip to Content

Version 5.1 by Denis Gervalle on 2012/03/12
Show last authors
1 (% style='font-size:x-large;' %)
2 {{warning}}
3 Before upgrading to this version, be sure to have a working backup of your database(s).
4 {{/warning}}
5
6 {{box cssClass="floatinginfobox" title="**Contents**"}}
7 {{toc/}}
8 {{/box}}
9
10 This is the first milestone of the XWiki Enterprise 4.0 version ([[Roadmap>>Main.Roadmap]]). This release brings reduced document database id collision and quite a few improvements and bug fixes.
11
12 = New and Noteworthy (since XWiki Enterprise 3.5 version) =
13
14 == Extension Manager improvements ==
15
16 === Extension Manager ===
17
18 * Added possibility to choose on which wiki to install an extension
19 * When installing/uninstalling extension or any other background job, the result of the job executing is stored on the filesystem so that it can be reviewed later. There is no UI to access it yet but it's always possible to access the saved file on filesystem directly.
20
21 === XWiki Repository ===
22
23 * Added a button to update an imported extension
24 * It's now possible to extend an Extension sheet with custom informations. For example http://extensions.xwiki.org adds "Bundled with" and "Compatibility" fields.
25
26 = For developers =
27
28 == Extension Manager moved to commons ==
29
30 Everything not not specifically related to wiki is now part of xwiki-commons. That means that anyone can get all Extension Manager features (easy live JAR installation/uninstallation from remote repositories, dependency management, etc.) in any Java application.
31
32 == Classloader module moved to commons ==
33
34 Mostly been moved as Extension Manager dependency but also useful on it own as a tool to dynamically add new URLs in a classloader at runtime.
35
36 == New Job module ==
37
38 The code to execute a task in backgroup and provide related progress and isolated log has been extracted from Extension Manager and is now in its own module.
39
40 == Component related improvements ==
41
42 === Role moved from Class to Type ===
43
44 In order to support parameterized role like DocumentReferenceResolver<String>, all the APIs of ComponentManager and Component descriptors has been changed to take Type instead of Class. All the old API are still here and working but deprecated.
45
46 === ComponentRole is deprecated ===
47
48 You should now use @Role instead of @ComponentRole. The difference is that when using @Role the generic parameters will be taken into account as part of the role while with @ComponentRole the role stay the Class of the component role so be careful when you do this change, it might break everything if you don't want to take into account parameters (that's why a new annotation has been introduced instead of changing the behavior of ComponentRole).
49
50 === References resolver/serializer and Provider now support parameter type as part of the role ===
51
52 This mean that declaring or injecting a such component no longer require any hint unless you want to provide/inject a variant for the same type.
53
54 Here are some example. Instead of:
55
56 {{code language="java"}}
57 @Inject
58 @Named("reference/default")
59 private DocumentReferenceResolver<EntityReference> resolver
60
61 @Inject
62 @Named("reference/current")
63 private DocumentReferenceResolver<EntityReference> resolver
64
65 @Inject
66 @Named("sometypeprovider")
67 private Provider<SomeType> resolver
68 {{/code}}
69
70 you will write
71
72 {{code language="java"}}
73 @Inject
74 private DocumentReferenceResolver<EntityReference> resolver
75
76 @Inject
77 @Named("current")
78 private DocumentReferenceResolver<EntityReference> resolver
79
80 @Inject
81 private Provider<SomeType> resolver
82 {{/code}}
83
84 All reference resolver and serializer provide static variables with the Type for both String and EntityReference. For example you can write:
85
86 {{code language="java"}}
87 DocumentReferenceResolver<EntityReference> resolver = componentManager.lookupComponent(DocumentReferenceResolver.TYPE_REFERENCE, "current")
88 {{/code}}
89
90 = Bug fixes and improvements =
91
92 * [[XE-1096>>http://jira.xwiki.org/browse/XE-1096]] The attachment selector should also work with the ##/edit/## action in 'Inline form' edit mode
93 * [[XE-1105>>http://jira.xwiki.org/browse/XE-1105]] Default class sheet doesn't display correctly the class title
94 * [[XWIKI-7411>>http://jira.xwiki.org/browse/XWIKI-7411]] Cannot import a XAR containing ##%3A## in its file name
95 * [[XWIKI-6305>>http://jira.xwiki.org/browse/XWIKI-6305]] Keep the current user in the administration application when editing user details
96 * [[XWIKI-7462>>http://jira.xwiki.org/browse/XWIKI-7462]] Improve the Profile breadcrumb to be more user friendly
97 * [[XWIKI-7484>>http://jira.xwiki.org/browse/XWIKI-7484]] Write a log line in the console instructing the user to open XWiki in a browser
98
99 See the full list of [[JIRA issues>>http://jira.xwiki.org/sr/jira.issueviews:searchrequest-printable/temp/SearchRequest.html?jqlQuery=project+in+%28XCOMMONS%2C+XRENDERING%2C+XWIKI%2C+XE%2C+XEM%29+and+status+%3D+Closed+and+resolution+%3D+Fixed+and+fixVersion+%3D+%223.5-milestone-1%22&tempMax=1000]] fixed in this release.
100
101 = For Developers =
102
103 * [[XCOMMONS-94>>http://jira.xwiki.org/browse/XCOMMONS-94]] Set the minimum required Maven version (3.0) to build XWiki in the POM
104 * [[XWIKI-7502>>http://jira.xwiki.org/browse/XWIKI-7502]] Replace notion of Container's ApplicationContext with the notion of Environment
105 * [[XWIKI-7476>>http://jira.xwiki.org/browse/XWIKI-7476]] Sheets need to be able to display the title of the document they are applied to
106 * [[XWIKI-7526>>http://jira.xwiki.org/browse/XWIKI-7526]] Enable Infinispan JMX mbeans by default for runtime monitoring of XWiki caches
107 * [[XWIKI-7504>>http://jira.xwiki.org/browse/XWIKI-7504]] Files within WEB-INF directory readable by using Velocity
108 * [[XE-1108>>http://jira.xwiki.org/browse/XE-1108]] Provide tomcat5 and tomcat7 based Debian packages
109
110 == Upgrades ==
111
112 The following dependencies have been upgraded:
113
114 *
115
116 == Translations ==
117
118 The following translations have been updated:
119
120 {{language codes="fr, it, ko, lv, sv"/}}
121
122 = Tested Browsers =
123
124 {{todo/}}
125
126 = Known issues =
127
128 * [[Bugs we know about>>http://jira.xwiki.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=category+%3D+%22Top+Level+Projects%22+AND+issuetype+%3D+Bug+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC]]
129
130 = Test Report =
131
132 You can check the [[manual test report>>TestReports.ManualTestReportXE40M1]] to learn about what was tested and the results on various browsers.
133
134 = Backward Compatibility and Migration Notes =
135
136 == Migration of database IDs ==
137
138 You need to enable database migration (//xwiki.store.migration=1//) to upgrade existing databases to the new identifier format.
139
140 {{info}}
141 This is a major migration affecting almost all rows and relations in the database. I may takes a while before the wiki respond to your initial request when you are migrating a large database. The initial request may even timeout but the database migration continue in the background.
142 {{/info}}
143
144 {{warning}}
145 Avoid to interrupt the database migration process and check the current progress of the database migration in the console output or the log file. The progress may be slow, so be patient during document id and object id conversion.
146 {{/warning}}
147
148 In case of interruption, the migration procedure could be restarted by restarting XWiki, and it will start over where it have been interrupted.
149
150 {{warning}}
151 We have taken many precaution to provide a reliable migration procedure, but due to the large changes it made, and this release being an unstable one, you should be really careful and ensure that you keep an appropriate backup until you are sure that your data has been properly migrated.
152 {{/warning}}
153
154 If you have custom mapped classes used externally, be aware that all internal identifier are now full 64bits longs.
155
156 == General Notes ==
157
158 {{info}}
159 If you're running in a multiwiki setup you'll also need to define the property //xwiki.store.migration.databases// in your //xwiki.cfg// file if you want to explicitly name some databases to be migrated as the default is now to migrate all databases. Database that are not migrated could not be accessed.
160 {{/info}}
161
162 You may also want to [[import the default wiki XAR>>Main.Download]] in order to benefit from all the improvements listed above.
163
164 {{warning}}
165 Always make sure you compare your ##xwiki.cfg## and ##xwiki.properties## files with the newest version since some configuration parameters were 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.
166 {{/warning}}
167
168 == API Breakages ==
169
170 The following APIs were modified since version 3.5:
171
172 {{todo/}}
173
174 {{code language="none"}}{{/code}}

About

About

Support

Platform

User Guide

Admin Guide

Developer Guide

Projects

XWiki

Extensions

Other

Contribute

Status

Practices

Under the Hood

Get Involved

Get Connected