Summary

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

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.VincentMassol
	1	+XWiki.Sergiu

Content

...	...	@@ -2,8 +2,20 @@
2	2	{{toc/}}
3	3	{{/box}}
4	4
	5	+Second (and last) milestone release of the 3.3 version.
	6	+
5	5	= New and Noteworthy (since XWiki Enterprise 3.3 Milestone 1) =
6	6
	9	+== New User Interface for the Extension Manager ==
	10	+
	11	+Although there's no back-end repository where to search for new extensions yet, the new UI for the Extension Manager is starting to shape up. The previous experimental UI has been replaced by a new category in the Administration dedicated to the extension manager, with three different sections.
	12	+
	13	+[[image:em.png||class="screenshot"]]
	14	+
	15	+[[image:searchextensions.png||class="screenshot"]]
	16	+
	17	+[[image:showextension.png||class="screenshot"]]
	18	+
7	7	== Link Checker ==
8	8
9	9	It's now possible to [[check the statuses of all external links found in your wiki>>extensions:Extension.Link Checker Application]].
...	...	@@ -37,11 +37,11 @@
37	37	* You wish to lazily get a component instance (instead of it getting injected when your Component is looked up the first time)
38	38	* 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
39	39
40		-== Component Event Improvement ==
	52	+== Component registration and unregistration event are now properly paired ==
41	41
42	42	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.
43	43
44		-== New Disposable interface for Ccomponents ==
	56	+== New Disposable interface for singleton components ==
45	45
46	46	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:
47	47	* the component role and hints is explicitly unregistered
...	...	@@ -122,13 +122,9 @@
122	122	* EntityReference#replaceParent(oldParent,newParent) allow creating a new entity with one of the parent in the parent chain replaced
123	123	* EntityReference#appendParent() allow creating a new entity with an appended root parent, this one is useless on any derived class since the parent chain could not appended in them.
124	124
125		-== Issues specific to <projet> <version> ==
126		-
127		-<issues specific to the project>
128		-
129	129	== API Breakages ==
130	130
131		-The following APIs were modified since <project> <version - 1>:
	139	+The following APIs were modified since XWiki Enterprise 3.2:
132	132
133	133	{{code language="none"}}
134	134	<clirr output here>