| 13 | |
| 14 | Bug fixes: |
| 15 | * Login/Logout: |
| 16 | * 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). |
| 17 | * 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). |
| 18 | * 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). |
| 19 | * When the user enters neither a username nor a password in the login dialog no exception occurs (#473). |
| 20 | * The type loader doesn't throw a bogus "Endless recursion" exception when repeatedly tried to load a type with an invalid URI (#487). |
| 21 | * Exceptions thrown from request filters (formerly servlet filters) appear in the log file (if file logging is activated) (#474). |
| 22 | * Webclient model update: |
| 23 | * When processing the directives of an update request the `dm4c.selected_object` is updated properly (#488). |
| 24 | * 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). |
| 25 | * 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). |
| 26 | * Web application plugins (derived from `WebActivatorPlugin`) are detected as DeepaMehta plugins. The `ALL_PLUGINS_ACTIVE` event is fired properly (#498). |
39 | | Bug fixes: |
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). |
45 | | * 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). |
50 | | * 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). |
51 | | * Web application plugins (derived from `WebActivatorPlugin`) are detected as DeepaMehta plugins. The `ALL_PLUGINS_ACTIVE` event is fired properly (#498). |