| 6 | |
| 7 | == ''upcoming:'' DeepaMehta 4.1.1 == |
| 8 | |
| 9 | Plugin Development Framework: |
| 10 | * New Property API: a plugin can store and index node properties. Node properties are topic/association metadata like timestamps or ACL information (#472). |
| 11 | * 3 new core events: |
| 12 | * SERVICE_REQUEST_FILTER allows request manipulation and interruption for REST service requests (#480). |
| 13 | * RESOURCE_REQUEST_FILTER allows request manipulation and interruption for static resource requests (#480). |
| 14 | * |
| 15 | * Simplified API: the Core API's and standard plugin service's get/retrieve/delete methods no longer require the `clientState` parameter (#496). |
| 16 | * A plugin can produce specific HTTP (error) responses by throwing a WebApplicationException from its resource methods or event handlers (#484). |
| 17 | * Exceptions thrown resource methods or event handlers must no longer be wrapped in a WebApplicationException when a 500 response is intended (#484). |
| 18 | |
| 19 | Further changes: |
| 20 | * The dependency on Felix's proprietary ExtHttpService is dropped. We are ready to replace Felix HTTP Service with OPS4J Pax Web (#448). |
| 21 | |
| 22 | Bug fixes: |
| 23 | * Web application plugins (derived from WebActivatorPlugin) are detected as DeepaMehta plugins. The ALL_PLUGINS_ACTIVE event is properly fired (#498). |
| 24 | * Exceptions thrown from request filters appear in the log file (#474). |