Changes between Version 39 and Version 40 of ReleaseNotes

Timestamp:

11.09.2012 19:36:03 (12 years ago)

Author:

jri

Comment:

--

ReleaseNotes

@@ -16 +16 @@
 * Access Control Foundation (#262).
     * Each topic, association, and type is attached with a Access Control List. There are 2 operations: WRITE, CREATE. There are 5 user roles: CREATOR, OWNER, MEMBER, USER, EVERYONE.
-    * Fully interactive read-only topicmaps (#269).
-    * Private installations [a661efb0].
+    * Scenario 1: Publishing fully interactive read-only topicmaps (#269).
+    * Scenario 2: Fully closed workgroup installations [a661efb0].
 * Backend Security (#293).
     * Global request filter [a0b48d3a].
@@ -24 +24 @@
 
 Improvements:
+* The detail panel lists the topics associated with the selected association (#306).
+* Modelers can utilize a Checkbox Renderer for multiple selection (#270) [6c4d87ad].
 * Launching and reloading the Webclient is speeded up (#286).
-* Modelers can utilize a Checkbox Renderer for multiple selection (#270) [6c4d87ad].
-* The detail panel lists the topics associated with the selected association (#306).
 
 Bug Fixes:
@@ -35 +35 @@
 Plugin Development Framework:
 * Simplified plugin development (more Convention Over Configuration):
-    * A plugin's REST resources and Provider classes are registered automatically. Plugins must no longer provide (JAX-RS) Application classes (#272) [a39e39c1].
+    * A plugin's REST resources and (JAX-RS) Provider classes are registered automatically. Plugins must no longer provide (JAX-RS) Application classes nor do manual configuration (#272) [a39e39c1].
     * All (JAX-RS) Provider classes are available to all plugins automatically [44d49e12].
     * A plugin's client-side main file is picked up automatically (#276) [b30004d6].
@@ -41 +41 @@
     * A plugin's CSS stylesheets are picked up automatically (#285) [2bee421c].
     * Plugin developers must no longer care about firing PRE_SEND (formerly POST_FETCH) events (#297, #268).
-    * A plugin is no longer required to have a main file (plugin.js). This is perfect for plugins whose only purpose is to provide custom renderers [3a4a0cbe].
-* Extended plugin infrastructure:
+    * A plugin's client-side part is no longer required to contain a main file (plugin.js). This is perfect for plugins whose only purpose is to provide custom renderers [3a4a0cbe].
+* Plugin infrastructure:
     * A plugin can publish a directory of the server's file system to the web (#292) [dea0910b].
     * A plugin can register a (Servlet API) filter (#293) [520c95c0].
+    * A plugin's client-side part is namespaced per URI for friendly co-existence (#275) [082a4651][faf8d006].
     * Custom renderer implementations (page renderers, simple renderers, multi renderers) are namespaced per URI for friendly co-existence (#282) [9bb0c6a7][4aab34b1].
-    * A plugin's client-side part is namespaced per URI for friendly co-existence (#275) [082a4651][faf8d006].
+    * A plugin can register listeners for 4 new Core Events: PRE_CREATE_ASSOCIATION, POST_CREATE_ASSOCIATION, PRE_SEND_ASSOCIATION [98fb628d], INITIALIZE_PLUGIN [435f4285].
     * A plugin can operate on the logged in user's HTTP session (#293) [faa7485e].
-    * A plugin can register listeners for 4 new Core Events: PRE_CREATE_ASSOCIATION, POST_CREATE_ASSOCIATION, PRE_SEND_ASSOCIATION [98fb628d], INITIALIZE_PLUGIN [435f4285].
-* Custom renderers:
-    * New renderer type: Multi Renderer. A plugin can provide custom renderers for multi-value topics (cardinality "Many") (#270) [6c4d87ad][7fe0a806].
+* Renderer Framework:
+    * New renderer type: Multi Renderer. A plugin can provide custom renderers for multi-value topics (in conjunction with cardinality "Many") (#270) [6c4d87ad][7fe0a806].
     * Topicmap renderers have a server-side part as well (#294).
 * Core consolidation and optimization:
-    * The core service now processes update requests where aggreagted composite child topics are involved (#30, #267).
-    * For handling core events plugins implement listener interfaces instead of overriding methods. The core delivers events to the registered listeners instead of iterating over all plugins. This is the more efficient approach (#261) [b59fff18].
+    * The core service is now able to process update requests where aggreagted composite child topics are involved (#30, #267).
+    * For handling core events plugins implement listener interfaces instead of overriding methods. A plugin's listeners are registered automatically. The core delivers events to the registered listeners instead of iterating over all plugins. This is the more efficient approach (#261) [b59fff18].
     * The application layer is separated from the network layer. This avoids high-rate firing of unnecessary core events (#268).
     * Core is modularized and its API is cleaned up (#281).
 * Miscellaneous:
     * The Proxy plugin is dropped. Its features are transfered to the Files plugin (#292).
-    * The Facets plugin is included to the DeepaMehta Standard Distribution (required by Access Control plugin)
+    * The Facets plugin is included to the DeepaMehta Standard Distribution (required by the Access Control and Workspaces plugins).
     * The Javadoc Maven plugin is configured to generate cross-referenced API Docs with inlined class hierarchy diagrams [5d6b13bc].
-    * A lot of API changes and extensions in several plugins, e.g. the Facets API supports multi-value facets.
+    * A lot of API changes and extensions in various plugins, e.g. the Facets API supports multi-value facets.
     * Updated jQuery 1.7 -> 1.7.2 and jQuery UI 1.8.16 -> 1.8.21