Last modified by Thomas Mortagne on 2023/10/13

<
From version < 5.1 >
edited by Vincent Massol
on 2011/12/15
To version < 6.1 >
edited by Vincent Massol
on 2011/12/15
>
Change comment: Merge developers + translations sections

Summary

Details

Page properties
Content
... ... @@ -73,29 +73,85 @@
73 73  
74 74  = For Developers =
75 75  
76 -== <developer feature N> ==
76 +== Script services for Application Manager and Wiki Manager ==
77 77  
78 -<description of developer feature N>
78 +There are script services now available for the old application and wiki manager plugins. You can access them via ##$services.applicationmanager## and ##$services.wikimanager##, and call all the methods previously exposed by their respective plugin APIs. For the moment the plugins are still there, with the script services just bridging them to the new preferred way of accessing APIs from Velocity scripts.
79 79  
80 -== Deprecated and Retired projects ==
80 +== Cache improvements ==
81 81  
82 -<description of deprecated and retired projects>
82 +Several bugfixes and improvements have been committed, affecting the rendering cache, the cache macro, and the cache infrastructure in general. An important change is the introduction of an infinispan-based cache implementation, replacing JBossCache as the default one.
83 83  
84 +== New xdom+xml syntax ==
85 +
86 +The rendering now come with two reference XML based syntaxes which are the exact representation of rendering events.
87 +
88 +Two variants are provided:
89 +* 1.0: a stable syntax which represent the rendering events in the state they had when this version has been released. If anything change a new version of the syntax will be created (1.1, etc.)
90 +* current: always in sync with rendering events whatever the version but also mean that it can change anytime without warning, only use that for internal use when you are sure you will render and parse with the same version of XWiki Rendering
91 +
92 +== XE and XEM XAR changes ==
93 +
94 +The XAR plugin by default doesn't bundle dependencies anymore, so the XE and XEM XARs now come in two variants:
95 +
96 +* the old ##xwiki-enterprise-wiki## module has been renamed into [[##xwiki-enterprise-ui##>>https://github.com/xwiki/xwiki-enterprise/tree/xwiki-enterprise-3.3-milestone-1/xwiki-enterprise-ui]], and produces a XAR only with the documents specific to XWiki Enterprise, without dependencies;
97 +* the full XAR with all the dependencies bundled in it is now produced by the [[##xwiki-enterprise-ui-all##>>https://github.com/xwiki/xwiki-enterprise/tree/xwiki-enterprise-3.3-milestone-1/xwiki-enterprise-distribution/xwiki-enterprise-ui-all]] module.
98 +
99 +== JSR330 Provider Support ==
100 +
101 +XWiki now [[supports JSR330 Providers>>extensions:Extension.Component Module#HRegisteringandUsingaProvider]].
102 +
103 +They are useful for the following use cases:
104 +* You wish to break a cyclic dependency
105 +* You wish to lazily get a component instance (instead of it getting injected when your Component is looked up the first time)
106 +* 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
107 +
108 +== Component Event Improvements ==
109 +
110 +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.
111 +
112 +== New Disposable interface for Components ==
113 +
114 +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:
115 + * the component role and hints is explicitly unregistered
116 + * another component role with same hints is registered and therefore replace the existing component
117 + * the component instance is explicitly released calling the release function in the manager
118 +
119 +Components that require a singleton component should be aware that the instance provided is now subject release and should prevent from accessing a component that have been released. This could be done by observing the registration events of the component manager. The Unregister Event is always triggered when a component is released.
120 +
84 84  == Upgrades ==
85 85  
86 86  The following dependencies have been upgraded:
87 87  
88 -* <list libraries that have been upgraded>
125 +* commons-lang 3.1
126 +* Groovy 1.8.4
127 +* LogBack 1.0
128 +* Selenium 2.13.0
129 +* SLF4J 1.6.4
130 +* Maven AntRun Plugin 1.7
131 +* Maven Shade Plugin 1.5
132 +* Maven Checkstyle Plugin 2.8
133 +* CSS4J 0.13
134 +* JGroups 2.12.2
135 +* Reflections 0.9.6
89 89  
90 90  == Miscellaneous ==
91 91  
92 -<other stuff to add and link to JIRA for all issues fixed>
139 +* Make it simple to add Icon Transformation mappings when using the Rendering in standalone mode
140 +* Add support for being able to override components more than once TODO: Document it and linke to the documentation
141 +* Bundle the Icon and WikiWord Transformations in the Rendering Standalone JAR
142 +* Comments Macro is not bundled in the Rendering Standalone JAR
143 +* Allow setting time to live and max entries when using the Cache macro
144 +* IRC Bot application improvements
145 +* Move to JBoss Infinispan as default cache implementation
146 +* Application Manager and Wiki Manager plugins now expose a ScriptService and don't need to be added as plugin in xwiki.cfg file anymore. You can access they using {{code language="velocity"}}$services.applicationmanager{{/code}} and {{code language="velocity"}}$services.wikimanager{{/code}}.
147 +* The Dashboard feature which was part of several applications (XWiki Enterprise Application and Administration Application) has been extracted into in a separate [[Dashboard Application>>extensions:Extension.Dashboard Application]]. There's now a new ##Dashboard## space which is visible in the list of spaces on the XE home page.
148 +* [[XRENDERING-161>>http://jira.xwiki.org/browse/XRENDERING-161]]: Starting with XE 3.2 we had introduced caching of rendered content to improve performances but that led to a huge increase in memory needs. We've now tuned this and we've been able to keep the performance improvement and at the same time to drastically reduce the memory need.
93 93  
94 94  == Translations ==
95 95  
96 96  The following translations have been updated:
97 97  
98 -{{language codes="code1, code2"/}}
154 +{{language codes="cs, fr, pl, pt_BR, ru, sv, uk, it"/}}
99 99  
100 100  = Supported Browsers =
101 101  

Get Connected