Changes between Version 67 and Version 68 of ReleaseNotes


Ignore:
Timestamp:
24.08.2013 02:35:52 (8 years ago)
Author:
jri
Comment:

4.1.1 release notes, pt. 5

Legend:

Unmodified
Added
Removed
Modified
  • ReleaseNotes

    v67 v68  
    2323    * A plugin can produce specific HTTP (error) responses by throwing a WebApplicationException from its resource methods or event handlers (#484, #481). 
    2424    * Exceptions thrown from resource methods or event handlers must no longer be wrapped in a WebApplicationException if a 500 response is intended (#484). 
     25* (REST) resource methods can use an arbitrary class for the entity parameter as long as the entity is represented in JSON and the class has a public JSON constructor. Implementing a custom JAX-RS provider class is no longer required (#277). 
    2526* Access Control API: there are methods for retrieving topics/associations based on creator or owner (#458). 
    26 * New Webclient event (client-side): `pre_send_request` allows plugins to investigate and manipulate a request before it is send to the server (#486). 
     27* Webclient: 
     28    * New Webclient event (client-side): `pre_send_request` allows plugins to investigate and manipulate a request before it is send to the server (#486). 
     29    * The default topicmap view model is renderer agnostic. It is reusable by different renderer implementations (#443). 
    2730* Plugins can send REST service requests asynchronously (#476). 
    2831 
    2932Further changes: 
    30 * The dependency on Felix's proprietary ExtHttpService is dropped. We are ready to replace Felix HTTP Service with OPS4J Pax Web. OPS4J Pax Web is a far more modern and flexible OSGi HTTP Service implementation which enables a variety of new applications (#448). 
    31 * The REST service no longer delivers user-related permission information along with the topics/associations. Instead the Access Control API provides methods for retrieving the permissions explicitly (#489). This makes topic/association responses cachable by the browser (#478). 
     33* The REST service no longer delivers user-related permission information along with topic/association responses. The permissions are explicitly retrieved through the Access Control service (#489). This makes topic/association responses cachable by the browser (#478). 
    3234* Core Service REST API: the URLs for topic/association update (PUT) requests are REST-conform (#482). 
     35* The dependency on Felix's proprietary "Extended HTTP Service" is dropped. Thus we are ready to replace Felix HTTP Service with OPS4J Pax Web soon. OPS4J Pax Web is the far more modern and flexible OSGi HTTP Service implementation which enables a variety of new applications (#448). 
     36* The DM Karaf distro uses same default configuration as the DM Standard Distro (#447). 
     37* COPYRIGHT.txt is updated (#434). 
    3338 
    3439Bug fixes: 
    35 * Web application plugins (derived from WebActivatorPlugin) are detected as DeepaMehta plugins. The ALL_PLUGINS_ACTIVE event is properly fired (#498). 
    36 * Exceptions thrown from request filters (formerly servlet filters) appear in the log file (#474). 
    37 * Webclient: when processing the directives of an update request the `dm4c.selected_object` (part of the Webclient model) is updated properly (#488). 
    38 * Webclient: construction of the object model passed to a topic/association update request no longer manipulates the `dm4c.selected_object` in place. This allows a plugin to investigate the selected object's metadata (e.g. timestamps, access control information) before the request is actually send (#486). 
     40* Login/Logout: 
     41    * Logout works for private DM installations as well. (A private DM installation is one with `read_requires_login=true`.) The missing HTTP Logout is emulated by forcing the browser to bring up a dummy login dialog (#423). 
     42    * Login works for open DM installations as well. (An open DM installation is one with `read_requires_login=false` and `write_requires_login=false`.) (#475). 
     43    * When wrong credentials are entered DM's login dialog is not overlapped by the browser's login dialog. The user stays in DM's login dialog (#471). 
     44    * When the user enters neither a username nor a password in the login dialog no exception occurs (#473). 
    3945* The type loader doesn't throw a bogus "Endless recursion" exception when repeatedly tried to load a type with an invalid URI (#487). 
     46* Exceptions thrown from request filters (formerly servlet filters) appear in the log file (if file logging is activated) (#474). 
     47* Webclient model update: 
     48    * When processing the directives of an update request the `dm4c.selected_object` is updated properly (#488). 
     49    * Construction of the object model passed to a topic/association update request no longer manipulates the `dm4c.selected_object` in place. This allows a plugin to investigate the selected object's metadata (e.g. timestamps, access control information) before the request is send (#486). 
    4050* Requests issued by the Webclient have no superfluous "?" character at the end as it might confuse the browser's or network proxy's caching heuristic (#483). 
    41 * Login works with an open DM installation as well. (An open DM installation is one with read_requires_login=false and write_requires_login=false) (#475). 
    42  
     51* Web application plugins (derived from `WebActivatorPlugin`) are detected as DeepaMehta plugins. The `ALL_PLUGINS_ACTIVE` event is fired properly (#498). 
     52 
     53---- 
    4354 
    4455== 2013-03-11: DeepaMehta 4.1 ==