Ticket #296 (closed Defect: fixed)
Creating new File Browser throws error
Reported by: | jri | Owned by: | jri |
---|---|---|---|
Priority: | Major | Milestone: | Release 4.1 |
Component: | DeepaMehta Standard Distribution | Version: | 4.0.12-SNAPSHOT |
Keywords: | Cc: | dgf, Malte | |
Complexity: | 3 | Area: | |
Module: |
Description
On the browser's error console:
AccessControlError: topic 20789 (type_uri="dm4.files.folder") has no permissions info
Change History
comment:2 Changed 12 years ago by Jörg Richter
Core: PRE_SEND fires automatically (#296, #297).
The plugin developer must no longer care about firing PRE_SEND events for hers resource methods.
The framework does this automatically by the means of a Jersey Container Response Filter.
Core service API:
- method fireEvent() is no longer public
- enum CoreEvent? is no longer public
Files plugin:
- this client-side error doesn't appear anymore: AccessControlError: topic 20789 (type_uri="dm4.files.folder") has no permissions info
IMPORTANT: developers must drop the fireEvent() calls from their plugins.
See ticket 297.
See ticket 296.
comment:3 Changed 12 years ago by Jörg Richter
Core: PRE_SEND fires automatically (#296, #297).
The plugin developer must no longer care about firing PRE_SEND events for hers resource methods.
The framework does this automatically by the means of a Jersey Container Response Filter.
Core service API:
- method fireEvent() is no longer public
- enum CoreEvent? is no longer public
Files plugin:
- this client-side error doesn't appear anymore: AccessControlError: topic 20789 (type_uri="dm4.files.folder") has no permissions info
IMPORTANT: developers must drop the fireEvent() calls from their plugins.
See ticket 297.
See ticket 296.