<
From version < 9.1 >
edited by Denis Gervalle
on 2011/11/21
To version < 10.2 >
edited by Vincent Massol
on 2011/11/24
>
Change comment: Use shorter headings for better layout

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.dgervalle
1 +XWiki.VincentMassol
Content
... ... @@ -2,8 +2,6 @@
2 2  {{toc/}}
3 3  {{/box}}
4 4  
5 -<insert description of release here>
6 -
7 7  = New and Noteworthy (since XWiki Enterprise 3.3 Milestone 1) =
8 8  
9 9  == Link Checker ==
... ... @@ -24,6 +24,10 @@
24 24  
25 25  [[image:cjk.png||class="screenshot"]]
26 26  
25 +== Updated the installation process of Workspaces ==
26 +
27 +The [[Workspace Application>>http://extensions.xwiki.org/xwiki/bin/view/Extension/Workspace+Application]] requires that an admin provides the initial workspace template (as before), but now it can be anything the admin wants to use as base. The admin only has to rename it to "workspace-template.xar" and attach it to the WorkspaceManager.Install page. The workspace-related pages and settings will be applied to the template automatically.
28 +
27 27  = For Developers =
28 28  
29 29  == JSR330 Provider Support ==
... ... @@ -35,11 +35,11 @@
35 35  * You wish to lazily get a component instance (instead of it getting injected when your Component is looked up the first time)
36 36  * You wish to control how you return the instance you're providing for. For example you may wish to read the Component Hint from a configuration file and return the instance of the Component matching that Hint dynamically
37 37  
38 -== Component registration and unregistration event are now properly paired ==
40 +== Component Event Improvement ==
39 39  
40 40  The registration and unregistration event triggered by a component manager is now perfectly paired. Registering an existing component role and hint now trigger the unregistration event before registering the new component.
41 41  
42 -== New Disposable interface for singleton components ==
44 +== New Disposable interface for Ccomponents ==
43 43  
44 44  To prepare the future uninstallation feature of the Extension Manager, singleton components could now implements the Disposable interface. This interface require a single dispose() methods that will be call when a singleton component is unregistered from its component manager. When a singleton component has been created, this could happen in three cases:
45 45   * the component role and hints is explicitly unregistered

Get Connected